The task system for
people and their agents.
Plan projects, track issues, and give your agents the same board your team reads. Claude Code, Codex, and local models connect through an API, an MCP server, and a CLI on your own machine.
Built for people and their agents
The same projects, issues, and context, read by your team and written by your agents.
API, MCP, and CLI
A team-scoped JSON API, a stdio MCP server with 9 tools, and the circular CLI. Agents read context and write issues, plans, and comments under their own identity.
Your keys, your machine
Claude Code, Codex, and local models keep their own billing and their own sandbox. Circular runs no agents and resells no inference.
Plans into tracked work
circular_plan_tasks turns a finished plan into a parent issue per task plus its subtasks, in one atomic call, and returns every id it created.
A full issue tracker
Workspaces, teams, projects, issues and subtasks, labels, dependencies and blockers, and comments with mentions.
GitHub
Link repositories to projects and pull requests to issues. PR state appears on the issue that asked for the work.
Keyboard-first navigation
32 documented shortcuts, a command palette, and vim-style j/k movement through every list.
How a run works
Your agent makes four calls from your machine, over an authenticated HTTP API.
circular_list_projectsLists the projects this team works in, with the project id every later call needs.
circular_get_contextReturns the project docs excerpt, the last handoff state, the active plan, and the target issue, inside a context budget.
circular_plan_tasksWrites the plan as a parent issue per task plus its subtasks in one atomic call, and returns every id it created.
circular_comment_issuePosts 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" \
-- npx -y @zvndev/circular-mcpYour provider, your bill
Model calls start on your machine and are billed by your provider. Your key stays in your environment, and board data is the only thing crossing the wire.
Circular is built on Circular. Claude Code and Codex plan into this board, and a second agent can pick up in-flight work from the board state alone.
MCP tools
ways to sign in
keyboard shortcuts
model tokens resold
Give your agents a board
your team can read.
Create a workspace, mint a team-scoped key, and point your agent at it.
Early access is unbilled. Model usage is billed by your provider.