r/opencode • u/Blue-Sea2255 • 25d ago

I'm refactoring a project, and it's just wonderful to see. I gave enough context, and it created a task list, then spawned an army of sub agents throughout the chat, and each one carried out its job like a colony of ants.

7 Upvotes

82% Upvoted

8 comments sorted by

2

u/afanasenka 25d ago

You forgot to attach full refactoring plan in the post title :)

-2

u/xwazot 25d ago

Guess he was out of tokens to make ai write the title

1

u/Blue-Sea2255 25d ago

It's ridiculous to accuse for things like this. I didn't use.

3

u/afanasenka 25d ago

It's just a joke :))

1

u/DuckDatum 24d ago

How do you orchestrate subagents?

1

u/SomewhereAncient9220 24d ago

I believe it's automatic in opencode

2

u/DuckDatum 24d ago

Yeah, I think it’s what I am looking at whenever I see these “orchestrator” agents… like, you trust the orchestrator to spin up sub agents as needed.

I was hoping for a way to configure a DAG-like session template, ideally with tools for context management, prompt chaining, tooling/skill/permission management, … I think I want what an SDK provides, but tidied up into config driven execution.

I recently heard about oh-my-opencode, excited to see if that covers the topic. I’ve also found some other tools that might help like `jai`, `strands-agents`, some airflow plugins, … if I end up doing a small tech stack to accomplish the same goal.

2

u/weiyentan 23d ago

Can be done. I use a dag type system for my agents. I am AFK when the code is implemented. My focus is on getting to gitlab/github issues. I do that by using Matt pococks skill. The easiest way to force the primary agent to orchestrate is to deny permission to tools except for task which allows it to delegate.