Terminal workspace
A real terminal in the app, with team shells, local shells, history and autocomplete.
Switching between the agent UI and your own terminal means losing the thread of what the agents just changed.
Agents run commands and so do you — in the same window. Open a shell scoped to a team's workspace or a plain local shell, keep persistent history across restarts, and use autocomplete that knows your project. No alt-tabbing to check whether the build actually passed.
- Team-scoped and local shells side by side
- Persistent history across restarts
- Autocomplete aware of the project
- Configurable shell, font and env
- See agent commands and yours in one place
Workflows that lean on terminal workspace
- For anyone who inherited the code
Refactor a legacy codebase without breaking it
Split the refactor across agents, block risky work behind tests, and review every diff before it lands.
- For the person who has to fix the number
Raise test coverage on a project nobody tested
One agent per module, tests written in parallel, every suite run in the built-in terminal before review.
- AnswerHow many agents should I run at once?Start with three: a lead, a builder and a reviewer. Add builders only when the board shows cards waiting in assigned rather than in review. Most people over-provision builders and end up bottlenecked on review instead.
- Use caseRun several teams like departmentsNest teams into an org, watch every board on one map, and route work between departments.
- Use caseShip a product as one person with a team of agentsStart in solo mode, promote to a team when the work outgrows one agent, and keep the spend capped.
Stop being the message bus.
Install it, open a repo, and give three agents an objective. Free, no account, no API key.