npm:
codsh-cli· command:codsh
/ship takes one sentence to verified code. A terminal coding agent on the DeepSeek Harness.
npm install -g @deepseek-ai/dsh codsh-cli
# already have dsh? npm i -g codsh-cli
codshZero-dependency launcher. codsh is dsh --profile code. Key: DEEPSEEK_API_KEY.
codsh --resume <id> · codsh --continue · codsh -p "task" · codsh --version · codsh update
A session says so when a newer codsh is published. codsh update moves the
pair from the shell, /update does it from inside a session, and either way
the update also moves the code profile's runtime to match — the next boot only
registers a runtime a bare npm install -g codsh-cli upgrade left behind.
CODSH_UPDATE_CHECK=off silences the automatic check; asking still asks.
Or skip the launcher:
dsh plugin --profile code add codsh-bundle
dsh --profile code/ship <one-sentence idea> — pre-flight isolation, grill, two approvals, autonomous TDD, dual-layer DoD:
- Pre-flight & Isolation — checks working tree hygiene (
ship · preflightprompt if dirty); cuts an isolatedship/<slug>branch so the base branch stays pristine. - Grill — design-tree interview; facts are inspected, each round asks the open frontier with a recommended answer.
- Spec (Gate 1) — synthesized automatically (to-spec). You confirm. Records branch, base commit, decisions, and exact proving commands.
- Tickets & Baseline (Gate 2) — tracer-bullet vertical slices plus release compliance ticket. You approve. Baseline runs across proof commands and repo guardrails.
- Landing — TDD red-to-green proof logging; 3-strike circuit breaker; cascading re-verification on resume; each green ticket is a clean commit.
- Done (Dual-Layer DoD) — verifies acceptance criteria (exit 0) and zero new repo failures against baseline; interactive delivery prompt (
ship · deliver: merge back, keep PR branch, or stay).
Bare /ship resumes an unfinished spec with cascading re-verification of prior tickets.
/ship let long diffs open in a pager instead of scrolling pastThe site shows each one as a real capture. In brief:
Reading a long session
- A submitted prompt takes the viewport top and its reply fills the space beneath it. Read back into history and the way home is the same frame: the wheel and PgDn land on it again.
- Whatever you are reading, the prompt that asked for it pins itself at the top; the next prompt pushes it away.
- A one-column timeline on the right marks the turn you are in — ticks and arrows click-jump, hover previews the real prompt lines. Shift+←/→ does it from the keyboard, and
/jumpis a searchable, reversible preview./rewindforks the conversation from before a turn you pick and continues there; the original session stays in/resume, and Esc Esc still recalls the last prompt. - Thinking and long tool output fold: click one, Ctrl+O all, and what you opened by hand stays open across later turns. A finished answer stays whole. Compaction — automatic, or
/compact— leaves a fold too: how many items and tokens became a summary, which model wrote it, and the summary itself; the hint row sayscompacting history…while it runs. /view 1opens an answer full screen,/view 1:1its first code block; Esc restores the conversation exactly./copyaddresses the same targets — raw Markdown, or fence-free code./diffreads uncommitted changes in the same reader rather than scrolling them past, and a diff card too long for its own body opens there on click. Piped, it stays lines.
Working
- Alternate screen; the box never leaves the bottom; quitting gives your shell back untouched.
- Todos stay in the chrome (Ctrl+T /
/todos). Markdown, thinking, and tool cards stream in. Drag to copy, in the transcript or the box. - Ctrl+V pastes images. While the cursor rests on the
[Image #N]token a card centered over the transcript previews it: the picture itself wherever the terminal paints one — Ghostty, kitty and WezTerm through Kitty graphics, iTerm2 through its own — and a colour half-block mosaic everywhere else. Ctrl+O, or a click on the card, opens the original in the system viewer. (Native vision; DeepSeek text models borrow Vision Exp automatically; other text routes keep the file + optional sidecar fallback.) /commands,$skills,!shell,@files — the menu sits above the box. ⇧Tab is plan mode./ui compact|comfortablesets how much room the transcript takes. Compact is the default and the shape everything above is described in; comfortable only adds — a blank row between turns, a two-line preview while thinking streams, and a higher click-to-pager threshold on expanded diffs. The choice persists across sessions.- Approvals,
/model,/resume, and/thinking(or/effort) are arrow-key widgets;/clear, Esc Esc,/init, and/updateround it out.!cmdprints in-session and the agent sees it. /thinking [level](alias/effort) configures reasoning deliberation (e.g.off,low,high,max, or shortcutson/off) with an interactive selector on TTY, per-model persistence, and active level tags in MetaBar (e.g.deepseek-chat (high)) and/status.- Away from the window, a decision waiting or a turn over ten seconds ending rings the bell and sends a desktop notification: OSC 9 on iTerm2, WezTerm, Ghostty, kitty, and Windows Terminal,
osascripton Terminal.app,notify-sendbeside it on other Linux terminals. Focused, nothing.bellandnotifyare the two switches. - An approval names the call —
Allow bash: git push origin main?— and its third answer remembers it:bash(git push *)goes to.dsh/permissions.local.json(personal; gitignore it) and the same prefix is never asked again in this project..dsh/permissions.json(committed) and~/.dsh/permissions.jsonare hand-written,{ "allow": ["tool", "tool(prefix *)", "tool(exact command)"] }; a compound command —&&,;,|, a newline — never matches a prefix.
Off a TTY it becomes a line reader: no widgets, no drawing.
Three tiers decide what a release must not break:
| Tier | Terminals | Meaning |
|---|---|---|
| First | iTerm2, Terminal.app, VS Code integrated terminal, tmux, Windows Terminal + WSL | a regression here blocks a release |
| Second | Ghostty, kitty, Alacritty, Warp | a regression here is a bug, not a blocker |
| Best-effort | native Windows (pwsh) | persistent terminals are unavailable there; the rest is expected to work |
Protocol use is progressive: the kitty keyboard protocol, focus reports, and OSC 11 theme detection are requested and take effect wherever the terminal answers; one that ignores them keeps the legacy path. Inline graphics are chosen the same way, and by what each terminal actually implements rather than by what it is — Kitty graphics on Ghostty, kitty, and WezTerm, OSC 1337 on iTerm2, a half-block mosaic everywhere else, and nothing inside tmux or screen, which forward neither.
Any OpenAI-compatible endpoint is a dsh route. Declare it once in $DSH_HOME/settings.yaml (default ~/.dsh/settings.yaml, hot-reloaded), then pick it with /model:
llm-pi-ai:
providers:
acme-gateway:
displayName: Acme Gateway
apiKeyEnv: ACME_GATEWAY_API_KEY
api: openai-completions
baseURL: https://gateway.acme.example/v1
compat:
thinkingFormat: deepseek # how a thinking level travels on the wire
supportsDeveloperRole: false # system prompt as `system`, not `developer`
maxTokensField: max_tokens
models:
- id: acme-large
contextWindow: 65536
maxTokens: 4096/model acme-gateway/acme-large switches to it and saves it as the default; /status names the route. The key resolves per request from the named environment variable, then $DSH_HOME/.credentials.yaml, then <cwd>/.env, then $DSH_HOME/.env. A gateway that rejects the request shape is a compat question: the full switch table, per-model reasoningEfforts (including false for a model that must never receive a thinking field), and modelOverrides for correcting one catalog model are in the @deepseek-ai/dsh-llm-pi-ai README.
pnpm install
pnpm run dev # build → .dev-home → boot
MOCK=markdown pnpm run dev # keyless, against the e2e mock
pnpm test
pnpm run typecheck
pnpm run test:e2e # pack, install, drive the real binary
pnpm run site:screens # re-shoot the site's terminals from the real binaryMOCK=<mode> boots against the keyless mock model: write (the default),
bash, heredoc, slow, tall, spec, markdown, reasoning, echo,
vision, and the auto-vision, auto-vision-slow, auto-vision-fail trio
behind the automatic image description. INSPECT=1 opens the Node inspector on
the app process alone, so a breakpoint does not stop the build that precedes it.
CODSH_TRACE=<path> tees every byte the viewport writes, and the size it wrote
them at, into a file. A frame that arrives corrupted is a disagreement between
what the surface emitted and what the terminal did with it, and the emitted
half is gone by the time anyone looks; replaying the file through a terminal
emulator reproduces the screen it drew. Off unless the variable is set.
pnpm run sync:dsh tracks published @deepseek-ai/dsh-* releases. This repo never forks the harness.
MIT
