CLI errors

Reasonix command-line troubleshooting checklist

Use these commands to check Node/npm, DeepSeek API keys, Go build tooling, and terminal interaction issues without exposing secrets.

Triage order

Check command and version first, credentials second, and local tooling last. That avoids unnecessary reinstalls and keeps secrets out of public pages.

Version and entry point

Confirm node -v, npm dist-tags, and whether npx or the global command points to the intended package.

Credentials and config

Confirm that the DeepSeek API key exists and stays in local environment, Reasonix config, or a safe secret manager.

Toolchain and terminal

Check Go/make only for source builds; check terminal, shell, Windows Terminal, or Git for Windows only for interaction bugs.

npx reasonix code does not start or resolves the wrong version

node -v
npm view reasonix engines
npm view reasonix dist-tags
npm cache verify
npx reasonix@latest code

Use live npm metadata for the current Node requirement and package tags. Clear npm cache or pin the intended tag if npx resolves an unexpected package.

DeepSeek API key is missing or credentials expired

open https://platform.deepseek.com/api_keys
printenv DEEPSEEK_API_KEY
npx reasonix code

Confirm that a DeepSeek Platform API key exists first. Do not commit keys to public repositories.

Source build cannot find make or Go

go version
make --version
git switch main-v2
make build

main-v2 is the Go rewrite branch, so source builds require a Go toolchain and make.

Terminal scrolling, selection, or paste behaves incorrectly

echo $TERM
printf '\e[?1000h'
# Windows users should also review Git for Windows and Windows Terminal settings

GitHub issue #2649 tracks Windows Terminal scrolling, PageUp/PageDown, and selection-copy behavior.

Messages beginning with # are not received by the agent

npx reasonix@latest code
# Temporary workaround: add a leading space or newline, then follow issue #2658

This was still an open GitHub bug report on 2026-06-02, so it belongs in the error tracking area.

Need to confirm DeepSeek API connectivity

curl -s https://api.deepseek.com | head
# Then return to Reasonix and run /help or /pro to verify model switching

Network reachability is not the same as successful authentication. Key and Reasonix config still need separate checks.

GitHub issue tracker

#6582An open bug report says delivery-readiness prompts can keep reappearing after users leave delivery mode #6578An open feature request asks for clearer MCP-in-use indicators inside the workspace UI #6577An open bug report says the new TUI status bar no longer shows cache, branch, or balance details