docsterminals & rigs

One project. Up to twelve shells.

The Grid is 13x's main workspace: a dense, monochrome tile layout where each cell is a real interactive PowerShell session rooted in the same project folder. Pick a count or a saved rig, hit LAUNCH, and watch every shell at once.

overview

The Grid lays out 2 to 12 real interactive PowerShell shells side by side, all rooted in one project path. Each cell is a genuine PTY session — dev server, tests, git, and coding agents — so you can drive any of them by keyboard and zoom one to full screen without killing the rest. It replaces the chaos of juggling many terminal windows for a single project with one compact window you can watch all at once.

  • Up to 12 real interactive PowerShell shells in one window
  • Only process started is the shell itself — output never leaves your machine
  • No cloud, no accounts, no telemetry, no network calls
  • Monochrome: ANSI colors remapped to grayscale, never conveyed by hue
  • Checkpoints to .13x/snapshots/latest.json on launch and every 30s
  • Focus one pane full-screen while the rest keep running
why it matters

Real interactive PTYs, not fakes

Each card is a genuine PowerShell session over a portable-pty/ConPTY pseudo-terminal. Prompts, ANSI output, and interactive CLIs like git, npm, cargo, and claude all work — output streams into xterm.js and keystrokes forward straight back.

Local-first, no telemetry

The only process the Grid starts is the PowerShell shell itself. Terminal output stays on your machine — no cloud, no accounts, no telemetry, no network calls.

Monochrome by design

Pure black, white, and grayscale. ANSI colors are remapped to grayscale so colored CLI output stays legible without hue — workstation-grade minimalism, dense and dark-only.

Persistent terminals decoupled from React

xterm.js instances live in an imperative registry, not the React tree, so a terminal moves between its grid card and full-screen focus — or survives the grid unmounting — without losing scrollback or its PTY.

Keyboard-driven

Arrow-key selection that matches the on-screen column layout, Ctrl+1..9 to zoom a pane, Ctrl+Space to jump to the agent that needs you, and clipboard-aware Ctrl+C/Ctrl+V inside terminals without losing SIGINT.

Per-workspace isolation

Sessions are tagged with a workspace. The grid, broadcast, tallies, and chords scope to the active workspace while other open workspaces keep running and updating live — kill one without touching the others.

how it works
01

Pick a path and a count

Choose a project folder, then pick a shell count — 2, 4, 6, 8, 10, or 12 — or load a saved rig layout instead. LAUNCH stays disabled until a project path is selected.

02

Launch every slot at once

Hit LAUNCH (or Ctrl+L). Each slot opens in the chosen folder, auto-start slots type their command, and the grid renders one card per slot from the frozen launched roster — best-effort, so a slot that fails to spawn is reported per-slot while the rest keep running.

03

Drive and zoom any pane

Click into a card and type; output streams back live. FOCUS or Ctrl+1..9 maximizes one terminal to full screen while every other session keeps running in the background. BACK TO GRID or Esc returns to the overview.

04

Control shells individually

RESTART relaunches a single shell in place, STOP terminates just that one, CLEAR wipes its scrollback, and REC/END captures a terminal's raw output as a run log. KILL ALL (Ctrl+K, with a confirm) tears down the whole active workspace.

05

Resume from a checkpoint

The grid silently checkpoints on launch, slot start/stop, kill-all, and every 30 seconds while running, writing to .13x/snapshots/latest.json so the whole rig can be resumed later.

faq

How many terminals can I run at once?

Pick 2, 4, 6, 8, 10, or 12 shells for the default grid, or load a saved rig with its own slot layout. Every slot opens at once in the selected project path.

What shell does each cell run?

PowerShell only. Every slot runs pwsh, falling back to powershell.exe on Windows or a POSIX login shell as a last resort on macOS/Linux. There is no per-slot bash/zsh/cmd selection.

Does any of my terminal output leave my machine?

No. The Grid is fully local — the only process it starts is the PowerShell shell, and terminal output stays on your machine with no cloud, accounts, telemetry, or network calls.

Can I zoom one terminal without killing the others?

Yes. Click FOCUS or press Ctrl+1..9 to maximize a pane full-screen; every other session keeps running in the background. BACK TO GRID or Esc returns to the overview.

get started

one project. many shells. zero noise.

13x is local-first and free of telemetry — your code, commands and shells never leave the machine. Join the waitlist for the next build.