Solo
  • How it works
  • Orchestration
  • Pricing
  • Compare
  • Agents
  • Blog
  • Docs
  • Login
Download Solo download
Docs home

Product docs for Solo's desktop workflow: setup, projects, commands, agents, notifications, and troubleshooting.

Getting started

Installation and system requirementsFirst launchThe demo projectInterface overviewUnderstanding projects, processes, and sections

Projects

Creating and loading projectsCommand auto-detectionsolo.yml overviewProject icons, names, and customizationProject context menuReordering projects and sectionssolo.yml change notifications

Workspaces

Workspaces overviewManaging workspacesMultiple windows

Commands

Adding and removing commandsStart, Stop, and RestartAuto-startAuto-restartFile-watch Auto-restartStatus IndicatorsRenaming commandsReordering CommandsLesser-used CommandsOrphaned ProcessesTrust and Security

Agents

What are agents?Setting up agent toolsAdding custom agentsAgent installation healthLaunching agents in a projectStopping and resuming agentsAuto-summarizationAgent idle detectionClosing agents

MCP tools

MCP tools overviewProject MCP toolsWorkspace MCP toolsServices MCP toolsProcess MCP toolsBulk MCP toolsOutput MCP toolsAgent and terminal MCP toolsCoordination MCP toolsSetup and support MCP toolsScratchpad MCP toolsTodo MCP toolsPrompt template MCP toolsTimer MCP toolsKey-value MCP toolsMCP prompts and resources

Workflows

Daily operating patternsBuild, review, and land one changeDebug a live application with an agentRun an independent review panelHand off long-running work between agentsScratchpads and todos as agent memoryAgents spawning agentsAgent orchestration workflow

Todos

Using todosTodo agent tools

Scratchpads

Using scratchpadsScratchpad agent tools

Prompt templates

Prompt templatesCreating and editing templatesPlaceholdersUsing templates

Terminal

Terminal basicsTerminal control barTerminal context pinsTerminal keyboard inputTerminal mouse ownershipTerminal focus behaviorSearching terminal outputTerminal reattach behaviorFollow output and jumping to bottomTerminal session persistenceTerminal right-click menuOSC, links, and Kitty keyboard protocol

Sidebar

Understanding sectionsFiltering the sidebarProcess favoritesCPU and memory statsCollapsing and expanding sectionsReordering sectionsSection splash screens

Activity

Activity monitor

Keyboard shortcuts

Default keyboard shortcuts referenceSidebar keyboard navigationSwitching projects and commandsCustomizing keyboard shortcuts

Notifications

macOS notification permissionsIn-app toast notificationsNotification indicatorsAuto-restart notificationsBell soundsTriggering notifications from scripts

Environment

Shell environmentExecution profilesVersion managers

Integrations

MCP server integrationHTTP APIDeep links

CLI

Solo CLI overviewProjects and processes from the CLITodos and scratchpads from the CLIJSON output and scripting

Settings

Settings overviewTools: editors, terminals, and browsersSidebar settings

Appearance

ThemesTerminal font settingsInterface font and scale

Updates

Installing updatesRestarting safely for updates

Account

Free tierActivating a licenseTeam licensesMoving a license to another machineLicense errors

Troubleshooting

Commands can't find tools (PATH issues)Notification troubleshootingResetting settings and stateReporting issues

Command palette

Using the command paletteQuick jumpFocus jumpActions paletteContext actionsNew tab pickerPrompt template pickerNative app menus

Useful links

Download Solo Help Agent workspace Compare Solo Changelog
  1. Docs
  2. Notifications

Notifications

Solo can get your attention without making you watch every terminal. This section covers macOS permissions, in-app toasts, sidebar indicators, auto-restart notices, bell sounds, and notifications triggered by your own scripts.

macOS notification permissions
Solo can send native macOS notifications when events happen while you're away from the app. macOS requires you to grant notification permission before those alerts will appear.
In-app toast notifications
Solo uses in-app toasts for lightweight confirmations and longer-lived alerts that should stay visible inside the app.
Notification indicators
Solo uses small visual indicators to draw your attention to processes that raised a notification or alert while you were focused elsewhere.
Auto-restart notifications
Auto-restart mostly happens quietly in the background. The important notification path is when Solo pauses auto-restart because a command is crash-looping.
Bell sounds
Solo can play an audible bell when terminal notification events fire — things like the classic BEL character (\a) and supported terminal notification sequences.
Triggering notifications from scripts
Your shell commands and scripts can send notifications to Solo directly from terminal output using supported OSC sequences and bell events. This is useful for getting alerted when…

Are you an agent? Read this doc via API: /api/v1/docs/notifications

Solo

Solo is the programmable meta-harness for coding agents that runs every CLI harness beside your dev stack and gives agents shared processes, scratchpads, todos, and control through MCP, HTTP, or the Solo CLI.

Built by Aaron Francis, dad to two sets of twins, creator of faster.dev, and creator of Database School. He built Solo after running Claude Code alongside his dev stack and juggling nine terminal tabs.

Links
How it worksOrchestrationPricingCompareAgentsBlogDocsLoginDownloadHelpChangelog
Legal
Privacy PolicyTerms of Service
Compare

See how Solo’s programmable meta-harness fits around the editors and coding harnesses you already use without replacing them.

Comparisons
All comparisonsSolo vs CursorSolo vs Devin DesktopSolo vs WarpSolo vs Zed
Alternatives
All alternativesCursor AlternativeWarp AlternativeVS Code AlternativeClaude Code Alternative
Solo © 2026 Try Hard Studios, LLCWebsite designed by Quick14
Solo terminal workspace preview