# Terminal and chat

Work with an AI Employee in the session's terminal, or read and answer it in the chat view. The session owner types; everyone else on the team can watch.



Every session has a terminal, where the AI Employee runs, and a chat view of the same conversation.
Use whichever you prefer: they stay in step.

## The terminal [#the-terminal]

The terminal is the AI Employee's own screen, exactly as it would look on your computer. Type
your request and press Enter. When Claude asks for approval, answer in the terminal.

* **Paste** text and images as you would anywhere else.
* **Instant local echo** shows what you type right away, before the session echoes it back. An
  organization owner turns it on in **Settings**; each person can turn it off for themselves.
* **Wide or narrow screens:** when a session is open in two windows, the window you are using sets
  the size and the others match it.
* **On a phone,** a key bar above the keyboard has the keys a terminal needs, such as Esc, Tab and
  the arrows.

## The chat view [#the-chat-view]

Switch between **Chat** and **Terminal** at the top of the session; on a phone they are two icons.
The chat view shows the conversation as messages: what you asked, what the AI Employee did and
its answers, with images. It works for Claude Code and Codex. If the chat view can't show a
session, the terminal still works as usual.

* **Send a message:** press Enter, or Shift+Enter for a new line. On a touch screen with no trackpad
  or mouse attached, Return adds a new line and you tap **Send** to send (on a phone, the arrow
  beside the box). Cmd+Enter (Ctrl+Enter) always sends, also from a keyboard attached to a tablet.
* **When Claude is asking something on screen,** your message waits in the box and Chat says so
  above it. Answer the question first, then send.
* **When Claude has a plan ready,** Chat shows it as a card with **Approve plan**. Approving keeps
  Claude asking before each edit; it never turns on auto mode. To change the plan instead, type
  what to change in **Tell Claude what to change** and press **Send** (or Enter). Claude keeps
  planning with your feedback and shows you a new plan. With text already in the message box,
  **Use my message as the answer** moves it into that field. Approving with auto mode is only in
  the terminal.
* **Messages from your other Claude sessions** (a teammate or helper session that sent this one a
  message) show as a short note, such as "Message from another session (release-check): Tests
  passed". Routine status pings next to each other share one note, such as "3 status updates from
  another session (release-check)". Click or tap a note to read the whole message.
* **A message Claude is holding for you:** when another session's permission mode differs from this
  one's, Claude holds its message until you decide. Chat says a message is waiting and shows it as a
  card with **Deliver** and **Deny**, on a phone and a tablet too. Read it first: it came from
  another session, not from you. A long message (or one with quotes or brackets) shows the way
  Claude previews it, which can leave out part of the text. The card then says how much of the
  message it shows, and **Deliver** is not highlighted; it always sends the whole message. If
  nobody answers in a few minutes, the message expires and the sender is told it was declined. A
  scheduled run never answers it for you.
* **When you turn down a plan,** Chat says you didn't approve it, and Claude waits for your next
  message.
* **When you stop Claude or say no to a permission,** Chat says you stopped it and marks that step
  "stopped by you".

## Permission modes [#permission-modes]

The mode buttons in the session header (**Ask me first**, **Auto-edit**, **Autopilot**) change
how much the AI Employee does on its own. On a phone, they are under **More**, in **Permission
mode**. A change applies when the session restarts.

## Watch someone else's session [#watch-someone-elses-session]

Anyone on the team can open a teammate's session and watch it live, unless the team or the session
owner limited who can see it. Only the owner can type. To hand a session to someone else, a team
owner can reassign it. Schedules that run on the session can move to the new owner in the same
step; see [When a session is reassigned](/docs/schedules/#when-a-session-is-reassigned).

<Callout title="Who can do this">
  The session owner types. Viewers, editors and team owners on the team can watch and read the chat
  view.
</Callout>

## Related [#related]

<Cards>
  <Card title="Session history" href="/docs/sessions/history/" />

  <Card title="Attach from your terminal" href="/docs/cli/attach/" />

  <Card title="Session terminals in VS Code" href="/docs/vscode/terminals/" />
</Cards>
