Troubleshoot installation, sign-in, folder selection, execution, automation, and extension issues.
If chat is available in Qoder, type
In a local Qoder task, select
Confirm the operating system and architecture, verify the installer source, restart the client, and record the version, operating system, and exact error if the problem remains.
If a window encounters an error, follow the recovery view’s reload guidance and check task status afterward. Reloading the interface does not confirm that a failed tool action was retried. Check existing output before continuing to avoid duplicate operations.
Check network connectivity and system time, then run Network diagnostics to identify the affected online service.
If you are signed out, run diagnostics from the sign-in screen and check the failed service and the latest recorded sign-in attempt.
In Coding, confirm the workspace and run location shown in the composer. In General, confirm the selected folder. Then check file permissions, the absolute path, indexing status, and exclusion rules.
Inspect the command, exit code, and error output. Check access mode, system permissions, network access, and credentials. Do not use Full Access merely to hide an unexplained failure.
After a Git read times out on Windows, use an available retry action in the corresponding task monitor or branch view if the original read has exited. Check the state of operations that are still running first.
Confirm that it is enabled, the schedule is correct, Qoder is running, and the device is online and awake. Inspect Automations → Run history for the actual status.
Confirm that the Skill, Plugin, or Connector is installed and enabled. Check scope, configuration, credentials, network connectivity, and Hook match conditions.
If the issue remains, use Feedback to submit reproduction details.
/ in a local task, find and select qoder-helper, and describe the issue. Include your version, the steps you took, what happened, and any error message. Follow the explanations and manual steps in the reply, then repeat the original action to check whether the issue is resolved. qoder-helper supports local tasks, not Remote SSH or WSL remote tasks. If Qoder will not start or chat is unavailable, use the relevant steps below.
Ask Qoder Helper to inspect relevant logs
In a local Qoder task, select qoder-helper, describe the event, time, and impact, and explicitly ask it to inspect relevant logs. Helper can read recent relevant excerpts to assist diagnosis; distinguish log evidence from hypotheses in its response.
Check diagnostic material for sensitive information before sharing. Before changing a setting, review the exact setting, current value, and expected effect, then follow the current approval mode. This local workflow does not automatically apply to Remote SSH or WSL tasks.
If a Hook appears to slow down a task, explicitly ask Qoder Helper to inspect relevant Hook timing and diagnostics. Correlate them with the event time and logs. After editing Hook configuration, check fresh diagnostics instead of relying only on old records.
New Qoder app installation fails
- Update Qoder to the latest version. Alternatively, uninstall Qoder and download the latest version from the official Qoder website.
- Reinstall the Qoder app.