feat: Add directory selection to @ file search

[muqsitnawaz]

What

Adds directory support to the @ file search popup in TUI. Directories appear with a trailing / suffix and can be selected like files.

Why

Closes Issue #8863

Referencing entire directories (modules, packages, libraries) is faster than selecting files one by one. The model can then list_dir or read as needed.

How

• file-search/src/lib.rs: Add / suffix to directory entries
• protocol/src/user_input.rs: Add LocalDirectory variant
• protocol/src/models.rs: Convert directory to tree listing on submit
• tui2/src/bottom_pane/chat_composer.rs: Detect and attach directories
• tui2/src/chatwidget.rs: Include directories in UserMessage

Includes 3 unit tests for tree formatting, truncation, and error handling.

Examples

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[muqsitnawaz]

I have read the CLA Document and I hereby sign the CLA

[etraut-openai]

Thanks for the contribution, but our contribution guidelines indicate that we're not generally accepting new features at this time. We need to make sure that all new features compose well with both existing and upcoming features, fit into our roadmap, and are consistent across all Codex surfaces (CLI, IDE extension, web). This feature, in particular, should work the same in the CLI and the IDE extension.

If you would like to propose a new feature, please file or upvote an enhancement request in the issue tracker. We will generally prioritize new features based on community feedback.

[muqsitnawaz]

What's the roadmap? Please share.

I am using Codex every day and I would like it to be better and less buggy.

I'm happy to fix issues across CLI and Ext

[etraut-openai]

@muqsitnawaz, thanks for the offer. As I mentioned above, we generally prioritize enhancements based on community feedback (upvotes). You can get a sense for our roadmap by looking at the enhancement requests in the issue tracker and sorting by reaction counts.

I appreciate your willingness to help with new features, but the bottleneck is not in generating the code. That's the easy part — thanks to Codex. The bottleneck is in designing features that work across all Codex surfaces in a consistent manner, making sure they're implemented in a sound and maintainable way, ensuring that they compose well with other existing and upcoming features, making sure they're polished from a visual/interactive standpoint, documenting them, etc. It typically takes more time for a Codex team member to work with a community member on a new feature than it does for us to implement it ourselves, which is why we've decided not to accept feature PRs. We want to make sure that we're investing our time on the most impactful features and bug fixes.

Thanks for opening the feature request #8863. It has collected five upvotes in the last few days, which means other users are also interested in it. However, there are many features that are more popular — and therefore higher priority for us.

We are accepting PRs for bug fixes if you'd like to contribute in that way.

We're also hiring, so if you or someone you know might be interested in joining the Codex team, you're welcome to apply.