Common error messages, causes, and solutions, as well as frequently asked questions.
This page summarizes the meanings and solutions for common error messages, along with some frequently asked questions. For more specific troubleshooting, refer to the dedicated troubleshooting pages.
Network requests fail, usually due to network or proxy issues.
You are not currently signed in, or your credentials have expired.
Tool calls are blocked by the permissions system or a Hook.
The configuration is overridden by a higher-priority source, requires a restart, or has formatting errors. See Configuration not applied.
Use
Use
Use
Use
Use
Use
Common Errors
fetch failed / Request failed
Network requests fail, usually due to network or proxy issues.
- Check network connectivity and proxy configuration. See Network, Proxy, and VPC Issues.
general.retryFetchErrors(enabled by default) automatically retries some of these errors.
Unauthenticated / Sign-in required
You are not currently signed in, or your credentials have expired.
- Run
/loginto sign in again, or setQODER_PERSONAL_ACCESS_TOKEN. - See Sign-in and Authentication Issues for details.
command not found (command not found: qodercli)
qodercli is not in PATH. See Installation and Upgrade Issues.
Permission Denied / Action Blocked
Tool calls are blocked by the permissions system or a Hook.
- Use
/permissionsto view the current permission mode and rules, and adjust them if necessary. 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.
Configuration not in effect
The configuration is overridden by a higher-priority source, requires a restart, or has formatting errors. See Configuration not applied.
Frequently Asked Questions
How to check the version?
How to run non-interactively in scripts?
Use --print (-p), which can be combined with --output-format json for easier programmatic consumption. See Run in Scripts.
How to resume the previous session?
Use qodercli --continue (-c) to resume the most recent session, or --resume (-r) to select a historical session. See session management.
How to switch models?
Use -m <model> from the command line, or /model during an interactive session. See Select model and reasoning effort.
How to roll back to previous code or conversation?
Use /rewind or the Checkpoint feature to restore. See Undo and Restore.
How to view usage and quota?
Use /usage to view usage statistics. See Usage and Quota.
What to do when the context window is almost full?
Use /compact to proactively compress the context, or start a new session. See Performance, Context, and Long Session Issues.
Getting More Help
- Run
/helpin an interactive session to view help, or/docsto open the documentation. - Use
/feedbackto submit feedback. - Enable
--debug(-d) to get debug logs for troubleshooting.
Next Steps
- Installation issues: Installation and Upgrade Issues.
- Sign-in issues: Sign-in and Authentication Issues.
- Network issues: Network, Proxy, and VPC Issues.
- Performance issues: Performance, Context, and Long Session Issues.
- Loading issues: Memory, Skills, and Agent not loaded.
- Configuration issues: Configuration not applied.
- Extension issues: Hooks, MCP, and plugin issues.