Not an IDE. On purpose.
Run Claude Code, Codex, and Gemini CLI alongside your dev server, queue workers, databases, and interactive terminals.
The Issue
Claude Code in one tab. Codex in another. Amp in a third. npm is maybe running. The queue worker crashed twenty minutes ago but nobody told you. You have nine terminals open and you can't remember what's running in any of them.
Something needs your attention. Is it terminal three? Five? You're clicking through all nine trying to find the one that's screaming. By the time you find it, another terminal has rung a bell.
Your AI agent can't see your process output. It doesn't know your dev server crashed ten minutes ago. It's generating code against a stack that isn't even running. Garbage in, garbage out.
You're running three agents and a full dev stack. Green? Red? Running? Crashed? You have no idea without checking each terminal one by one.
The Fix
Run any CLI agent right alongside your dev stack. Solo auto-starts your stack, restarts crashes, and gives your agents visibility into your logs and process state via MCP.
Works with any stack
Auto-detects processes for:
Runs your agents and your dev stack together. No bloat, no configuration rabbit holes.
Add Claude Code, Codex, Gemini, Amp, whatever agents you need. Define your dev stack and hit play. Everything spins up together. When you're done, shut it all down with one click.
No more opening six terminals and trying to remember what this project needs.
Dev servers die. Solo notices and restarts them automatically. Set up file watchers so code changes restart the relevant process too.
Your AI agent won't generate code against a server that silently crashed 20 minutes ago.
Green means running. Red means crashed. See your agents and your entire dev stack in one dashboard. No clicking through terminals or guessing.
If something's wrong — agent or process — you'll see it.
Commit your solo.yml to the repo and everyone gets the same stack — including which agents to run. No more outdated READMEs or Slack messages asking how to set up the project.
New teammate? They're running the same agents and stack in minutes.
Why Solo
Your agents need a reliable terminal workspace. Solo gives them one.
Solo speaks MCP. Your AI agents can read logs, see process status, and restart crashed services — without you lifting a finger. Context-aware agents write better code.
❯Restart the queue worker and show me the output
●Solo MCP(restart_process)
└ process: "queue:work"
✓Process restarted successfully
Claude Code, Codex, Gemini CLI, Aider, your own scripts — if it runs in a terminal, it runs in Solo. No built-in models, no vendor lock-in. Use whatever agent is best for the job.
Type directly into running agents and processes. Respond to Claude's prompts, interact with your Rails console, or attach a debugger — all without switching windows. Smooth rendering with full ANSI support.
Everything in Solo is accessible via keyboard. Open the command palette, jump between projects, start and stop processes.
Check in your solo.yml and give your team a shared source of truth — including which agents to run and how. Everyone gets the same commands, agents, and terminal workflow in seconds.
Built with Tauri, not Electron. Solo is a lightweight native terminal workspace, not a 500MB IDE replacement. It runs your commands, agents, and terminal sessions without getting in the way. Your editor stays your editor.
Quality of Life
Details you'll appreciate every day. Polish that shows someone actually uses this.
Solo exposes your processes, logs, and project state to AI agents via MCP. Let Claude or other AI tools help debug and manage your stack.
Set your default editor and open any project directly. One click to VS Code, Zed — whatever you use.
Built with Tauri, not Electron. Around 25MB download. Uses less RAM than a single Chrome tab.
If your solo.yml changes after a git pull, Solo asks you to confirm before running anything. No surprises.
Light mode and dark mode included. Your terminal workspace doesn't have to clash with your setup.
Launch projects, start processes, and manage your stack from Raycast. (Pending Raycast Store approval.)
Solo works wherever you work. Mac available now, Windows and Linux coming soon.
Every feature included in Free. Most developers never need Pro—upgrade only when you need more than 4 projects.
FreeFull-featured. No trial. Never expires.$0forever
Up to 4 projects
Up to 20 processes total
All features included
MCP integration for AI agents
Native notifications
All future updates
ProUnlimited projects. Unlimited processes.$99/first year
then $69/year
Everything in Free
Unlimited projects
Unlimited processes
Priority email support
Activate on 3 devices
All future updates
30-day money-back guarantee. Cancel anytime.
Warp is a terminal replacement with a built-in agent. Solo is a native terminal workspace for agents, project commands, and shell sessions. No built-in editor, no lock-in. You can keep your current terminal if you want, but Solo also gives you built-in terminals and shell integration. Read the full Solo vs Warp comparison.
No. Solo just runs your local CLI tools and lets you interact with them. However you have your agents set up on your machine is exactly how they'll work inside Solo. Your keys, your config, your auth. Because Solo never touches your API keys or agent accounts, there's no risk of getting flagged or banned by any provider.
Mac now, Windows and Linux coming soon. Solo is a Tauri app. Small, fast, and uses your system's native webview. See the download page for the latest platform availability.
All processes stop — agents, project commands, and shell sessions alike. Solo is running the workflows in that window. When you're done working, close it and everything shuts down cleanly. No orphaned processes running in the background.
Yes. Commit your solo.yml to your repo and everyone on the team can spin up the same stack.
Yes. If you create a process locally and want to add it to your solo.yml, that's one click. Same if you want to take a shared process and make it local.
The free tier is the trial, except it never expires. You get 4 projects and up to 20 processes total. Use it as long as you want.
Because Solo is a joy to use. No config files to maintain, no manual restarts, no juggling terminal tabs. MCP integration so your agents can see your logs, desktop notifications when things crash, and a UI that actually looks good. Free tools work. Solo delights.
Yes, up to three machines per license.
We use Aptabase for privacy-first analytics. Basic usage stats only. We never send project names, process names, or anything about your code. Solo also checks license data to validate paid accounts. That's it.
Aaron Francis, creator of faster.dev. I built it because I was running Claude Code alongside my dev stack and juggling nine terminal tabs. Now I don't have to.
Yes, any CLI agent that runs in a terminal runs in Solo. All the CLIs that exist today and the ones that will undoubtedly come out in the coming months, you can run inside of Solo from day one. No updating required.
No. Solo manages processes, not containers. If your workflow uses Docker, Solo runs alongside it. Add docker compose up as a process and Solo monitors it like anything else.
Solo tracks PIDs of all running processes. On restart, it detects orphaned processes and shows a dialog to kill or reattach them. No zombie processes eating resources in the background.
Solo never auto-runs something you didn't add yourself. If your solo.yml changes (like after a git pull), Solo asks you to confirm before running anything. No surprises.
Yes. You can define local processes that don't get committed to the repo. Your personal stuff stays personal.
Updates are free forever. The only restriction on the free tier is the number of projects and processes you can have, not whether you get updates. You can also follow the changelog.
Free tier: 4 projects, up to 20 processes total. Pro: unlimited projects and processes.
Yes. Solo validates your license once then caches it locally. You get a 14-day offline grace period before it needs to check in again. Your configs are plain text solo.yml files, portable and readable by anything.
Yes. Light mode and dark mode, plus a system option that follows your OS preference.
Haha, no. Solo is a native Tauri app — 25MB, no Electron, no bundled Chromium running a text editor. It uses your system's native WebKit and does one thing well: run your agents, project commands, and terminal sessions from a single window.