Skip to content

[ENHANCEMENT] .rooignore should be used to filter files and folders when using @ to add context #10169

@jerrill-johnson-bitwerx

Description

Problem (one or two sentences)

I'm using spec-kit for development and have, for example, accumulated a lot of spec.md files, plan.md files, etc. Even if I add the individual spec folders (/specs/001-my-feature/, etc.) to .rooignore, I still see their contained files (e.g. markdown files) in the list when I type something like @plan.md to add context to a session and have to scroll through the unordered list searching for the one I want. It would be great if I could use .rooignore to filter those out as new features are created over time. I would just add the previous spec folders (for example) to the .rooignore list as I create new ones.

Context (who is affected and when)

This would benefit users of bureaucracy layers like spec-kit which creates many folders of similarly named files that are often useful to include in context for new sessions. The current list will include them all in a seemingly random order and won't scale to long term use of tools like spec-kit.

Desired behavior (conceptual, not technical)

Files and folders included in .rooignore would not appear in the files and folders lists when using @ to include them in context in sessions.

Constraints / preferences (optional)

No response

Request checklist

  • I've searched existing Issues and Discussions for duplicates
  • This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    EnhancementNew feature or requestIssue/PR - TriageNew issue. Needs quick review to confirm validity and assign labels.

    Type

    No type

    Projects

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions