One command.

It starts DeckHQ, opens the floor in a window of its own, and asks once whether you want a Desktop and Start Menu icon.

npx deckhq app

Node 18 or newer. The package has no dependencies.

No Node on the machine

Paste the line for your shell. It checks for Node 18 or newer and offers to install it, never without asking, then installs DeckHQ, offers the icon and opens the window.

irm https://deckhq.dev/install.ps1 | iex

curl -fsSL https://deckhq.dev/install.sh | sh

Read them first: install.ps1 and install.sh are two short files, served here byte for byte from the repository.

A step at a time

Install it, open it, and add the icon when you want one.

npm install -g deckhq

deckhq app

deckhq shortcut --install --yes

Without --yes, the last one prints every path it would write and the exact command each will run, and writes nothing.

Inside Claude Code

The plugin brings the hooks without touching your settings.json, starts DeckHQ on your first session, and adds /deckhq:waiting.

/plugin marketplace add DkPanseriya/deckhq

/plugin install deckhq@deckhq

A permission prompt cannot be answered from the panel on this route; install the hooks from Settings for that.

Look before you install.

The report installs nothing, writes nothing and sends nothing. It reads the transcripts already on your disk and prints how many sessions there are, how many are running, and how many finished and are still waiting on you.

npx deckhq doctor

The fourth line is the number nobody else counts: sessions that finished their turn, left the agent view when their process exited, and are still on the floor.

$ npx deckhq doctor
  claude code     available
  transcripts     77 sessions across 20 projects
  running now     6   (claude code's own agent view reports 6)
  on the floor    77  ← 71 sessions have already finished; the agent view no longer lists them
  codex           not installed
  waiting on you  0   (3 waiting, all still running)
  hooks           installed, port 4400, 285 events, last 1m ago
  state           ~/.deckhq/state.json, writable
  egress          none. no outbound sockets.

A real run on the development machine, 3 September 2026. Your numbers will differ.

Run it like an app.

The floor opens in Chrome or Edge in application mode: no tab strip, no address bar, its own taskbar button, its own browser profile. Closing the window costs nothing.

The window

deckhq app

Reuses a running DeckHQ or starts one, then opens the floor.

The icon

deckhq shortcut --install --yes

A Desktop and Start Menu icon. On Windows, a taskbar pin keeps the DeckHQ icon.

At login

deckhq autostart --install --yes

Starts DeckHQ quietly when you log in. No window.

Windows is the platform this was run on. The macOS bundle and the Linux desktop entries are written from Apple's and freedesktop.org's documentation and have not been executed on a machine.

Hooks, and taking it all off again.

Hooks are a choice

Without them, DeckHQ reads state from transcripts. With them, state is exact: a permission prompt raises a hand within milliseconds. The consent screen shows the literal JSON and the exact file, and nothing is written until you click.

Everything is tagged

Every file and every settings entry DeckHQ writes carries a tag. Removal deletes what is tagged and nothing else, and your settings file is backed up before the first write.

deckhq shortcut --remove

One folder

Your queue, names, settings, cache and ledger live in ~/.deckhq/. Delete it and nothing of DeckHQ is left.

npm uninstall -g deckhq