Skip to main content
Troubleshooting

Error Messages and FAQ

Common error messages, their causes and solutions, plus frequently asked questions

This page collects the meanings of common error messages and how to resolve them, along with some frequently asked questions. For more focused diagnosis, see the dedicated troubleshooting pages.

Common errors

fetch failed / request failed to send

A network request failed, usually related to networking or proxies.
  • Check network connectivity and proxy configuration; see Network, Proxy, and VPC Issues.
  • general.retryFetchErrors (on by default) automatically retries some errors of this kind.

Not authenticated / sign-in required

You are not signed in or your credentials are invalid.

Command not found (command not found: qodercn)

qodercn is not on PATH. See Installation and Upgrade Issues.

Permission denied / operation blocked

A tool call was intercepted by the permission system or a hook.
  • Use /permissions to view the current permission mode and rules and adjust if needed; you can also press Shift+Tab to switch permission modes.
  • If blocked by a hook (exit code 2), check the feedback message; see Hooks, MCP, and Plugin Issues.

A setting does not take effect

The setting is overridden by a higher-priority scope, requires a restart, or has a format error. See Settings Not Taking Effect.

Frequently asked questions

How do I check the version?

qodercn --version

How do I run non-interactively in scripts?

Use --print (-p), optionally with --output-format json for programmatic consumption. See Run in Scripts.

How do I continue the last session?

Use qodercn --continue (-c) to continue the most recent session, or --resume (-r) to pick a past session. See Session Management.

How do I switch models?

Use -m <model> on the command line, or /model in an interactive session. See Models and Reasoning Effort.

How do I roll back to earlier code or conversation?

Use /rewind or the Checkpoint feature to restore. See Undo and Restore.

How do I check usage and quota?

Use /usage to view usage statistics; see Usage and Quota.

The context is almost full — what do I do?

Use /compact to compress proactively, or start a new session. See Performance, Context, and Long-Session Issues.

Getting more help

  • Run /help in an interactive session for help, and /docs to open the documentation.
  • Use /feedback to submit feedback.
  • Enable --debug (-d) to get debug logs for pinpointing issues.

Next steps