Chutdown
Shutdown your computer(or notify) when all tasks are finished, run terminal servers minimized, launch a specific claude model 50% faster than claude code, See the progress of your current sessions (and idle sessions), see your claude usage at all times.
One click per model, 2x faster loading time and 100x faster than running /models.
Claude models wear orange letters and open claude --model; the OpenAI ones (Astra, Sol,
Terra, Luna — tick them in the picker) wear blue letters and open a codex -m terminal,
so the two S buttons — Sonnet and Sol — are never mistaken for each other. Codex tabs
get the same traffic light and the same auto-named tab as Claude ones, and the armed
shutdown waits for a codex turn like any other.
Details →
View usage instantly
See your /usage limits, without leaving the status bar — and click the meter to step
past a limit that is already spent, so a weekly window at 0% left stops being the only
number you can see. Use both CLIs and you get a tile each — $(pulse) 64% Claude
and $(pulse) 30% Codex, each clicking through its own windows — with the Codex numbers
read from its own session files, no token and no request. A vendor's tile shows only
while that vendor is among the models you picked buttons for, and both tiles compact with
the rest of the bar when it fills.
Details →
off / sound / notify / shutdown
*When your sessions finish:
- stay quiet.
- chime.
- pop up a notification.
- turn off computer.
read from the transcript's own stop_reason, never guessed from silence.*
A command Claude left running in the background counts as unfinished too — Claude is
re-invoked when it exits — so a build in flight keeps its light 🟡 and holds all three
gears, for up to chutdown.shellMinutes (default 60).
And a session that stops to ask something need not stop the night: with the gear armed
Chutdown answers for you after chutdown.autoAnswerMinutes (default 5) — one Enter, taking
the option the dialog has highlighted. On by default for the armed gear only, opt-in for
the other three, and chutdown.autoAnswerScope: "questions" keeps it away from permission
prompts and plans. Both hovers say what is about to be pressed, and when.
Leaving for the night but not before a set time? Shutdown timer… in the gear's hover
arms the shutdown after the minutes you type — and it still waits for every session to
finish before its countdown. The same hover's Settings link opens Chutdown's settings.
Details →
:
*See all your claude tasks and status:
- 🟢 Processing task.
- 🟠 Requires prompt.
- 🟡 A command it started is still running — it will pick itself back up.
- 🔴 Task has finished.
The light for the tab you have selected wears a › in front of it, at every size the bar
compacts to.
Hover to see the task details — the latest output, plus the prompt it started on, the two
you sent in between (↓ lines), and the one you last sent, in the order you typed them;
click to jump to it. The hover's links copy it, rename it, open its raw transcript, and — when the session has a tab in this window — close that tab, which folds the light into idle without losing anything. Initial tasks are renamed based on the initial prompt.*
Details →
On a crowded afternoon the bar compacts itself rather than falling off the right edge:
the launch buttons drop to their letters, then the names shorten, then the lights are just
lights — the hover keeps the full name. chutdown.statusBarBudget sets how much room it
gets before that starts (0 = never).
Details →
Old sessions turn idle but still redeemable — one click to run again,
no claude --resume picker. And a tab you close by accident while its
light is 🟢 comes straight back, resumed and told to finish the task —
nothing redone, only the one tool call that was in flight.
Details →
Terminals
"npm run start" your project with one click and allow agents to restart the app as well.
Details →
.terminals — batch multiple processes as well.
{
"dev": "npm run dev", // workspace root
"web": { "cmd": "npm run dev", "port": 3000 }, // root too, with a port probe
"api": { "cmd": "npm run dev", "cwd": "packages/api", "port": 4000 } // custom folder
}
cwd is the only thing that picks a folder: leave it out, like web above, and the
entry runs in the workspace root. A one-line syntax is read too, so a single app in the
folder you are already in is one line — name:port = command, no folder anywhere:
dev:3000 = npm run dev
Declare your dev servers once: each gets a light with its latest log in the hover,
its port is freed before launch, and one button stops them all.
And when one dies on its own, it comes back. A nonzero exit is appended to
error.md in the workspace root — the command, the exit code, the last 25 lines it
printed — and the entry is relaunched, port taken back first, backing off 2s → 60s and
giving up after five crashes in ten minutes rather than looping for ever. A stop or a
restart you asked for is never mistaken for a crash.
(chutdown.autoRestart, chutdown.autoRestartMax, chutdown.crashLog.)
And the agent in the repo can restart them itself — no mouse, no asking you to
click:
code --open-url "vscode://d8a.chutdown/restart?name=web&ws=C:/path/to/this/folder"
/start, /stop and /restart, all of them or one by name, straight from the shell
your session already has. It edits a file, it restarts the server, it re-reads the log
in the hover.
Details →
Choose your favorite models
Choose models — Choose what models you want to show and hover to see their use-case.
The buttons you start with follow your plan — no Fable button on a Pro account with no
usage credits — and the picker still lets you tick anything, including the four OpenAI
models under their own heading (blue letters, launched with codex -m).
Details →
Install
Requirements: VS Code 1.93+, and the Claude Code
CLI installed and signed in.
From the Marketplace — search Chutdown in the Extensions view, or from a terminal:
code --install-extension d8a.chutdown
From a .vsix — download it from the
latest release
git clone https://github.com/D8Acom/Chutdown.git