What is Coda?
A code companion that lives in Slack and works alongside your team.
Coding agents write code. Coda handles the work around it: PR reviews, issue triage, feature planning, debugging. It lives in Slack as a teammate and works against your codebase on disk.
The system
Coda is a multi-agent system:
| Member | Role | Tools |
|---|---|---|
| Explorer | Reads code, traces call chains | CodingTools (read-only), GitTools, GithubTools, ReasoningTools |
| Coder | Writes code in isolated worktrees, opens PRs | CodingTools (full), GitTools (worktree), GithubTools, ReasoningTools |
| Planner | Breaks features into ordered GitHub issues | CodingTools (read-only), GitTools, GithubTools (issues), ReasoningTools |
| Researcher | Hits the web for framework docs, library APIs, CVEs | ParallelTools, ReasoningTools |
| Triager | Labels, comments, closes issues based on the actual code | CodingTools (read-only), GithubTools (issues), ReasoningTools |
| Leader | Routes the request, posts to Slack | SlackTools |
The Coder works in a coda/<branch> git worktree off main. A human reviews and merges. Coda never merges. Worktrees clean up on restart.
How Coda runs
Code is searched on disk. Grep, find, read against actual files, synced every five minutes. No vector indexing. No stale embeddings. Three scheduled tasks ship by default:
| Task | Cadence | What it does |
|---|---|---|
| Repo Sync | Every 5 minutes | Pulls latest changes from every configured repo |
| Daily Digest | Each morning | Posts what merged yesterday, PRs waiting, issues opened, what's gone stale |
| Issue Triage | Daily | Reviews open issues against the actual code, labels them, posts a summary |
Coda learns your conventions through Kern's Learning Machine. Week 1 you get generic patterns. Week 4 it follows your service layer style, error handling, naming, and logging.
Next
Setup → takes about five minutes and points at the kern repo by default.