
The agentic metaharness
Coding agents are getting good. The annoying part is everything around them: the tabs, logs, dev servers, half-finished plans, and other agents you forgot were still running.
Solo Blog
Coding agents don't work alone. They need dev servers, logs, project context, and sometimes a few other agents. This is where we write about that whole system: what works, what breaks, and what we're learning while building Solo.
Latest
Practical writing about agent workflows, local tooling, and keeping the work visible.

Coding agents are getting good. The annoying part is everything around them: the tabs, logs, dev servers, half-finished plans, and other agents you forgot were still running.
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 →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.”