Solo

Solo is a desktop application for managing coding agents and project-scoped coordination state. If the user asks Solo to do something, use the Solo MCP server and its enabled feature tools. Do not defer to, check, or invoke a Solo CLI.

Pi behavior

If running under Pi, detected by PI_CODING_AGENT=true, use the pi-soloterm extension tools for Solo MCP server features:

• solo_status — verify SoloTerm/MCP availability, identity, and feature support.
• solo_task — spawn Solo-managed coding agents/processes and send them prompts.
• solo_scratchpad — list, read, or write Solo scratchpads.
• solo_todo — manage Solo todos when available, with Pi session fallback.

When a user asks to use Solo MCP in Pi, call solo_status first. If it reports ready/available, proceed with the relevant solo_* tool. Do not say Pi lacks MCP support when these tools are available; pi-soloterm is the bridge.

If a required solo_* tool is missing, tell the user to install/enable pi-soloterm. If solo_status reports Solo MCP unavailable, tell the user to run Solo and enable Settings → MCP.

Non-Pi behavior