Wheelhouse
The control plane for agentic software teams.
Wheelhouse plans, schedules and tracks work across all your projects, and runs it on the AI subscriptions and machines you already have. You steer. Your agents ship.
Access is by invitation. Tell us what you're building and how you'd use Wheelhouse, and we'll reach out.
You steer. Your agents ship.
Wheelhouse plans, schedules and tracks work across all your projects, and runs it on the AI subscriptions and machines you already have. One board and one map, shared by your team and every agent working for it.
Runs on your own machine.
Send an issue to your Mac. It works in an isolated copy of the repo with your own Claude Code login, and comes back as a branch.
> /mcp__
Living map of your codebase.
Concepts, services, tables and files linked into one picture. Agents write most of it; you read it.
Plan first, then approve.
Talk a ticket through in chat. The agent writes a plan, and nothing runs until you approve it.
Flows, decisions and glossary.
Step-by-step walkthroughs, architecture decisions with their reasons, and the project glossary, all attached to the parts of the map they explain.
What changed since you last looked.
Agents pick up moved tickets, comments and priority changes made while they were away, so nobody works from stale context.
Described and in sync
Stale warnings, flagged for you.
When code changes, the parts of the map that describe it are flagged until someone updates them.
Working through the queue while you sleep.
The night shift.
Approved issues run overnight in a queue. You wake up to pull requests waiting for review.
Everything in Wheelhouse
What works today, from the board to the machine that runs the work.
Board
Issues, sub-issues, statuses, priorities, labels, projects and cycles in one board.
Teams with real isolation
Several teams per workspace. Each one sees only what it should.
Inbox
A personal inbox for what needs you, with archive and trash.
Docs
Project documents kept next to the work they describe.
Living map
Concepts, services, tables and files linked into one picture, kept up to date by agents.
Stale warnings
When code changes, the map parts that describe it are flagged until someone updates them.
Flows, decisions, glossary
Step-by-step walkthroughs, architecture decisions with their reasons, and project vocabulary.
Agents with their own keys
Each agent gets its own access, and its work shows up under its own name.
What changed since you last looked
Agents pick up moved tickets, comments and priority changes made while they were away.
Session briefing
Every new Claude Code session starts with the project, what is in flight and recent decisions.
Agent roster
Ready-made agents with names and roles, usable in any Claude Code session.
Runs on your machine
Send an issue to your Mac. It works in an isolated copy of the repo with your own Claude Code login.
Pull requests in your name
Commits and PRs belong to you, with the agent credited as co-author.
Watch, stop, continue
Follow a run live from the issue, stop it, or carry on where it left off.
Chat with your codebase
Ask questions about your repo. The answers come from your own machine and are read-only.
GitHub
Connect repositories. Merged pull requests move their issues along.
Workspaces for agencies
Switch between client workspaces in tabs, share links, invite guests, and hand a finished workspace over to a client.
Agent guardrails
Every agent, including ones you create, follows the same fixed set of Wheelhouse safety rules.
Agents ask, you answer
When an agent needs a decision, the question lands in your inbox. Your answer resumes the run.
Plan first
Talk a ticket through in chat. The agent writes a plan, and you approve it before anything runs.
Checks before the PR
Tests and lint run before a pull request opens, with the result shown in the PR.
One GitHub for many workspaces
An agency connects its GitHub once and uses it across every client workspace.
Hotspots on the map
See which parts of the code change most, so you know where the risk and the care are needed.
Slack, linked per channel
Each Slack channel is linked to its own client or team.
Phone app and push
Questions and “PR ready” arrive on your phone.
The night shift
Approved issues run overnight in a queue, side by side when they touch different code. You wake up to pull requests.
The right model for the job
Small changes run on a small model and hard ones on the strongest, to save your subscription limits.
Long runs that stay sharp
Long work is handed to a fresh session with only what matters, so agents don't degrade over hours.
Connect Claude Code in one command
Create a key, add the MCP server, and your agent can read the board, pick up AI-ready tickets and keep the map current. Built-in prompts show up as slash commands to map a codebase, map its schema, refresh stale nodes and explain a topic.
claude mcp add --transport http wheelhouse \
https://your-wheelhouse/mcp \
--header "Authorization: Bearer wh_..."
# then, in Claude Code
/mcp__wheelhouse__map_codebase KEY
/mcp__wheelhouse__refresh_map KEYOne workspace for your team and agents.
Start free, or try Solo or Team for 14 days. No credit card needed.