Desktop troubleshooting

For KeenKind API requests from Codex, ZCode, or another tool, start with API troubleshooting.

First confirm the current chat, directory, model, and permissions. Many failures come from a mismatch between the task context and the current page.

Model does not respond

1. Check that the configuration and model are enabled in Settings > Configuration.
2. Check endpoint, model ID, and key.
3. Match the provider and API type.
4. Send a simple message in a new chat to rule out current-chat state.
5. Check provider rate-limit, balance, or region errors.

Choose the matching provider for services such as DeepSeek even when they support OpenAI Chat Completions.

Tools do not run

• Check the permission mode near the composer.
• Confirm the working directory.
• Check required Skills, MCP, or plugins in Settings > Extensions.
• Expand the failed call for its specific error.
• Stop the current task before retrying to avoid overlapping operations.

Files or images cannot be used

• Check format, size, and count limits.
• Confirm files are still in their original locations.
• Resolve workspace-relative paths from the current project.
• Try previewing Office documents, PDFs, or images in the right panel.
• Password-protected, damaged, or scanned files may lack extractable text.

Browser shows the wrong page

• Browser state belongs to each chat; check the current chat.
• Inspect the selected tab and URL.
• Close unused tabs to avoid repeated page openings.
• Complete sign-in, CAPTCHAs, QR codes, and payments yourself.
• After a page changes, let KeenKind inspect it again before continuing.

Extension does not load

1. Disable and re-enable it.
2. Check the platform, command path, and environment variables.
3. Inspect details or plugin debugging diagnostics.
4. Update or reinstall the extension.
5. For persistent third-party failures, contact its author with version and error details.

Subagents and persistent tasks

• No tool execution: check the role’s approval policy and allowed risk categories.
• Stuck in queue: concurrency slots are occupied; the run starts when one becomes available.
• Role edits have no effect: existing runs keep their original snapshot; create a new run.
• Long task stops progressing: check whether information or plan confirmation is needed.
• Planner or verifier unavailable: check for usable models in Settings > Persistent tasks.

Collect logs

Provide support with:

• KeenKind version.
• Operating system version.
• Model provider and API type.
• Reproduction steps.
• Error screenshots.
• Logs for the relevant time range.

Windows production logs are usually in:

%LOCALAPPDATA%\Keenkind\production\logs

Development logs are in %LOCALAPPDATA%\Keenkind\development\logs.

Remove API keys, cookies, personal file content, and other sensitive information before sending logs or screenshots.