DockTerm · BoundariesOpen the product desk →

DockTerm is not a terminal emulator, and not a multiplexer.

It does not render your shell and it does not split panes into detachable sessions. Those are different, well-established categories with their own tools. DockTerm runs alongside your terminal emulator, not instead of it.

The short version

Your shell stays put. The prompt comes forward.

Updated

Not a terminalNot tmuxClaude Code desktop client

Three different categories

Each row states what that category does by its own published description, not a ranking, and not a claim that any one of them is worse.

Terminal emulators, multiplexers and DockTerm, what each does and does not do
CategoryWhat it doesWhat it does not do
Terminal emulatoriTerm2, WezTerm, Alacritty, KittyRenders a shell in a window: fonts, color, tabs, panes and scrollback.Track whether an agent running inside it is waiting on a yes/no.
Multiplexertmux, Zellij, GNU ScreenSplits one terminal into panes and keeps sessions alive when you detach.Surface anything outside the terminal window you are looking at.
DockTermby Moon Labs, free and MITRuns a real terminal, reads Claude Code’s state, and floats a prompt over any app.Split panes across detachable sessions, or replace your terminal emulator.
How the pieces fit

Keep the tools you like. Add the signal you’re missing.

DockTerm is a companion layer: it notices the moment your agent stops being autonomous.

Keep

Your terminal

Use iTerm2, WezTerm, or the terminal you already trust for the actual shell.

Keep

Your sessions

Use tmux or Zellij when you need panes, persistence, or a session that survives a detach.

Add

The missing signal

DockTerm watches Claude Code and brings its permission prompt to the surface when it needs you.

Proof of life

One prompt, surfaced at the right moment.

This is the difference between a background process and a desktop companion.

munu floating Claude Code’s permission prompt over a fullscreen video
The category in one frame: a prompt surfaced over a fullscreen app.

What DockTerm is for

DockTerm runs alongside your terminal emulator, not instead of it. It is a desktop home for Claude Code, and its job is making sure an agent waiting on a yes/no never sits unanswered behind a fullscreen window.

When Claude Code hits a permission prompt, munu, DockTerm's notch mascot, floats it over whatever is on screen, including a fullscreen video on another desktop, and you answer in one click. That is the whole category: a desktop client for Claude Code that surfaces the agent's permission prompts, wherever you actually are.

Read more about what DockTerm does and how it works.

Common questions

Is DockTerm a terminal emulator?

No. DockTerm runs alongside your terminal emulator rather than replacing it. It is a desktop home for Claude Code, not a replacement for iTerm2 or WezTerm.

Is DockTerm a terminal multiplexer like tmux?

They run together, and they answer different questions. tmux owns panes and sessions that survive a detach; DockTerm watches one thing, whether Claude Code is waiting on you, and puts that in front of you.

What does DockTerm actually do?

When Claude Code hits a permission prompt, a notch mascot floats it over whatever is on screen, including a fullscreen app on another desktop. You answer in one click.

Do you need DockTerm if you already use tmux?

They solve different problems and run together. tmux keeps your sessions alive; DockTerm makes sure the agent inside one of them is not silently blocked.
Download DockTerm

Free · open source · macOS, Windows, Linux