Error Codes

The errors you may see in your editor or on the dashboard, what they mean, and how to fix them.

When a Scrubby tool can't complete, your editor shows the error message it returned. When something fails on the dashboard, the page shows the reason. This page lists the situations you're most likely to hit and how to resolve each one.

Repositories

What you seeWhat it meansWhat to do
Repository not foundThe repository doesn't exist or you don't have access to it.Check the owner/repo name and that you can access it on GitHub.
Repository not indexedA tool that needs an indexed repository was used before indexing finished (still pending, indexing, or failed).Ask your editor to run scrubby_index and wait for it to finish. If it failed, see Indexing Stuck.
File not found in the indexed snapshotThe file isn't in the last index. Scrubby reads from GitHub, not your local working tree.Commit and push the file to the indexed branch, then re-index.
File has no embedding yetSimilar-file search was run on a file that's indexed but not yet embedded.Re-index the repository, then try again.

Billing

What you seeWhat it meansWhat to do
No active subscriptionYou tried to connect a repository without an active trial or subscription.Start a trial or subscribe. See Billing.
Repository limit reachedConnecting this repository would exceed your plan's included private repositories.Upgrade, or accept the per-repository overage. See Billing.
Trial already usedThe account already used its one free trial.Subscribe to a paid plan.

Authentication

What you seeWhat it meansWhat to do
Not authenticatedYour editor's session with Scrubby expired or never completed.Reconnect from your editor (in Claude Code, run /mcp). See Authentication.

Indexing and reviews