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 Codex, Claude Code, Cursor Agent, or omp in a Terminay terminal.
- Open 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.
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.
Roots and subagents
A root entry represents one agent session in one terminal. If that agent starts supported child work, its subagents appear beneath the root. Selecting a subagent normally opens the same terminal because the child runs inside that root session.
Privacy and scope
Agent activity is scoped to the current project and terminal. Terminay reduces supported local journals into status, titles, models, and lifecycle events. Raw reasoning, responses, tool arguments, tool output, and journal records are not sent to connected clients.
If an agent does not appear
- Confirm the agent is running inside a Terminay terminal for the current project.
- Check that its built-in extension is enabled in Settings → Extensions.
- Keep the agent in the foreground briefly while it creates or resumes its session.
- Remote environments must provide the process and journal-observation capabilities required by that agent.
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.