Summary
During production verification, one working managed agent displayed no way to open its worktree from Mission Control, while other working managed agent slots exposed an Open this worktree action.
Steps to reproduce
- Open a production workspace for CoDevOrg/CoDev.
- Start three managed agents.
- Open the first agent in Mission Control.
- Compare its worktree action with the other managed agent cards.
Actual behavior
The first agent was shown as WORKING with a managed session and an active read-only instruction, but its action was disabled and labeled:
Nothing to open
This agent has no open chat or worktree to step into.
Other managed agent cards exposed Open this worktree and showed distinct clean agent branches in Source Control.
Expected behavior
Every managed agent that owns a worktree should expose a reliable way to open or inspect that worktree. If the worktree is not yet available, the UI should show a clear provisioning state and make the action available once ready.
Verification context
- Environment: production (trycodev.com)
- Repository: CoDevOrg/CoDev
- Three managed agent slots were allocated
- Slot 2 and slot 3 exposed distinct branches; slot 1 did not expose a worktree action
Summary
During production verification, one working managed agent displayed no way to open its worktree from Mission Control, while other working managed agent slots exposed an Open this worktree action.
Steps to reproduce
Actual behavior
The first agent was shown as WORKING with a managed session and an active read-only instruction, but its action was disabled and labeled:
Other managed agent cards exposed Open this worktree and showed distinct clean agent branches in Source Control.
Expected behavior
Every managed agent that owns a worktree should expose a reliable way to open or inspect that worktree. If the worktree is not yet available, the UI should show a clear provisioning state and make the action available once ready.
Verification context