Install & update

Install

Node ≥ 22.5:

bash

npm i -g @silassolivagus/deepcode

Just run deepcode. On first launch a wizard prompts you to paste your key (written to ~/.deepcode/settings.json, mode 600):

bash

deepcode

If you already have a key, skip the wizard and set an environment variable instead:

bash

export DEEPSEEK_API_KEY=sk-...
deepcode

The default model is deepseek-v4-pro. To switch providers, see multi-provider config; to edit the config file directly, see settings.

It's a global npm package, so updates go through npm too:

bash

npm i -g @silassolivagus/deepcode@latest

or:

bash

npm update -g @silassolivagus/deepcode

After startup deepcode checks for a new release in the background (at most once per 24 hours) and reports the result in the footer:

npm global install in a writable directory → it upgrades itself in the background; the footer then shows ✦ 已升至 <version> · 重启生效, and the new version takes effect on the next session.
Any other install shape (pnpm / bun / npx cache / a directory that needs sudo) → it only shows ✦ 有新版 <version> · <the matching upgrade command> and never touches disk.
A repository working copy (running from source) → completely silent: no check, no prompt.

Type /update in a session to check immediately, bypassing the 24-hour throttle. Three switches:

Switch	Effect
`"autoUpdates": false` (settings.json)	Still checks and prompts, but never upgrades on its own
`DEEPCODE_DISABLE_AUTOUPDATER=1`	Same, as an environment variable
`DEEPCODE_DISABLE_UPDATES=1`	Everything off: no query, no prompt, and `/update` refuses outright

bash

npm uninstall -g @silassolivagus/deepcode

If your machine needs a proxy to reach the API, deepcode automatically picks up the standard proxy environment variables — no extra config needed:

bash

export https_proxy=http://127.0.0.1:7890
deepcode

Multi-provider config: switch between DeepSeek / GLM / Kimi / self-hosted backends.
Settings: settings fields for ~/.deepcode/settings.json.