Agents
Agents are AI coding sessions that run alongside your project commands and terminals. This section covers setting up agent tools, launching and resuming sessions, understanding idle detection and summaries, and connecting agents to Solo through MCP.
What are agents?
Agents in Solo are AI coding tools that you configure in Settings → Agents and launch inside a project. Regular commands stream terminal output and can also accept terminal input.…
Setting up agent tools
Before you can launch agents from Solo, you need to tell it which tools are available. You do this in Settings → Agents.
Adding custom agents
Solo lets you add the same agent CLI more than once, each time with a different name and set of default arguments. Think of these as reusable launch presets: one installed tool, se…
Agent installation health
Solo checks whether each agent tool's CLI is actually installed and working, and shows the result in Settings → Agents. Health helps decide which agents are offered for launch. The…
Launching agents in a project
Agents always launch inside a project context, opening in that project's directory and giving them access to your code and files.
Stopping and resuming agents
Stopping an agent ends its running CLI process but keeps the agent in Solo. If Solo has captured the provider's session ID, you can resume that exact conversation later instead of…
Auto-summarization
Solo can generate a sidebar-visible, compact summary after recent activity in an agent or terminal. This gives you a quick way to catch up without re-reading the full output.
Agent idle detection
Solo tracks agent state so you can tell which agents are working, idle, waiting for permission, or blocked by an error.
Closing agents
Closing an agent removes it from the sidebar and ends its process if it's still running. This is different from stopping an agent, which keeps the row and any saved resume identity…
Are you an agent? Read this doc via API: /api/v1/docs/agents