Common Issues
The most common snags when setting up or trusting a result, and the fastest way through each one.
| Symptom | What to do |
|---|---|
| Tools do not appear in the AI coding tool | Finish the website wizard, then restart or reload the tool. |
| Token or auth error | Return to the dashboard and regenerate or re-copy the trial token. |
| Wrong branch or missing SHA | Rerun the same guided prompt with an explicit branch/ref and commit, or use AUTO_DEFAULT_BRANCH plus latest and verify the resolved SHA. |
| 0 source files, or “No source files found” | Confirm the repo/ref contains a supported source. Prompt-only, Markdown-only, and manifest-only repos are not source-code audit targets. |
| Output lacks file paths or line references | Treat it as incomplete and rerun the guided prompt, or ask for current-ref source evidence. |
| PR review mixes diff and applied source | Rerun with the correct ref, or explicitly label the diff as diff evidence only. |
| Security report says clean without probes | Treat as unsupported; use UC-02 and require adversarial probes plus source-to-sink evidence for the inspected scope. |
| Setup says “unhealthy,” or only one MCP server connects | Finish the website setup, then reload the IDE. Confirm both Semantic and Codebase appear in the IDE and run the setup health check again. If only one server connects, your token is fine, that server's URL or configuration is the more likely problem. If it still fails, contact support with the server name and error message, never the token. |
| GitHub App installed, but no bot review or the check stays pending | Open the PR's Checks tab and make sure you're looking at its latest commit. Confirm the App has access to that repository in GitHub's installed-app settings. Open a pending or failed check for details; pending does not necessarily mean failure. If the bot has commented, @rubberduck status can show its progress, and @rubberduck review (or GitHub's Re-run checks) starts a fresh one. If nothing appears, send support the PR link and commit SHA. GitHub explains check statuses here. |
| IDE analysis is still computing | Keep the same IDE conversation open and watch that run for progress updates rather than starting a second analysis while the first is active. If it returns an error or never returns a report, send support the error message plus the repository and ref. |
| Report shows zero files or an empty graph | Check that the selected branch and commit actually contain supported source, not just a README. RubberDuck analyzes Python, TypeScript, JavaScript, Vue, C, C++ and Go today; files in other languages will still show up as an empty graph. For Semantic analysis, confirm the repository was loaded before querying it. If the correct ref has supported code and the report is still empty, send support the repo/ref, commit SHA, and report link. |