Problem
The claude-context MCP indexer fails to process files without extensions.
I am not able to index bash files that have no extensions.
Root Cause
The indexer uses a hardcoded DEFAULT_SUPPORTED_EXTENSIONS array in packages/core/src/context.ts that filters files before they reach the splitter. This design assumes all indexable files have extensions for language detection and parsing.
Impact
- Extension-less executable scripts cannot be searched semantically
- Reduces codebase coverage.
- Limits ability to find command implementations and shell utilities
Proposed Solutions
- Add extension-less file support: Modify
DEFAULT_SUPPORTED_EXTENSIONS to include a pattern or special case for extension-less files
- Content-based detection: Implement file type detection based on shebang lines (
#!/bin/bash) or file content
- Explicit inclusion parameter: Add
includeExtensionless: boolean option to force processing of extension-less files as shell scripts
Problem
The claude-context MCP indexer fails to process files without extensions.
I am not able to index bash files that have no extensions.
Root Cause
The indexer uses a hardcoded
DEFAULT_SUPPORTED_EXTENSIONSarray inpackages/core/src/context.tsthat filters files before they reach the splitter. This design assumes all indexable files have extensions for language detection and parsing.Impact
Proposed Solutions
DEFAULT_SUPPORTED_EXTENSIONSto include a pattern or special case for extension-less files#!/bin/bash) or file contentincludeExtensionless: booleanoption to force processing of extension-less files as shell scripts