You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Codebase indexing should be supported as it is in the Vscode extension #20
I'm trying GitHub Copilot CLI as an alternative to Claude Code for devs that like the terminal UI and don't wish to use VSCode. The main feature Claude Code doesn't have that GitHub Copilot in VSCode has is automatic remote workspace indexing for repositories hosted in GitHub.
If Copilot CLI doesn't use the code indexing capabilities that makes GitHub Copilot in VSCode shine, then there's no reason for our existing Claude Code users to even try Copilot CLI, unfortunately. We have a lot of large code repositories, and tests have shown a huge difference in performance between GitHub Copilot in VSCode against Claude Code for complex questions that require scanning a lot of files to produce a good answer.
Can we get Copilot CLI to support using code indexing? This is a strong selling point
@numman-ali@mamoreau-devolutions would love to hear your perception on how this would improve the quality of the agentic coding loop? What do you think this will improve in terms of agent capability?
Isn't it sufficiently obvious from what has already been said? Excellent code search performance not only means the agent can run faster, but it also reduces token usage by spending less time ingesting unrelated data, and increases accuracy with fewer cases where the agent failed to find something that was there to be found. This is a shining feature inside VSCode, we just need the same in Copilot CLI
This appears to be resolved as of GitHub Copilot CLI v1.0.105. Please update to that release or a newer stable version. We're closing this as completed. If it still happens, please comment with your version and reproduction steps.
Activity
mamoreau-devolutions commentedon Nov 12, 2025
I'm trying GitHub Copilot CLI as an alternative to Claude Code for devs that like the terminal UI and don't wish to use VSCode. The main feature Claude Code doesn't have that GitHub Copilot in VSCode has is automatic remote workspace indexing for repositories hosted in GitHub.
If Copilot CLI doesn't use the code indexing capabilities that makes GitHub Copilot in VSCode shine, then there's no reason for our existing Claude Code users to even try Copilot CLI, unfortunately. We have a lot of large code repositories, and tests have shown a huge difference in performance between GitHub Copilot in VSCode against Claude Code for complex questions that require scanning a lot of files to produce a good answer.
Can we get Copilot CLI to support using code indexing? This is a strong selling point
EvanBoyle commentedon Nov 13, 2025
@numman-ali @mamoreau-devolutions would love to hear your perception on how this would improve the quality of the agentic coding loop? What do you think this will improve in terms of agent capability?
mamoreau-devolutions commentedon Nov 21, 2025
Isn't it sufficiently obvious from what has already been said? Excellent code search performance not only means the agent can run faster, but it also reduces token usage by spending less time ingesting unrelated data, and increases accuracy with fewer cases where the agent failed to find something that was there to be found. This is a shining feature inside VSCode, we just need the same in Copilot CLI
copilot-cli-bot commentedon Oct 28, 2026
This appears to be resolved as of GitHub Copilot CLI v1.0.105. Please update to that release or a newer stable version. We're closing this as completed. If it still happens, please comment with your version and reproduction steps.