Managed agents launch as Codex even when the workspace specifies Claude

[yousef20920]

Summary

During production verification of a workspace created from CoDevOrg/CoDev, the workspace URL included codevDefaultAgent=claude, but all three managed agent cards in Mission Control displayed the provider as Codex.

Steps to reproduce

1. Create or open a workspace for CoDevOrg/CoDev.
2. Start a managed CoDev agent.
3. Inspect the agent card in Mission Control.

Actual behavior

The workspace is configured with Claude as the default agent, but the managed sessions launch and are labeled Codex.

Expected behavior

Managed agents should honor the workspace/provider configuration, or the UI should clearly expose and confirm which provider will be used before the session starts.

Verification context

• Environment: production (trycodev.com)
• Repository: CoDevOrg/CoDev
• Observed with three managed agent slots active
• No credentials were changed during verification

[Keesan12]

The agent launching as the wrong model when you specified something else means the scope contract isn't being enforced before the run starts.

We set an authority manifest before every run that includes which model is authorized. If it starts with the wrong one, it stops before doing anything. martin-loop on npm, open source.