@christophrumpel@aarondfrancis Where do you see that? Also, consider joining https://t.co/SSG0RXqF5W, would be easier to help out real time instead of X posts.
@christophrumpel@aarondfrancis But in simple terms you could just tell your agent:
"Use Solo MCP to spawn 2 claude agents and tell them to review {something}".
You can right click other agents/todos/scratchpads etc and "Copy link". Give that to your agent and it will be able to read/use it.
@christophrumpel@aarondfrancis Solo gives you primitives to set up your own workflow, so you have to think about it on a lower level.
I have created a skill for myself: https://t.co/GRIqe0Aiq3
It's opinionated to fit my needs as I have created separate agents in solo to spawn exactly what's needed:
@Stammy@aarondfrancis That's the thing though, you'd still be using cc/codex apps, but you can do it through solo. Included MCP opens a lot of possibilities to orchestrate your agents.
@AArdvarkErick@aarondfrancis@Stammy I think you just haven't seen it's true power. It has an MCP and you can achieve full multi-agent orchestration. Scratchpads, todos, timers all available via MCP. Agents can talk to other agents. Imagine claude talking to codex and what not.
131: Crush My Competitors
https://t.co/pc3ktBR9uR
@IanLandsman & @aarondfrancis talk about what's cooking with Solo, why Aaron's hiring his first full-time employee, Ian's frustrations with moving the team to Codex, and a feel good AI story.
@mark_a_phelps@aarondfrancis Solo MCP is amazing! Docs have a guide, but in general it exposes tools to let your agents read and write to other Solo processes. Imagine claude talking to codex or any other harness/model.
https://t.co/oXK8hT2ArF
Here's a perfect example of when I use Solo's scratchpads.
I had @AmpCode do a bunch of research on how to implement live light/dark theme switching in terminals, but turns out I'm not ready to do it yet.
Instead, I had it write all the research to a scratchpad for later!