Run OpenCode with your dev server and queue worker in one Solo project.
Launch OpenCode from the agent picker, add your development commands, and connect Solo MCP. OpenCode can then inspect command output without asking you to copy logs into its conversation.
Use an existing Laravel project for this setup. You need an npm dev script and an asynchronous queue connection. By the end, OpenCode can inspect both commands through Solo MCP.
Run the version command below in your project shell. It prints the installed OpenCode version. If the command is missing, follow the OpenCode installation instructions.
Complete model provider setup in OpenCode before continuing. Solo launches the installed CLI and uses your existing provider account.
Check the command in your project shell
opencode --versionAdd your repository to Solo. In Settings > Agents, enable OpenCode and check its installation status. Launch OpenCode from the project agent picker. Its session appears in the project sidebar.
Use the agent picker to launch OpenCode. The solo.yml file configures commands such as servers and workers.
If either service is already running, use that process. Otherwise, save this solo.yml in the project root. Review and trust the imported commands, then start Web and Queue from the sidebar.
Queue restarts after it exits or a job file changes. File-watch restarts can interrupt jobs, so use a development queue. These settings apply to Queue and do not restart OpenCode.
solo.yml for an existing Laravel project
name: Storefront
processes:
Web:
command: npm run dev
auto_start: false
Queue:
command: php artisan queue:work
auto_start: false
auto_restart: true
restart_when_changed:
- app/Jobs/**/*.phpIn Settings > MCP, enable Solo MCP. Follow the generated OpenCode setup for your installation, then reconnect the client as instructed.
Send the prompt below. OpenCode should report the status and recent output of Web and Queue. If Solo tools are unavailable, check the MCP connection. If a service command is missing, check the project shell path.
Check the running commands
Use Solo MCP to inspect Web and Queue in this project.
Report their status, recent output, and any errors.
Do not start or restart processes, or edit files.Use the process check in step 4 before asking OpenCode to change application code. Confirm that it can read the output of the services you expect it to use.
Compare the products and workflows closest to OpenCode, including where Solo fits.
Start with one project and a small task. These guides walk through the setup and what to check when the work finishes.
Set up both tools in one project, give one agent implementation work, and ask the other to review the diff.
Read the guide →Give a lead agent a plan, shared todos, and a scratchpad so workers have clear assignments and a useful handoff.
Read the guide →Put a Laravel server, Vite, and a queue worker in solo.yml, then manage their output and restart behavior in Solo.
Read the guide →Solo is a lightweight desktop terminal workspace for local agents, project commands, interactive terminals, and long-running services. It sits beside your editor, keeps your stack visible, and gives Claude Code, Codex, and the rest of your tools one shared local control surface.
Solo is built by Aaron Francis, creator of faster.dev and Database School, and VP of Marketing at Laravel. He built Solo after running Claude Code alongside his own dev stack and getting tired of juggling nine terminal tabs just to keep local agents, services, and project commands visible.
He is also a dad to two sets of twins, which tends to create a strong preference for software that reduces chaos instead of adding more of it. That is why Solo keeps showing up in these comparisons as the local workspace around your tools, not another editor or orchestrator trying to absorb the whole workflow.
Free for four projects on macOS and Windows.
Start with a terminal and add the programmable meta-harness when you need to coordinate agents with your local development stack.
“I can't live without it.”
