Build with Coding Agents

Use Claude Code, Codex, or Cursor to set up, build, improve, evaluate, review, and deploy an AgentOS Starter.

The repository gives your coding agent the source code, a live MCP endpoint, evals, and runtime logs in one place. It can make a change, exercise it against the running platform, and bring back a verified result.

Everything on this page runs inside a cloned AgentOS Starter. If you don't have one running yet, pick a Starter first.

Skills

Each AgentOS Starter stores its coding-agent workflows in .agents/skills/.

Skill	Use it when
`/setup-platform`	Bring up a fresh clone, verify the platform, and build the first agent
`/create-agent`	Turn an idea into a registered agent and smoke-test it live
`/extend-agent`	Add a tool, capability, instruction change, or targeted fix
`/improve-agent`	Derive probes from an agent's instructions and harden its behavior
`/create-evals`	Add eval coverage for an agent from its behavior and real sessions
`/eval-and-improve`	Diagnose failing evals and repair the affected behavior
`/review-and-improve`	Check code, documentation, configuration, and registered components for drift
`/deploy-platform`	Deploy with the template's provider workflow and verify the live platform

The setup prompt invokes the setup-platform skill from .agents/skills/. Claude Code also discovers the skills through the Starter's committed .claude/skills symlink. Codex and Cursor can link to the same .agents/skills/ directory.

Connect the live platform

Connect the local AgentOS to the supported clients on your machine:

uvx agno connect

The command registers AgentOS with detected Claude Code, Claude Desktop, Codex, and Cursor clients. Your coding agent can then call run_agent, run_team, and run_workflow while it works on the repository.

For a deployed platform:

uvx agno connect --url https://<your-domain>

See Connect Your Clients for authentication modes and client-specific setup.

Keep behavior stable with evals

Use the bundled eval suite to check response quality and tool calls as you change instructions, tools, and models. Run it against a dedicated local test platform and database with no concurrent writers. The starter’s cleanup hooks remove components and learning records created after each case’s snapshot, so concurrent application writes can be removed too. These evals make model calls and require a real provider key.

Install uv, deactivate any existing venv, then create the host environment:

./scripts/venv_setup.sh
source .venv/bin/activate

Then run:

python -m evals --tag smoke      # fast checks of the platform agents
python -m evals --tag release    # broader pre-release confidence
python -m evals --name <case>    # one case while iterating
python -m evals -v               # stream the full run with rich panels

Cases wrap AgentAsJudgeEval (LLM judge, binary pass/fail) and ReliabilityEval (tool-call assertions). Results log to Postgres, so run history shows up at os.agno.com next to sessions and traces.

If a case fails, run /eval-and-improve.

Agent patterns

The bundled agents demonstrate three patterns to copy:

Pattern	Example	When to use
Runtime tools	`agents/manager.py`	Inspect the runtime directly through AgentOSTools and deployment-check tools.
Source context	`agents/engineer.py`	Let the agent choose its own source reads and searches through WorkspaceContextProvider in tools mode.
Studio builder	`agents/builder.py`	Create and refine runtime components from chat; archive and delete retain confirmation gates.

Scheduled tasks

The scheduler is on by default. Two reference workflows are registered out of the box:

Workflow	What it does	Default
Deployment check	Daily readiness report: database, auth, scheduler, MCP, Slack config. Fixed checks, no LLM calls.	On. Disable with `ENABLE_DEPLOY_CHECK=False`.
Run evals	Daily smoke-tag eval run. Uses model calls.	Off. Enable it from the AgentOS UI.

Keep scheduled evals disabled on a platform receiving concurrent writes. Use a dedicated test platform or an idle window with exclusive access to the stores, for the same cleanup reason described above. Startup reapplies ENABLE_DEPLOY_CHECK; it preserves the enabled state of an existing run-evals schedule.

See Scheduler for the cron API.

Next steps

Task	Guide
Choose a Starter	AgentOS Templates
Connect coding clients	Connect Your Clients
Add or customize evals	Evals