The tmux grid for coding agents, in your browser

Parallel agents are how people get real throughput from Claude Code and Codex. Each task gets its own context window, and four tasks finish in the time of one. The usual setup is a tmux session split into panes, one claude per pane.

That works until you want it from another computer, on another machine, or with a different agent in pane three.

What Terminal mode is

Terminal mode is the Terminals page in Termdeck. It lays chats out the way tmux lays out a session: panes tiled edge to edge, a status bar along the bottom. Each pane reads like the CLI you know. Your prompt sits after ❯, replies and tool calls get a ● bullet, and a tool's result hangs under it after ⎿.

Every pane is a real session on a real machine. Under the prompt it shows the project, git branch, worktree and machine, then the model, effort and how full the context is.

Why it beats a local tmux grid

• Any agent in any pane. Claude Code in one, Codex in the next, Grok in a third. Same layout for all three.
• Any machine in any pane. Pane one on your laptop, pane two on the build server. The grid does not care where the agent runs.
• Open it anywhere. The grid is a browser tab. Open it at work, at home, or on a borrowed laptop.
• Notifications that lead to the pane. When a pane needs approval, the alert offers Go to pane.
• Nothing to install but the agent. No tmux, no config, works the same on Windows, macOS and Linux.

How to use it

• Attach a running chat. The attach list puts chats that are working right now first. Open it in this pane, split right, split down, or in a new window.
• Drag from the sidebar. Drop a chat near a pane's edge to split on that side, or in the middle to replace it.
• Start fresh. Click + on the status bar or any pane, pick machine, folder, agent, model and effort, and type.
• Steer mid turn. A message sent while Claude or Codex is working goes into the running turn. On Grok it is queued for when the turn ends.
• Stop. Press Ctrl C in the pane, or click ■. With text selected, Ctrl C copies instead.
• Reset. Type /clear to archive the chat and start a new one with the same settings.

Full reference in Terminals.

Terminal mode and your real terminal

Termdeck reads the same session files the CLIs write. A chat you started in your own terminal can be attached to a pane, and a chat started in a pane resumes in your terminal with claude --resume or codex resume. While another process is writing to a chat, the pane goes view only so two writers never fork the transcript. Details in working across the browser and the terminal.

Plans

Starter shows four panes in a 2x2 grid. Pro shows nine. See plans, or compare it with a plain setup in Termdeck vs tmux.

Terminal mode, answered

Do I need tmux installed?

No. The grid is in the browser. The machine only needs the Termdeck agent and the CLI you want to run.

Can I run Claude Code and Codex in the same grid?

Yes. Any engine in any pane.

Is it a real shell?

No. Each pane is a coding agent chat with a terminal look, not a shell prompt. You type to the agent, and the agent runs commands under your approval rules.

Does it work on a phone?

The chat view is built for phones. Terminal mode is built for a big screen.