How It Works
Coda is a team of five specialist agents coordinated by a leader:| Agent | Role |
|---|---|
| Explorer | Code search, architecture Q&A, PR reviews (read-only) |
| Coder | Writes code in isolated worktrees, opens PRs |
| Planner | Breaks features into ordered GitHub issues |
| Triager | Labels, comments, closes issues based on code analysis |
| Researcher | Web search for docs, APIs, error messages |
coda/* branches. Your main branch is never touched. Coda opens PRs; humans merge them.
| Capability | What It Does |
|---|---|
| Architecture Q&A | ”How does auth work?” “Where is the model API call?” |
| PR Reviews | Diffs against your conventions, leaves comments |
| Issue Triage | Reads open issues, flags urgent ones |
| Code Writing | Isolated worktrees, never touches main |
Self-Learning
Coda improves without retraining through Agno’sLearningMachine. It picks up your coding standards, conventions, and patterns:
| Week 1 | Week 4 |
|---|---|
| Writes working code using generic patterns | Follows your service layer conventions, uses your team’s error handling pattern, matches your naming style |
Run Locally
See Setup guide for detailed instructions.http://localhost:8000/docs.
Configure GitHub Access
Create a GitHub Personal Access Token with repo access and add it to.env:
repos.yaml:
Connect to the Control Plane
- Open os.agno.com
- Click Connect OS → Local
- Enter
http://localhost:8000
Connect to Slack
Coda is designed to live in Slack as your teammate. Add your Slack credentials to.env:
Deploy to Railway
See Deploy to Railway for JWT setup and production configuration.- Open os.agno.com
- Click Connect OS → Live
- Enter your Railway domain
Example Prompts
Try these after connecting your repos:- How does authentication work in this codebase?
- Review the open PR on feature/new-api
- What are the most important open issues?
- Where is the database connection configured?
- What testing conventions does this project use?