OpenCode subagents
In my experience, I've gone back to basics and want to make them really good before going back up to multi-agent. This is why I'm using opencode now, one top-level agent, no message passing. Scion can then run these OC agent trees and they can send messages to each other. If you don't have the basics in a good place, they will go off the rails and you will burn more tokens.
There are some opencode plugins that take things further. Keeps things simple and understandable first, then move up the stack. (imo)
Yes: the subagent couldn't talk to the parent anymore after a first return to it, but that didn't matter. That I could beget new useful interact able agents was amazing.
I'm mad and bitter angry and won't ever stop being mad until opencode or I fix it so that opencode really has multiple agents that can work with each other, and that I can work with.
I started doing some work on message passing mailbox systems, alike many of the other great https://github.com/joelhooks/swarm-tools or https://github.com/Dicklesworthstone/mcp_agent_mail_rust efforts , but super trailed off.
I have high interest in scion too! I love the robust platform underneath. Yes please. I've spent a lot of time digging into the opencode data model underneath, & it's a moving inplementation defined system. Making the pieces of the system concrete like Scion has feels like a superpower.
davidjkim•1h ago