Agents
The Agents sidebar shows coding agents running in your project, including their current state and any subagents. Select an entry to jump directly to its terminal.
Open the Agents sidebar
- Start Claude Code, Codex, Grok, or oh-my-pi in a Terminay terminal. Hover a folder's New terminal row for a Claude Code or Codex button that opens a terminal and starts it for you.
- Open the Agents tab in the left column, or Agents in the project sidebar.
- Select an agent or subagent to activate the terminal where it is running.
Terminay detects supported agents automatically from their local session activity. You do not need to install hooks or configure each terminal.
Which sessions appear
The Agents sidebar lists every live session of a supported agent on the server's machine whose working directory is inside the project root, or inside any Git worktree of the project's repository. A session that runs in one of the project's terminals is also listed when it changes to a directory outside the project.
Sessions started outside Terminay, for example in another terminal app, appear with an External marker. You can watch their status, but selecting one does nothing because there is no Terminay terminal to focus. External sessions do not mark tabs or add to activity counts.
Until an agent reports a title, its entry is labelled with the agent's name.
Read agent status
| Status | Meaning |
|---|---|
| Working | The agent is processing a turn, using a tool, or running subagent work. |
| Waiting | The agent needs approval, an answer, or another action from you. |
| Blocked | The agent reported a condition preventing it from continuing. |
| Done | The current turn completed, failed, or was cancelled. |
| Idle | The session is still available but has no active work to highlight. |
New activity can mark an entry as unread. Opening it clears the unread emphasis without changing the agent’s actual state.
The same status appears on the agent's terminal tab. Each project tab shows a count of its terminals that currently have an activity indicator, coloured red when something needs your attention, amber while work is in progress, and green for finished work you have not viewed. The activity menu in the header uses the same counts.
What each agent CLI can report
What Terminay can show differs by agent. Every fact comes from files the CLI already writes for its own purposes. Terminay never modifies, configures, hooks, or wraps an agent, and where a CLI records nothing, Terminay shows nothing rather than guessing.
| Capability | Claude Code | Codex | Grok | oh-my-pi |
|---|---|---|---|---|
| Appears while running | ✓ | ✓ | ✓ | ✓ |
| Shows the session title | ✓ | ✓ | ✓ | ✓ |
| Shows the model | ✓ | ✓ | ✓ | ✓ |
| Working and idle status | ✓ | ✓ | ✓ | ✓ |
| Waiting for your input | ✓ | ✗1 | ✓ | ⚠2 |
| Done, with its outcome | ✓ | ✓ | ⚠3 | ✓ |
| Subagents and their state | ✓ | ✓ | ✓ | ✓ |
| Value | Meaning |
|---|---|
| ✓ | The CLI records the fact and Terminay shows it. |
| ⚠ | The CLI records the fact only in some cases. The note explains which. |
| ✗ | The CLI records nothing Terminay can read. The note explains what you see instead. |
- Codex shows an approval prompt on screen but does not save it, so a Codex session awaiting approval reads as working.
- oh-my-pi reads as waiting when it asks you a question. A permission approval is not saved, so a session stopped on one reads as working.
- Grok reports a failed turn as failed but records no error message for it.
A Codex session that has been launched but not yet given a prompt has nothing on disk, so it appears after your first message.
Codex and shell integration
Terminay's shell integration for zsh, bash, fish, and PowerShell runs codex with --no-daemon in new terminals, when the installed Codex supports the flag. That keeps each Codex attached to the terminal it was started in, so its status lands on the right tab. Terminay writes none of your shell startup files; a codex alias or function of your own takes precedence. A Codex started without the flag, for example inside tmux or a nested shell, shows no status rather than the wrong one.
Roots and subagents
A root entry represents one agent session. If that agent starts supported child work, its subagents appear beneath the root, with a count beside the root's name. Use the arrow to expand or collapse them. Selecting a subagent opens the same terminal as its root, because the child runs inside that session.
Choose which agents are tracked
Agent tracking is provided by the Built-in Agents extension. Open Settings → Extensions to switch individual agents on or off: Claude Code, Codex, Grok, and oh-my-pi each have their own switch.
To turn the whole feature off, including the Agents sidebar, disable Agent status and sidebar under Settings → AI → Agents.
Privacy and scope
Terminay reads the agents' own session files on the server and keeps only status, titles, models, the current tool's name, and turn outcomes. Prompts, responses, reasoning, tool arguments, and tool output are not sent to connected clients.
With several servers attached to one window, each project shows the agents running on the server that owns it.
If an agent does not appear
- Confirm the agent is running in the project root or one of its Git worktrees, on the same machine as the project's server.
- Check that the Built-in Agents extension and that agent's switch are enabled in Settings → Extensions.
- Check that Agent status and sidebar is enabled in Settings → AI → Agents.
- Other agent CLIs are not tracked. Their terminals still show ordinary terminal activity.
The Agents sidebar is independent from Terminay MCP. MCP lets an agent control sibling terminals; the sidebar reports agent activity. You can use either feature on its own.