Indexing problems

Indexing is what lets an answer point at the file that broke, not only the file that crashed. When an answer says DebugAI could not see your code, start here.

Two commands tell you where you stand:

• DebugAI: Check Index Status says what this window has indexed.
• View Details, on the message an index run ends with, opens the DebugAI Indexing output with the list of files DebugAI stored.

Each heading below is the message as DebugAI shows it, without the DebugAI: in front. N and M stand for the numbers on your screen.

When an index run endsCopy Anchor Link

Indexed N files. DebugAI can now trace an error across your codebase.Copy Anchor Link

Nothing is wrong. Every file DebugAI tried was stored. View Details lists them.

DebugAI indexed N files so far. The remaining M are queued for the next run in about 15 minutes.Copy Anchor Link

The run went faster than the server's limit allows (600 index requests per 15 minutes for an account), so it stopped early. The files it stored already work: you can debug now, and answers improve once the rest are in. Press Finish indexing after about 15 minutes, or run DebugAI: Index Entire Workspace again then.

DebugAI indexed N files. M more in this project were not indexed, so answers that need them will be incomplete.Copy Anchor Link

The message goes on to say that nothing failed and there is nothing to retry, and that is true. One of two limits was reached:

• The free plan keeps 200 files per project. Pro and Team have no per-project cap.
• One run sends at most 500 files, on any plan. When a project has more, DebugAI picks which. Source files come before config files, though a tenth of the places is kept for config. Tests, snapshots and vendored files rank below other source. Running it again picks the same files.

With debugai.autoIndex on, each file you open or save is sent on its own, so on Pro and Team the files you work in join the index as you go.

Indexed N files. M could not be indexed and were not checked. Run indexing again to retry them.Copy Anchor Link

Some files failed for a reason that is neither a plan limit nor the rate limit, such as a dropped connection or a server error partway through. Press Finish indexing, or run DebugAI: Index Entire Workspace again.

The server asked us to slow down before anything was stored. Nothing was indexed. Try again in about 15 minutes.Copy Anchor Link

The account's index limit (600 requests per 15 minutes) was already used up, for example by another window indexing a large project. Wait 15 minutes, then press Try again.

No files could be indexed. This is not a result about your codebase.Copy Anchor Link

Every file DebugAI tried failed. That points at the connection or the server, not at your code. Check that this machine can reach DebugAI (see Behind a proxy or firewall), then press Try again.

No files were indexed.Copy Anchor Link

Nothing failed and nothing was stored. Either every file found was one DebugAI never keeps, or the project is already at the free plan's 200 files, so nothing new fits.

DebugAI found no files to index in this workspace.Copy Anchor Link

The open folder holds no file DebugAI indexes. It takes source files ending in .js, .jsx, .ts, .tsx, .py, .mjs, .cjs, .java and .cs, plus config files such as package.json, tsconfig.json, pyproject.toml, requirements.txt, Dockerfile and go.mod. Open the folder that holds your code, not a parent folder with only notes in it.

DebugAI could not search this workspace for files, so nothing was indexed.Copy Anchor Link

VS Code's own file search failed, so DebugAI had no list of files to send. Run DebugAI: Index Entire Workspace again. If it keeps happening, write to support@debugai.io.

A file is missing from the indexCopy Anchor Link

Some files are never indexed, by design:

• .env and every file like it (.env.local, staging.env and so on).
• Key and certificate files: .pem, .key, .pfx, .p12, .jks, .keystore, .ppk, .asc, .gpg, .kdbx, .crt, .cer, .der, .cert, .secret.
• Files whose whole name is a credentials word, such as secrets.py, credentials.ts or password.js.
• appsettings*.json, Docker Compose files, lock files, minified .min.js and .min.css files, and .map files.
• Anything inside node_modules, dist, build, out, .git, __pycache__, .venv, venv, env, .next, .nuxt, coverage, site-packages, dist-packages, .tox, .pytest_cache, eggs, .eggs, .terraform, secrets, .secrets, .ssh, .gnupg, .aws, .azure, .kube, .docker or a folder named .env.

Folders are judged by their path inside your workspace. A project that itself sits under a folder called build still indexes. A folder called build inside your workspace does not.

Files are cut at 50 KB. The rest of a longer file is not sent.

Indexing one fileCopy Anchor Link

DebugAI: Index Current File sends the file open in the editor. With no file open, it does nothing.

File indexed.Copy Anchor Link

Nothing is wrong.

This file is queued and will index on the next run, in about 15 minutes.Copy Anchor Link

The account's index limit is used up for now. Run DebugAI: Index Current File again in about 15 minutes.

Could not index this file.Copy Anchor Link

The request failed. Run the command again.

This file was not indexed. Secret files are never indexed, and free plans cap the project at 200 files.Copy Anchor Link

Either the file is one DebugAI never keeps (see the list above), or the project is already at the free plan's 200 files.

Check Index StatusCopy Anchor Link

No workspace open. Open a folder to begin indexing.Copy Anchor Link

DebugAI indexes a folder, not loose files. Use File > Open Folder.

Set your API key to start indexing. Run "DebugAI: Set API Key" from the command palette.Copy Anchor Link

You are not signed in. Run DebugAI: Sign In.

Indexing in progress (n/t files, p%)...Copy Anchor Link

A run is going. The status bar shows the same percentage.

N files indexed. Ready for errors.Copy Anchor Link

Nothing is wrong.

DebugAI has not indexed this workspace in this window yet. Run "DebugAI: Index Entire Workspace" to index it now.Copy Anchor Link

Check Index Status only knows what happened in this window. An index from an earlier session is still on the server. Run DebugAI: Index Entire Workspace if you want to be sure it is current.

Nothing happened when VS Code startedCopy Anchor Link

Automatic indexing runs when VS Code starts, and only when all of these hold:

• You are signed in, and you were signed in when VS Code started. The first index after a new sign-in does not start on its own: press Index workspace on the DebugAI connected message, or run DebugAI: Index Entire Workspace.
• The debugai.autoIndex setting is on (it is by default).
• No full index of this project finished in the last 15 minutes. If one did, the automatic run is skipped without a message. A command you run yourself always runs.

Answers still say DebugAI could not see your codeCopy Anchor Link

If an answer reads Insufficient context for specific fix after you indexed, see Answers and limits. It says which of several reasons applied.