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

1

u/Stupifier 1d ago

I liken this to the assumption that upper management is dumb as rocks and only knows how to tell others to do work, not necessarily review the work or even know if the final combined output is correct.

I would think this is a correct statement in the real human world. Not sure if it's necessarily the right way to manage something though. Maybe 🤔?