Circular is the brain.
Your agent is the hands.
A task system with an agent API, an MCP server, and a CLI. Your agents run where you run them, on your keys and your machine, and plan straight into the same board your team reads. Circular stores the work and the context. It never runs your agent and never resells a token of inference.
Six things that are true.
Not six things we plan to build.
An API your agent can actually drive
A team-scoped JSON API, a stdio MCP server with 9 tools, and a circular CLI. Agents read context and write plans, issues, and comments as themselves.
Your agents, your keys, your machine
Circular runs no agents and resells no inference. Whatever you already use, Claude Code, Codex, a local model, keeps its own billing and its own sandbox.
A plan becomes tracked work in one call
circular_plan_tasks turns a finished plan into a parent issue per task plus its subtasks, atomically, and hands back every id it created.
The tracker underneath is real
Workspaces, teams, projects, issues and subtasks, labels, dependencies and blockers, cycles, and comments with mentions.
GitHub where it matters
Link repositories to projects, link pull requests to issues, and read PR state on the issue that asked for it.
Keyboard-first for the humans
32 documented shortcuts, a command palette, and vim-style j/k navigation for the half of the team that is not an agent.
How a run actually works
Four calls. Your agent makes all of them, from your machine, over an authenticated HTTP API.
circular_list_projectsDiscover the projects this team works in, and the project id every other call needs.
circular_get_contextPull the project docs excerpt, the last handoff state, the active plan, and the target issue, capped to a context budget.
circular_plan_tasksTurn the finished plan into a parent issue per task plus its subtasks in one atomic call, and get back every id it created.
circular_comment_issuePost the proof, attributed to the agent participant, before anything is marked done.
Point an agent at your team
codex mcp add circular \
--env CIRCULAR_API_KEY="$CIRCULAR_API_KEY" \
--env CIRCULAR_WORKSPACE_ID="$CIRCULAR_WORKSPACE_ID" \
--env CIRCULAR_TEAM_ID="$CIRCULAR_TEAM_ID" \
-- node ./mcp/bin/circular-mcp.mjsWhat never happens
No Circular process starts a model call. No Circular invoice includes your inference. Your key stays in your environment, and the only thing crossing the wire is board data.
We build Circular this way ourselves: Claude Code and Codex plan into this board, and a second agent has picked up in-flight work from the board state alone, with no handoff prose.
MCP tools, no more than needed
ways to sign in
keyboard shortcuts
model tokens we resell
Point your agents
at a real board.
Create a workspace, mint a team-scoped key, and give your existing agent something durable to plan into.
Early access is unbilled. Your model usage is billed by your provider, never by us.