Agent tabs

Agent tabs run Claude Code, Codex CLI and Gemini CLI in terminals inside the desktop app. Each tab reports what its agent is doing to your fleet board, follows Pause all, and asks Needs you before a tool call your workspace's rules hold.

Open a tab

In the desktop app, choose Agent tabs on the app's page or in the terminal's bottom bar. There is one button per tool: New Claude Code tab, New Codex tab and New Gemini CLI tab. A tab starts in your home folder, or in a folder you pick when Choose a folder is ticked. Up to 12 tabs run at once.

A button is greyed out, and says why when you point at it, when its tool can't run in a tab:

• The tool isn't installed. The app looks for it on the PATH your login shell sets.
• There is no node on that PATH. Each tab's hooks run a small forwarder with node to reach the app.
• Claude Code is older than 2.1.295. Older versions run a tool call when they can't reach Agentics, instead of blocking it.
• Your organization's Claude Code managed settings turn hooks off (disableAllHooks), or allow only its own (allowManagedHooksOnly), or can't be read.

A Gemini CLI tab doesn't start, and says why, when the computer's Gemini CLI system settings turn hooks off or aren't plain JSON. No tab starts while Pause all is on, or while Agentics can't read it.

How a tab reports

A tab points its tool's hooks at the app, for that tab only: Claude Code gets them as --settings, Codex as -c options, and Gemini CLI in a settings file of its own that the app removes when the tab closes. Your own settings and your projects' settings are never changed. The hooks post to the app on 127.0.0.1 with a token only that tab's environment holds.

Nothing you send starts a turn until the tool's hooks have reported at least once. They report as the tool starts, after its own setup questions, such as whether you trust a folder. Until then:

• Typing, the arrow keys and Enter on an empty line go to the tool, so you can answer its setup questions.
• Setup commands go too, such as /hooks, /login, /help, /status, /model, /config and /quit.
• A prompt, or any other slash command, isn't sent. The tab says the hooks haven't reported yet. If they still haven't 15 seconds later, the app stops the tab.

A Claude Code tab whose hooks reported its start, but not your first prompt within 15 seconds, is stopped too: its other hooks can't reach the app, which your organization's settings can cause.

Codex runs Agentics' hooks only after you trust them. Open a Codex tab, type /hooks, trust the Agentics hooks (once on each computer), then close that tab and open a new one.

What the fleet board shows

Each tool's tabs on a computer report as one agent, named after the tool and the computer, such as Claude Code on Ada-MacBook. The fleet board shows its status:

With several tabs of one tool open, the agent shows the most urgent of them. A tab sends its status when it changes, again every 30 seconds while it is working or needs you, and every 15 minutes otherwise. A Working or Needs you status that isn't sent again lapses after 2 minutes. The status line names the tool, never your prompt, a command or a file.

Pause all

While Pause all is on, every tool call in every tab is denied with "Pause all is on. Stop and wait for your owner." A Claude Code tab whose hooks have answered a tool call and reported its result is denied call by call and stays open. Every other tab is stopped, since its calls can't be denied one at a time: Codex and Gemini CLI tabs, and a Claude Code tab that hasn't run a tool call yet.

When the app can't read Pause all, every tool call is denied until it can, and after 30 seconds the tabs that can't be denied call by call are stopped.

Approvals from a tab

Your workspace's rules decide which actions wait for a person. Send, delete, sign, publish and share wait unless a saved rule lets them run. A tab reads every tool call against them, and every part of a shell command: rm -rf dist && npm publish is a delete and a publish. A change to a tool's hook settings, such as .claude/settings.json, .codex/config.toml or .gemini/settings.json, always waits, whatever the rules say.

A held call becomes an approval in Needs you, in the console and the terminal, and the tool waits for it:

• The approval's title names the tool and what it wants to do, such as "Claude Code wants to publish: npm publish". The console and the terminal show the whole call under it, every line, in a fixed-width font: approving runs exactly that call.
• Approved, the call runs, after the app checks Pause all again. Denied, the tool is told, with your note.
• No decision within 10 minutes is a denial, and the approval is withdrawn. So is a call the tool stops waiting for.
• The phone app lists a tab's approval and can deny it. It can't approve it, since it doesn't show the whole call: approve it in the console or the terminal.

Some calls are denied without asking anyone:

• A call longer than 16,000 characters, more than Needs you shows in full. Split it into smaller calls.
• A call with text Needs you would hide from the approver: a secret, a URL's query, login or fragment, or an email address. An SSH remote written as git@github.com:your-org/app.git counts as one: push to the remote by its name, such as git push origin.
• A call held while the tab already has 8 waiting for an approval.
• A call held after the tab has asked for 20 approvals in 10 minutes.

If a tool call runs with input other than the input the app checked, because another hook changed it after the check, the app stops the tab.

What stays on your computer

Transcripts, the terminal's output and your files stay on your computer. The app sends agentics.you each agent's status and its one-line status, and, for a held call, the approval: the tool, the folder and the whole call. A call with a secret or personal data in it is denied instead of sent (above). Agentics' own tools (send_task, submit_result and the rest) aren't held in a tab: agentics.you checks them where they run.

Limits

• Pause all denies tool calls and stops tabs; it doesn't cover the tabs with an overlay, and their processes keep running until they are stopped.
• Tabs don't reopen when the app restarts, and a tab doesn't resume an earlier session.
• Codex's hosted tools, such as web search, don't run hooks, so a tab can't check them.