You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[idea] Codex integration: agent-reported state, not only the session
#6018
The managed Codex integration (v10 on herdr 0.9.5) reports the session identity only, so a Codex pane's state comes from screen detection. Some other integrations (opencode, for example) report the agent's own state.
For Codex panes the hardest case to see is "waiting for a person to approve a command": it can look like idle or working, and Codex's TUI changes from release to release.
requested change
Lifecycle state for Codex panes that comes from Codex itself, distinguishing at least working, waiting for a person's approval, and idle, and showing "unknown" when that source is missing or stale. How to get it is up to you.
why you want this
We run Claude Code and Codex side by side and a person answers approval prompts from a phone over SSH. We want the sidebar and agent list to show where a person is needed and which pane has stalled. We don't use the state as permission to type into a pane or to answer a prompt. Related: #4649 (session binding under the shared daemon), #5073 (the same idea for Claude Code via OSC 7501).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
idea / problem
The managed Codex integration (v10 on herdr 0.9.5) reports the session identity only, so a Codex pane's state comes from screen detection. Some other integrations (opencode, for example) report the agent's own state.
For Codex panes the hardest case to see is "waiting for a person to approve a command": it can look like idle or working, and Codex's TUI changes from release to release.
requested change
Lifecycle state for Codex panes that comes from Codex itself, distinguishing at least working, waiting for a person's approval, and idle, and showing "unknown" when that source is missing or stale. How to get it is up to you.
why you want this
We run Claude Code and Codex side by side and a person answers approval prompts from a phone over SSH. We want the sidebar and
agent listto show where a person is needed and which pane has stalled. We don't use the state as permission to type into a pane or to answer a prompt. Related: #4649 (session binding under the shared daemon), #5073 (the same idea for Claude Code via OSC 7501).All reactions