Workflows
This section turns individual Solo features into repeatable ways of working. Follow practical playbooks for daily operations, debugging a live app, building and reviewing changes, handing off long-running work, and coordinating multiple agents.
Daily operating patterns
Solo is built for days where you are carrying several projects, local services, terminals, and agents at once. Use the sidebar to see the state of your work, the command palette to…
Build, review, and land one change
The most reliable agent workflow is a small loop: define one change, implement it, review the exact result, fix anything real, run the project gate, and land only that slice. Solo…
Debug a live application with an agent
When a local app is failing, the fastest useful agent is often the one that can see both the code and the running process. Solo lets a lead agent inspect command status and output,…
Run an independent review panel
Some decisions benefit from more than one review, especially when correctness, product behavior, test strategy, and maintainability pull in different directions. Solo can run sever…
Hand off long-running work between agents
A long project should not depend on one agent's context window, quota, or terminal session. Solo gives the project a durable memory layer so you can stop an agent, launch a differe…
Scratchpads and todos as agent memory
Scratchpads and todos give Solo agents a project memory layer that survives chat history, agent restarts, and handoffs. Treat them as tools you can ask your agents to maintain: scr…
Agents spawning agents
Solo agents can delegate work to other Solo agents. The important part is that delegation is not limited to the same agent tool, model, provider, or lab.
Agent orchestration workflow
Solo lets one lead agent coordinate several worker agents in the same project. Treat the lead agent as the orchestrator: it interviews you, writes the plan, creates todos, dispatch…
Are you an agent? Read this doc via API: /api/v1/docs/workflows