Documentation
TermHQ is a terminal workbench for running coding agents. These pages describe how it behaves and how to change that behavior.
Downloads are available for Windows and macOS (Apple silicon). Linux support is pending. See Installation for platform availability.
Press Ctrl+K (⌘+K on macOS) anywhere on this site to search every page. To read or search everything at once — or paste the whole corpus into an agent — use all documentation on one page.
Getting started
Open your first terminals, tile them, and learn the handful of shortcuts that matter.
Installation
Install TermHQ on Windows or macOS, what to expect from SmartScreen and Gatekeeper, and how updates work.
Panes and layout
Tile and resize panes, move running terminals and editors between workspaces, arrange from the keyboard, maximize, stash, and undo a close.
Browser panes
A real web page as a pane in the grid: the OS browser engine embedded in TermHQ, with the same drag, stash, resize and maximize moves as a terminal.
SSH connections
A shell on another machine as a pane in the grid, through the OpenSSH client you already have: typed targets, saved profiles, your ssh config's aliases, and a way back when a connection drops.
The editor
Editor panes: files as tabs, saving that cannot lose work, reading markdown, and the keys a VS Code hand already knows.
Language servers
Diagnostics, hover, completion, go-to-definition and formatting in editor panes — from language servers you install, never bundled.
Workspaces
Group your work into windows, move running terminals and editor panes between them, and close a window while its shells keep running.
Persistent sessions
Why quitting TermHQ does not kill your shells, exactly what survives what, and the settings that control it.
Remote workspaces
A preview: open another computer's workspaces in windows on this one, over your local network, while their shells, git, files and agents keep running on that computer.
Running coding agents
The parts of TermHQ built specifically for running Claude Code, Codex, and other coding agents.
Letting agents use TermHQ
Connect Claude Code, Codex and other agents to TermHQ, so they can see and work its panes, and decide what each one may do.
Dictation
Talk into a terminal, a text field or a web page: on-device transcription with a local Whisper model, started from a button, a chord, or a held key, with a cursor that shows it listening.
Source control
Review, stage and commit changes, browse history, manage branches, sync, resolve conflicts, and work with stashes and worktrees.
Worktrees
Keep several checkouts organized, open a terminal or agent in the right one, and track worktrees across repositories.
Configuration
Where TermHQ keeps its settings, every setting you can change, and how config files behave across versions.
Keyboard shortcuts
Every default shortcut in TermHQ, how to rebind them, and how conflicts with terminal programs are resolved.
Theming
Built-in themes, writing your own, theming the workbench and editor, splitting the terminal palette, and importing themes from Open VSX.
Under the hood
What TermHQ is built from: a native Rust core, the OS webview instead of a bundled browser — for the interface and for browser panes alike — and first-party parts everywhere it counts.
Troubleshooting
Fixes for the problems people actually hit: monochrome agents, missing shells, stale sessions, language servers, unsaved edits, browser panes, and where the logs are.