Troubleshooting

Below are some approaches for troubleshooting problems with cecli:

• Reproduce the problem with the smallest possible command and set of files.
• Check the terminal output for the first error, rather than only the final message.
• Confirm that cecli and its dependencies are up to date, then retry if the problem may be version-related.
• Try --verbose or --debug when more diagnostic information is needed, and save the resulting logs for an issue report.
• If the problem involves a model or provider, record the model name, provider, and relevant configuration without sharing credentials.

Create logs for an issue report

When asking for help in Discord or opening a GitHub issue, include the relevant command, cecli version, operating system, model/provider, and a log captured while reproducing the problem. Do not include API keys, tokens, passwords, or other sensitive information.

Use --verbose and --debug for additional diagnostic output:

cecli --verbose --debug

If the problem involves an LLM request, --debug may also create request logs under .cecli/logs/. Review and redact those files before sharing them, since request logs can contain prompts or other private project content. Attach the redacted log files to your GitHub issue or upload them in Discord, and briefly explain what you expected to happen and what happened instead.

Tip:
Use /help <question> to ask for help about using cecli, customizing settings, using LLMs, etc.