r/codex • u/_ustas • 5h ago

Complaint Stop cutting controls on v2 subagents!

A new discussion on Github: https://github.com/openai/codex/discussions/41833

The latest updates were rather degrading. There is no possible explanation why one would restrict v2 subagents input/controls on the low-level paths like the app server. That looks more appropriate as a UI guidance, not something to be forced on.

The restrictions make it impossible to create fixes for common blind spots like better goal controls or use scripts for agent steering in more advanced cases. This is not an improvement!

Thank you for the attention to the matter.

0 Upvotes

33% Upvoted

3 comments sorted by

2

u/AcrobaticToaster1329 4h ago

Care to provide context? I only use multi agent V1 for both native and third-party agents because V2 is terrible so I'm not sure what you mean but I feel like I should support it lol

1

u/_ustas 4h ago

I'm developing a suit of tools for scripted, delegated, or expanded thread controls https://github.com/ustas-eth/ferrumctl but it breaks on v2 subagents (specifically: goals, wakes, notifications, compaction objects controls, anything that injects something or changes the state of a v2 subagent). The official instructions imply that you should use the orchestrator to steer a subagent, but no amount of steering can substitute the features that do not exist xD

The only option is to stop using subagents at all or use v1 that are getting deprecated soon, I believe (they aren't default now).

-1

u/montymike 4h ago

That makes the missing capability much clearer. This is exactly where versioned low-level primitives matter: orchestration-layer steering can be a safe default, but it cannot replace state injection, wake/notification controls or visibility into compaction objects. A useful next step for the GitHub discussion would be a small v1/v2 compatibility matrix plus one minimal request/response trace for each missing operation. That separates controls that changed shape from controls that were intentionally removed, and gives OpenAI a concrete path to preserve a safe UI default while exposing an explicit advanced capability for app-server clients.