The Agent Platform template is a foundational codebase for an agent platform. FastAPI on port 8000, Postgres for sessions and memory, Docker for local, Railway for production, two reference agents, and a set of Claude Code prompts that create, improve, and eval new agents. Once it’s running, ship a new agent without writing code. Claude Code uses the prompts inDocumentation Index
Fetch the complete documentation index at: https://docs.agno.com/llms.txt
Use this file to discover all available pages before exploring further.
docs/ to generate the agent file, register it, restart the container, and smoke-test it. Then it queries the running platform’s traces to recursively improve what it built.
Why an agent platform
Every team running agents in production hits the same shape of problem: agents need a system to run on. Sessions live somewhere. Traces live somewhere. Tools and credentials live somewhere. Without a platform, each new agent stitches its own version of the same six concerns. With one, you build agents and the platform handles the rest.What an agent platform needs
| Layer | Responsibility |
|---|---|
| Runtime | The service that runs agents. SSE streaming, sessions, scheduling, RBAC. |
| Storage | Sessions, memory, knowledge, traces, eval history. One database. |
| Connectors | Tools, MCP servers, APIs, CLIs the agents reach out to. |
| Interfaces | Slack, Discord, Telegram, custom UIs. One place to resolve user identity. |
| Infrastructure | Where it all runs. Docker locally, Railway (or any container host) for prod. |
What you’ll build
This tutorial takes you from clone to a deployed agent platform in six steps:| Step | What happens |
|---|---|
| Setup | Run AgentOS and Postgres locally with Docker Compose. |
| Create an agent | Claude Code generates a new agent from a prompt. |
| Improve an agent | Claude Code reads live traces and iterates. |
| Evals | Lock in behavior with regression tests. |
| Deploy to Railway | One command to provision Postgres, app, and a public domain. |
| Next steps | Teams, workflows, scheduling, and Slack interfaces. |