Agent status and notifications
Session Bay shows what each agent is doing next to its tab, in the sidebar, in All workspaces and on attached board tasks:
| Status | Meaning |
|---|---|
| Working | The agent is running a step. |
| Waiting for input / permission | The agent needs an answer from you. |
| Done | The agent finished its turn. |
| Failed | The agent reported an error. |
Status comes from the agents themselves (the Codex app server or the OSC 7501 terminal status sequence). Session Bay never guesses from the output text. If an agent cannot report status, its pane simply shows whether the process is running.
Status from any program in a shell
Section titled “Status from any program in a shell”Plain shell panes also read the OSC 7501 program status sequence, so a script, a build tool or an agent you start by hand can report its own status:
printf '\e]7501;state=working\e\\' # workingprintf '\e]7501;state=done\e\\' # done; raises the completion alert when the pane is off screenSupported states are idle, working, done, blocked (with kind=permission, question or auth), error and clear. A program should report done, error or clear before it exits: Session Bay sees the pane’s shell, not each command, so working, blocked and idle only end when the shell itself exits or shows a new prompt with OSC 133 prompt marks (shell integration). Done and error stay until replaced. Shell status is display only: it never links the pane to an agent session.
System notifications
Section titled “System notifications”When an agent waits for input or permission, finishes or fails, Session Bay sends a system notification if its pane is off screen or the window is in the background. Click it to bring Session Bay forward on that pane. Each pane has a 5-second cooldown between alerts.
Turn notifications off in Settings → Appearance and defaults → System notifications. macOS may also ask for permission the first time.
You can enable an optional attention sound separately; it is off by default. Volume and test buttons are in the same section. See sound settings and Do Not Disturb limitations.
Live status
Section titled “Live status”Enable live status for each agent in Settings → Sources and tools. The existing per-agent setting is preserved. It applies to launches from Session Bay and never changes your global agent settings. Claude Code needs 2.1.295 or later; OpenCode needs reviewed 2.2.0–2.2.5. Unsupported status versions still launch with process state only and a clear panel notice. OpenCode CLI 1.x is no longer supported.
Claude Code and OpenCode now use OSC 7501 terminal reports. A working-to-idle transition in the same runtime raises one completion alert; an initial idle when opening or reattaching a pane stays quiet. Explicit done/error reports retain their existing behavior. OpenCode can report permission and question waits, but cannot report failures through its current OSC sequence. These alerts use the same visibility rules and cooldown as other attention notifications and sounds.
Claude keeps only a SessionStart hook to identify its native session. OpenCode needs no Session Bay plugin or injected configuration; its terminal record IDs are accepted as session identity only after the history catalog confirms a 2.x session with matching directory and creation time after launch. Until then, automatic board attachment may wait for indexing. Terminal status is display-only and never authorizes an action.
Claude Code 2.1.316’s startup capability query and exit clear were verified offline; its normal working/waiting/completion/error reports still need verification in a real session. OpenCode’s OSC states were verified in 2.2.3 source; a real end-to-end model run remains unverified.