CLI: @file context provider does not find .cc files.

[mkhmkhgit]

Path: /guides/cli

When using the Continue CLI, the @file context provider does not find files with the .cc extension. The same files are found without issue when using the VS Code extension with the same Continue configuration.

Steps to reproduce:

Have a workspace containing C++ source files with .cc extension
In the Continue CLI, type @path/to/file.cc
File is not found

Expected behavior: .cc files should appear in @file results, same as in the VS Code extension.
Workaround confirmation: Copying the same file with a .cpp extension makes it immediately discoverable via @file in the CLI.
Environment:

OS: Linux
Continue CLI v1.5.43

VS Code extension works correctly with the same files and configuration

Continue CLI works correctly with .cpp files

Notes: .cc is a standard C++ file extension, widely used in Unix/Linux environments and Google-style codebases. The CLI's file discovery likely has a hardcoded extension allowlist that is missing .cc (and possibly other valid C++ extensions like .cxx, .C, .c++).

[sestinj]

Related issues:

• @file only sends file path to AI but not content #8507 - @file only sends file path to AI but not content (different @file context provider bug where files are found but content is not properly included)