Semantic search unavailable in Codespaces due to missing workspace index

[charlckh]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

VS Code

Body

The workspace index in GitHub Codespaces is not being created correctly, and the UI shows Codebase index not available. I

wonder why the workspace index fails to build and how to restore semantic search?

[dorukcodes]

Welcome to the GitHub Community 👋

This usually happens when the Codespace semantic index hasn’t been created yet or failed during setup. The “codebase index not available” message typically means the indexing process didn’t complete.

You can try restarting the Codespace or reopening it in VS Code — this often triggers the index to rebuild. If that doesn’t work, recreating the Codespace usually fixes it.

More info here:

https://docs.github.com/en/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces
https://docs.github.com/en/copilot/github-copilot-in-codespaces/about-github-copilot-in-codespaces

If it still persists, it may be a temporary issue on GitHub’s side.

[Gecko51]

The "Codebase index not available" in Codespaces is different from the local workspace index in desktop VS Code. In Codespaces, Copilot primarily relies on a remote GitHub-hosted semantic index built from your repo, not a local one. When that message shows up, it's usually one of three things:

The repo hasn't been indexed yet. Any new or private repo enters a queue after the first push. Small repos get picked up within minutes, larger ones can take several hours on the first pass.

The repo is above the indexing size threshold. Very large repos (huge file count or over the size limit) get skipped by the automated indexer, there's no way around that other than narrowing what Copilot sees via a .copilotignore.

Indexing is disabled at the org/enterprise level. If you're in an org with Copilot policies, a policy can turn off repo indexing. Check the Copilot settings at the org level, not just your personal ones.

Open the command palette inside the Codespace and run the Copilot workspace indexing command (type "index" in the palette, you'll see a rebuild option). That forces a fresh attempt and if it fails you'll get a clearer error in the Copilot output channel.

Quick way to confirm it's a remote-index issue and not a local one: @workspace queries in Copilot Chat still work against whatever local fallback exists. If those return sensible results but the UI still says "not available", you're looking at a remote-index delay. If @workspace also returns nothing useful, it's a config/policy problem on the repo or org side.

What's the repo size roughly, and is it in a personal account or an org?