Terminals and local echo
Open an HQ session in a VS Code terminal, start a new one, wake an AI Team Cloud Computer, and see what you type at once with local echo.
The person who started a session is the only one who can type in it. Everyone else who opens it watches it live, view only. To work yourself, start your own session.
Open a session
In the HQ sidebar's Teams view, expand a team and click one of its sessions. It opens in a VS
Code terminal named HQ · <team> · <session>. HQ: Attach in the Command Palette asks you to
pick a team and a session.
With more than one HQ account signed in, the name also shows the account:
HQ · owner@client · Backend team · main. A terminal works as the account that opened it.
Switching the window's account leaves it open, still working as that account.
The first line says whose session it is, and whether you can only watch:
Attached to "fix login bug" (Dana) · view onlyEach session row shows who started it (you for your own), starting while HQ is still starting
it, view only when you cannot type in it, and Codex for a Codex session. Clicking a session
that is already open shows its terminal.
Closing the terminal leaves the session running in HQ. Open it again any time.
Start a new session
Press + on a team, or right-click it and choose New Session Terminal. HQ starts a new session on that team and opens it in a terminal. You need editor or owner access to the team and an active plan; when the team is at its session limit, the extension says so.
Start, stop and restart a session
Each session row has buttons for what you may do with it, and the same items when you right-click it:
- Start Session (play icon) on a stopped session. A team that is off starts for it, as when you press Start in HQ. Start on a session that is already starting says so: "Session "fix login bug" is already starting."
- Stop Session and Restart Session on a running session. Restart stops it and starts it again, resuming its conversation.
When Claude or Codex is answering in the session right now, Stop and Restart ask first, for example "Claude is answering in "fix login bug" right now. Stop it anyway?". Only Stop Session (or Restart Session) goes ahead.
Only the session owner or a team owner can start, stop or restart a session, as in HQ. On a session you can only watch, the buttons do not show. When HQ refuses, a notification says why, for example when the team is at its session limit, or "Too many requests. Try again in 34 seconds." with the wait HQ asked for. The Teams view refreshes afterwards.
Each start, stop and restart is recorded in your organization's Audit log in HQ as coming from VS Code. The computer's name shows to people who can manage remote access; others see a short device id.
Paste or drop an image
Give Claude a screenshot or a picture the way you would on your own computer:
- Paste it. Copy an image, click in the session terminal and press Cmd+V (macOS) or
Ctrl+V (Windows and Linux; Ctrl+Shift+V works too on Linux). "Uploading image..." shows,
then the image's path appears at the prompt, for example
.uploads/pasted-20261002-101500-3f2a.png. Describe what you want and press Enter. - Drop it. Drag image files from your computer onto the terminal. The extension asks first, for example "Upload ~/Desktop/screenshot.png to Backend team?": Upload adds each file and types its path; Type the path types your computer's path as it was, with nothing uploaded.
- From the team's own files. Drag an image from the team's folder in the Explorer: its path in the team is typed, with nothing uploaded. Files from another team's folder are not added.
PNG, JPEG, GIF and WebP images up to 10 MB are added, into the team's .uploads folder. When the
clipboard holds text, it pastes as text, even if the copy also carries a picture (a copy from a
spreadsheet or a slide does). An upload that does not finish within 30 seconds stops with "The image
upload did not finish." If one file of several fails, the ones already added stay in .uploads, and
Cancel during an upload may still leave that file in .uploads (nothing is typed). On Linux, image paste needs wl-paste (Wayland) or xclip (X11); without them,
Ctrl+V pastes text only. You need to be able to change the team's files: with view access, the
extension says so and adds nothing.
When the AI Team Cloud Computer is off
A team that is not running shows off in the Teams view. Two ways to start it:
- Wake Team: press the play icon on the team, or right-click it and choose Wake Team. A notification shows the progress, "Waking Backend team... this usually takes 15-30 seconds" (30-45 seconds on Boost Max), then "Backend team is running." A team that is stopped (not asleep) cannot be woken: the message offers Start a Session, which starts its Cloud Computer.
- Open one of its sessions. The terminal says "Backend team is off." and "Press any key to wake it." The next key you press wakes it, and the terminal connects when the Cloud Computer is ready.
After 30 seconds (45 on Boost Max) the progress says "Taking longer than usual, still working.". If the Cloud Computer has not started within 3 minutes, the extension says so; check the team in HQ and try again. Viewers can wake a team too.
When the connection drops
The terminal reconnects on its own. HQ's connections are renewed about once an hour; the terminal moves to a fresh connection before that happens, with nothing to see and no keystroke lost. If the connection drops anyway, the terminal reconnects quietly, and says "Connection lost, reconnecting..." only when reconnecting takes more than a few seconds or the connection drops again. If it cannot reconnect, it says "The connection to HQ was lost." and "Press any key to reconnect.": the next key you press reconnects it in the same tab (that key is not typed into the session).
When a session ends on HQ's side, for example because it was stopped, the terminal stays open with
the reason, and its name ends in · stopped. Press any key to reconnect, or close it. Attaching a
session whose terminal has ended (for example after VS Code restarted its extensions) opens a fresh
terminal instead of the ended one.
When the session's process is restarted on the AI Team Cloud Computer, the terminal clears and shows the new one by itself, at the terminal's width.
If VS Code restarts its extensions (for example after an update), the HQ terminals that were open come back by themselves in fresh tabs.
The same session in two places
A session has one terminal size on the AI Team Cloud Computer. When the same session is open in more than one place, for example in HQ in your browser and in a VS Code terminal, or in two VS Code windows, the place you are using sets that size:
- The terminal in front sets it. Clicking into the HQ terminal, switching to it, or bringing its VS Code window to the front gives the session this terminal's size. So does typing in it.
- The others follow it. A terminal that is not in front draws the session at that size and redraws its screen once, so nothing overlaps or breaks mid-word. When its panel is larger, the extra space stays empty; when its panel is narrower than the session, it shows as much as fits until you bring it to the front.
- Watching never changes the size. A view-only terminal follows the size of the one that can type, and never sets it.
- A very small terminal never sets it. One smaller than 40 columns or 10 rows keeps showing the session at the other place's size, so it cannot shrink the session for everyone.
- A new size waits while Claude Code is writing. If the size changes while Claude Code is writing an answer, the session takes the new size once it stops writing text, and never more than 30 seconds later. That keeps the part of the answer that has already scrolled up from being drawn twice for everyone who opens the session later. This terminal resizes at once, so until the session catches up it can show a few lines laid out for the old width. At a prompt, or while a tool runs, the first size change applies at once. Codex sessions always change size at once.
Local echo
On a slow connection, local echo draws your keystrokes the moment you press them, before the AI Team
Cloud Computer echoes them back. It only applies in sessions you can type in. Set it with the
hq.localEcho setting:
| Value | Behavior |
|---|---|
auto | Show what you type at once where the session's prompt allows it, while the round trip to the AI Team Cloud Computer is slower than 60 ms. This is the default. |
always | Always show what you type at once. |
off | Show only what the session echoes back. |
The setting applies to terminals you open after changing it.
- Your organization has to allow it. An owner or admin turns on Instant local echo in HQ, under Settings, Security. When it is off, the extension says so once and the terminal works without it.
- VS Code has a local echo of its own. When VS Code's own is on for a terminal
(
terminal.integrated.localEchoEnabled), HQ's local echo stays off there, so nothing is drawn twice, and the terminal says so. To use HQ's, setterminal.integrated.localEchoEnabledtooff.
Good to know
- While an HQ terminal is the active one, the status bar shows its account, its team and whether
it is running. When the terminal works as another account than the window's, the status bar ends
in
· other account. - If another window renews the terminal's account, the terminal says "Connection lost, reconnecting..." and comes back in the same tab.
- When a session starts a server on a port, the Ports view offers to forward it. See Ports.
- Signing out of an account closes that account's HQ terminals, in every window. The sessions keep running in HQ.