Updates and troubleshooting

Keep DCode up to date, check your setup with dcode doctor, and fix the problems people run into most.

On this page

Start with dcode doctor: it checks the usual causes in one go and says how to fix each one. The sections below cover what it cannot see.

Update DCode

  • Desktop app. When an update is ready, DCode offers Restart to update; Check for updates in the Help menu looks for one now. Turn on Automatically download and install updates in Settings, General to have it done for you (Install).
  • CLI. At start, the CLI asks Update now? [Y/n] when a new version is out. To update by hand: npm install -g @dipoleml/dcode-cli@latest. dcode --version prints the version you have (Install).

The current version is DCode 2.5.0. What changed in each release is on the Changelog.

Check your setup

shell
dcode doctordcode doctor --json
What doctor reportsWhat to do
Node.js ... is too oldInstall Node.js 22.13 or newer (23.4 or newer on Node.js 23). An older Node.js stops the CLI at start with exit code 3.
PATH contains a stray double quote (") that breaks the dcode command in cmd.exeOn Windows, open Settings, System, About, Advanced system settings, Environment Variables, Path, and remove the quote.
Cannot reach the Dipole ML Inc. serversCheck your internet connection, VPN or proxy.
Not signed inPress Enter in the workspace, or run dcode login.
Browser Use: no Chrome or Edge foundInstall Chrome or Edge, so DCode can browse for you.
Computer Use needs permissionOn a Mac, open System Settings, Privacy & Security, and allow your terminal under Accessibility and Screen Recording.
git is not installedOptional, but needed for diffs and for parallel work on separate branches.

Common problems

dcode: command not found

The folder npm installs commands into is not on your PATH. Open a new terminal first. If it still fails, npm prefix -g shows npm's folder: add its bin folder to your PATH. The one-line installer for macOS and Linux tells you this itself, and when npm's folder needs administrator rights it installs for your user only, in ~/.dcode/npm, and prints the line to add to your profile (Install). On Windows, also check for a stray quote in PATH, as above.

Sign-in problems

  • The browser does not open. Run dcode login --no-browser, open the link it prints on any device and enter the sign-in code (Sign in).
  • A script stops with Not signed in. A -p run found no saved sign-in and no key, and exited with 2. Run dcode login on that machine, or set DCODE_API_KEY.
  • DCODE_API_KEY was refused. Check the key in your dashboard: it may be mistyped, revoked or expired. Create a new one if you need to (Caps, expiry and revoking).

A usage limit is reached

The message names the limit and when it resets, and links to the pricing page. /usage in the CLI and the rings in the app's sidebar show how much is left. How DCode counts against your plan is on Billing source.

Behind a proxy or a company network

In the desktop app, open Settings, General:

  • HTTP Proxy sends the model, MCP, command and app traffic through your proxy. The app does not read the system's proxy variables for this. Left blank, that traffic connects directly and the built-in browser follows your system proxy settings.
  • No proxy lists hosts that connect directly, separated by commas, for example localhost,127.0.0.1,.example.com.
  • Custom certificate takes the path of a PEM root certificate, for a network that inspects its traffic.

Restart the app after changing them.

DCode keeps asking, or a script stops on a step

The permission mode decides what asks. Answer Always allow in this project for a step you trust, or pick a freer mode. In a -p run, a step that would ask is refused instead, so give the run the mode and the allowed tools it needs (Permission modes).

A hook, plugin or instruction has no effect

Instructions, project memory, hooks, plugins and new MCP servers are read when a session starts. Start a new session after changing them: a new chat in the app, /new in the CLI. Hooks that come with a project also need your trust before they run (Hooks).

Pull requests say Needs setup

The desktop app opens pull requests with the GitHub CLI, gh. Install it, sign in, and choose Check again. The project also needs a GitHub remote (Pull requests).

A remote connection fails

Read the connection log in the wizard: it shows the step that failed. If the server cannot download DCode's files itself, set Resource download method to Download locally, then upload (SSH).

Get more detail

Add --verbose to any CLI command, or set DCODE_LOG_CONSOLE=1 for a -p run, to print the full error output. An error in a -p run is one line on standard error with the run's traceId.