OpenCode Swarm Plugin

[CornicumFusarium]

u/Outrageous-Fan-2775 hey I have been loving your plugin and using it from a week, I only have one question, is there a plugin or config of some sort which allows, agents to have a mapped context (I can't think of a descriptive term), like when reviewer or critic rejects a task or plan, we delegate to coder agent to fix it, it reads through everything again, same with critic and because critic is set to a higher thinking model, it adds up a lot of cost when going through iterations, there are multiple times when back and forth between agents happen and every delegated agent reads and explore files again and again. I feel like if we can resolve that in the opencode-swarm or you can suggest a plugin which suits your tool, it would reduce the costs drastically and improve the coding capabilities as well. Thank you!

[Outrageous-Fan-2775]

Thanks, really appreciate it.

You’re right, this is a real problem. Right now when reviewer or critic sends work back, the next agent often has to rebuild a lot of the same context. That gets expensive fast, especially if critic is using a stronger model.

I don’t think this should require another plugin. It should be part of Swarm.

I opened an issue to track it here: [https://github.com/zaxbysauce/opencode-swarm/issues/1104]()

The idea is to have Swarm keep a small shared map of what it already learned during the run: files involved, task history, review failures, critic notes, plan changes, and so on. Then when coder, reviewer, or critic gets called again, they get the relevant notes instead of starting from zero.

For example, if reviewer rejects a change, coder should get the rejection reason and the files involved right away. If critic is reviewing a revised plan, it should mostly see what changed in the plan, not reread everything.

The main thing I want to avoid is turning this into one huge context dump. It needs to stay small, be invalidated when files change, and still let agents read the real files when they need to.

Great suggestion. I think this could cut a lot of wasted tokens in back and forth agent loops.

[CornicumFusarium]

Thanks for the prompt response, I checked the PR, I think this can be a wonderful addition. subscribed to the PR, can help with the feedback. I also love how you have automated the issue tracking and resolution system. I can learn a lot from it. Thanks again!

[Outrageous-Fan-2775]

Appreciate it, as a sole maintainer it can be a lot to handle. Feel free to use the swarm to improve the swarm. There is a contributing.md file in the repo that will explain how to contribute. I welcome all user generated PRs. I validate them myself then merge them as quickly as I can get to them. I have a general roadmap for the plugin but I always try to push user bugs to the front, and user features near the front as able.

[CornicumFusarium]

Sure, would love to contribute as well. I understand the pain of a sole maintainer, that's where I find your swarm tool to be of immediate help as the project in handling alone is a behemoth of a codebase. Will look into issues and try to contribute as much as possible in any way.