Steering a managed agent fails when the OpenAI connection is revoked

[yousef20920]

Summary

During production verification, steering a running managed agent failed even though the agent was shown as working in Mission Control.

Steps to reproduce

1. Open a production workspace for CoDevOrg/CoDev.
2. Start a managed agent.
3. Open Mission Control and select Steer.
4. Submit a harmless read-only instruction.

Actual behavior

The UI reports:

Could not steer this agent
This OpenAI connection was revoked or is not connected. Reconnect a key in Settings before starting another turn. The existing session is unchanged.

The instruction does not execute and the agent provides no response.

Expected behavior

The provider connection should be validated before launching the session, and the UI should either:

• route the session through the configured provider,
• provide a clear reconnect flow before the agent starts, or
• fail with an actionable setup state instead of presenting a working agent that cannot be steered.

Verification context

• Environment: production (trycodev.com)
• Repository: CoDevOrg/CoDev
• Observed on a managed Codex session
• No credentials were changed during verification