Bands

A definition of done Jev checks after every turn: per-criterion probabilities that demand evidence, a band above the prompt, optional auto-continue.

Keeps changes on task: every edit is judged by Jev against your last request (and Claude's plan) in a few hundred ms; drive-by changes go back to Claude.

Catches tests being weakened to make them pass: every test-file edit is judged by Jev in a few hundred ms against what you asked for.

What Claude touched this session: reads, edits (+/− lines), searches per file, main vs subagent, with flags for blind edits and repeated reads.

Git at a glance and in reach: a branch/changes readout, a /git pane to diff, stage, revert and commit, and Conventional Commit messages written by haiku.

One-tap follow-ups: after each answer, three short next prompts above the prompt, on keys 1-3.

Standing context you control: pin notes and files once, and every prompt you send carries them.

Rough idea in, precise prompt out: /polish or a trailing ?? rewrites your prompt into the input box for you to edit and send.

Park a half-written prompt, ask something else, and pop it back into the box later.

Blocks catastrophic shell commands (rm -rf ~, curl | sh, force-push to main, DROP DATABASE, format C:) and asks before risky ones (git reset --hard, rm -rf, terraform apply), in Bash and PowerShell.

Keeps work off protected branches: no commit, merge, rebase, cherry-pick, am or push on main/master/release/* (or an explicit push to one), with an optional auto-branch for commits.

Stops accidental truncation of real code: no "// ... rest of the code" placeholders over real code, and a question before a Write or Edit throws away most of a file.

Supply-chain check before installs: npm/pnpm/yarn/bun/npx, pip/uv/poetry/pipx, cargo and gem packages are looked up first; nonexistent names are refused, brand-new, unpopular, deprecated or lookalike ones need your yes.

Protected files and a project boundary: Claude can't edit .env, keys or .git, asks before touching lockfiles and migrations, and asks before writing outside the project.

Notices the commands you keep approving by hand and offers a one-click standing allow rule (never for risky or interpreter-wide commands).

Keeps credentials out of your code, your shell commands and Claude's context: blocks hard-coded secrets in edits, asks before commands with literal keys, redacts secrets from tool results and flags them in prompts.

During long turns, haiku writes one line above the prompt every ~30 s on what Claude is doing and what comes next, from a compact log of its tool calls; a one-line recap toast after turns over two minutes.

Opt-in: after a turn that adds or changes functions, sonnet (or haiku) drafts focused unit tests in the background, in the repo's framework and style; Review, Add & run (only that file), or Dismiss; never writes without a press; daily budget cap.

Prompt-cache hit rate, a live warm/cold countdown, cache-bust alerts with likely causes, savings, and optional keep-warm pings.

Context-window gauge: a fill bar in the readout, toasts as it fills, a /ctx breakdown pane with Compact now, and optional auto-compaction between turns.

Spend tracking across sessions: session and today's cost in the readout, daily and weekly budgets with toasts and an optional hard stop, and a /spend pane.

One compact status line: model, context fill, cache hit and warm countdown, session cost, the fullest rate limit, and git branch with changed files.

Subscription rate limits at a glance: each window and its reset in the readout, toasts at 75% and 90% and when your pace beats the reset, and a /limits pane.

Every subagent, live: a /subagents pane with status, model, elapsed time, steps, tokens, last tool and answer, plus a band while any run.