Current Behavior
The project currently has two ways to exclude files from the file structure:
- Use .gitignore rules - applies user's gitignore patterns
- Use custom rules - strictly ignores files that should never be added to the project
The problem: When a folder is ignored by .gitignore rules, clicking to expand/open that folder in the UI does not load its contents. This makes it impossible to browse and select individual files or subfolders from within that ignored folder.
For custom rules, this behavior is desired and working as intended - these files should remain completely inaccessible. However, for .gitignore rules, this limitation is problematic.
Desired Functionality
Add the ability to selectively include files and folders from directories that are ignored by .gitignore rules, on a per-session/selection basis.
The UI should allow:
- Expanding folders that are ignored by .gitignore rules to view their contents
- Selecting individual files from within ignored folders
- Including entire subfolders from within ignored parent folders if needed
Use Case
There are scenarios where folders contain documentation or resources specifically prepared for AI agents (such as proposals, reference documents, or context materials). These files should not be committed to version control (hence they are in .gitignore), but they need to be temporarily present in the project folder. Different sessions may require different subsets of these documents - sometimes one section of documentation is needed, other times a different section.
Requirements
- Important: Custom rules must maintain absolute priority - files matching custom rules should remain completely inaccessible and hidden, with no ability to expand or view their contents
Current Behavior
The project currently has two ways to exclude files from the file structure:
The problem: When a folder is ignored by .gitignore rules, clicking to expand/open that folder in the UI does not load its contents. This makes it impossible to browse and select individual files or subfolders from within that ignored folder.
For custom rules, this behavior is desired and working as intended - these files should remain completely inaccessible. However, for .gitignore rules, this limitation is problematic.
Desired Functionality
Add the ability to selectively include files and folders from directories that are ignored by .gitignore rules, on a per-session/selection basis.
The UI should allow:
Use Case
There are scenarios where folders contain documentation or resources specifically prepared for AI agents (such as proposals, reference documents, or context materials). These files should not be committed to version control (hence they are in .gitignore), but they need to be temporarily present in the project folder. Different sessions may require different subsets of these documents - sometimes one section of documentation is needed, other times a different section.
Requirements