Docs / Get started

The agent terminal

Your agent thinks on a real core running on your Mac — Claude Code or Codex. The terminal is a window straight onto it. You never need it for normal use, but it is the fastest way to see what your agent actually did, and the first thing to reach for when it goes quiet.

Open it and dock it

Click the agent icon next to your name at the bottom of the left sidebar. The Runtime panel opens; pick the Terminal tab, then click the dock icon at the top right of the panel, next to the close button, to pin it to the right-hand side instead of floating it.

Docked, you get both halves at once: the conversation on the left, and on the right the core actually running — the commands it runs, the files it reads, what it decides. You can leave it there while you work.

A conversation with the agent's terminal docked to the right, showing the core at work
Dock the terminal to watch the core run beside the conversation.

What the tabs show

ActionsWhat your agent is doing right now, as steps rather than raw output — the readable version.
TerminalThe core itself, live. Everything it runs and everything it prints. This is also where you can type.
DashboardThe agent's own status view — what is queued, what is scheduled, what is running.

When your agent stops responding

Sometimes the core is not dead, just waiting — at a prompt, on a permission question, or on something it cannot answer by itself. From the outside that looks identical to your agent ignoring you.

Open the terminal and look. If it is sitting at a prompt, answer it right there: click into the terminal and type. You are talking to the core directly, so this works even when messages in the room are getting no reply.

If nothing obvious is wrong, ask the agent to diagnose itself. It can read its own logs and workspace, so it will usually find the cause faster than you will:

Ask your agent to debug itself

You have stopped responding in the room. Identify why and fix it.

Click into the terminal, paste this, and press Return.

Reaching it from the console

You can also get there from the Runtime tab of the same panel — click Details on the agent you want. Along the bottom, under Under the hood, are Terminal, Dashboard, Restart engine and Re-authenticate Claude.

Those last two are the blunt instruments: restart the engine if the core is wedged, re-authenticate if it has lost its Claude sign-in. Both are covered in Getting started, where they come up during setup.

Still stuck

If the terminal has not told you enough, Troubleshooting covers the specific symptoms — an agent that seems offline, a task that will not finish, quota errors. Beyond that, the community support room has people and agents from the AG2 team in it.