Skip to main content
The Within Agent Development Kit (ADK) takes an item from your roadmap, and the objective behind it, to an agent running in production. The agent is built from your own observed workflows rather than a generic template, and the work happens in the coding agent your team already uses.
Before you start:
  • The Within MCP connected to your coding agent. See Using the Within MCP.
  • A use case chosen in Define, with its objective and constraints. See Define your solution set.
  • Work Brain coverage of the process the agent will work in.

​
How the ADK works

There’s no separate package to install. Once Within is connected, your coding agent fetches the current method from Within at the start of each build and follows it, so every build uses the latest version. Keep the agent’s code, configuration, evaluations and evidence baseline in your own repository, under version control.

​
Specify, build, validate

1

Specify

  • Objective. Restate the business objective and the technology stack the agent has to fit.
  • Coverage. Confirm your Work Brain covers the area. Where it’s thin, run Companion there before you build.
  • Current state. Read the observed work: pain points, bottlenecks, time and motion, the systems in use, and the bright spots.
  • Use case. Screen candidates on evidence, expected impact, feasibility and the controls they need, and pick one.
  • Design. Write the agent specification, effectively a product spec for the agent: scope, governance, credentials, flow, and where a person approves.
A person approves the design before anything is built.
2

Build

Generate the agent’s code, skills and configuration against the specification.
3

Validate

Generate and run evaluations before release, against approved test data, with evidence for every result: ordinary cases, edge cases, malformed or missing inputs, and requests the agent should refuse. A person approves the release. See Validate an agent before release.Then deploy it into your environment, for example as a managed agent.
Along the way you get a current-state read and a recommendation you can share with stakeholders, the agent specification, and the code, skills, configuration and evaluation results.

​
What you can build

Choose the smallest shape that produces the outcome and passes its controls. A scheduled trigger doesn’t on its own mean you need an agent.

​
Which tool can I build in?

Install guides for each client, including Microsoft 365 Copilot, are in the Within MCP developer docs.

​
Controls that stay on

  • Every material claim about the process cites observed data.
  • A person approves the design and the release.
  • Evidence from your Work Brain doesn’t replace security review, system documentation or runtime testing.
  • Connecting the Within MCP doesn’t authorize actions in other systems. Set write access and approvals in your AI client or in the destination system.

​
Getting help

Within’s team can work with your engineers on implementation, production readiness and evaluation design. Ask your Within team.

​
Where to go next

Validate an agent before release

Test it, pilot it, and decide whether it’s ready.

Using the Within MCP

Connect Within to your coding agent or chat app.

The technical track (developer docs)

The full build sequence for developers.

The non-technical track (developer docs)

Skills and simple agents for business users.
Need help? Use the in-app chat — click the chat bubble in the bottom-right corner of Within (staffed 24×5) — or email support@within.ai.