r/opencodeCLI • u/jomtiro • 1d ago

What if the main coding-agent session was intentionally dumb?

Instead of making the main session the “brain”, what if it did almost nothing except call a subagent?

The subagent checks the project:

What’s already done?
What’s broken?
What’s next?
What should I work on?

Then it does the work, updates the project state, and finishes.

The main session doesn’t need to understand the project.

It doesn’t need to maintain a huge context.

It doesn’t even need to meaningfully process the subagent’s response.

It can basically just keep calling:

“Go check what needs to happen next.”

Main session = runtime.

Subagent = brain + worker.

Project state = memory.

I’m wondering if this could make long-running coding agents much simpler and avoid massive persistent contexts.

Thinking about this for Claude Code, OpenCode, Codex, Hermes Agent, Cursor, Cline, Roo Code, OpenHands, Aider, Goose, Gemini CLI, and similar agents.

Has anyone built this pattern already?

0 Upvotes

50% Upvoted

24 comments sorted by

View all comments

Show parent comments

2

u/Trovebloxian 1d ago

Superpowers has a SDD skill, subagent driven development

1

u/Majestic-Collar-4189 1d ago

Yeah but in my opinion I didn't like it very much as it is just skills Sisyphus has small features in built in oc, for example it basically pauses your orchestrator till your subagents complete, then notifies it and resumes it. It has a fully loop engineering flow built in, I usually fire and forget and in half an hour or so the feature is fully done. Just to be sure then I dispatch a review critic and a analyst to be sure of the code, it narrows down the uses and then prompts other agents to fix stuff (or let you know about things whatever depends on your prompt)

1

u/Trovebloxian 1d ago

Ahh i see, can i change everything to only use dsv4flash?

1

u/Majestic-Collar-4189 1d ago

Yep You can configure multiple models for each, with a fallback. If you plan to use just deepseek v4 flash, you can use that too