Skip to content

[FEATURE]: Dynamic AGENTS.md resolution has no low-cost trigger for intentional loading #13540

Closed as not planned

Description

@wblazer

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

The AGENTS.md autoloading (added in #10678) is only triggered by the read tool. This means the only way to trigger autoloading of a subdirectory's AGENTS.md is to read an actual file from that directory.

There's no low-cost way for an agent to load folder-level agent documentation without pulling in potentially unwanted file content. Tools like glob and grep that operate on directories don't trigger autoloading, and explicitly reading the AGENTS.md itself doesn't prevent re-injection on subsequent reads (since explicit reads don't populate metadata.loaded the same way).

The root problem for me is that I want a system where an agent can explore the codebase through its localized agent documentation before reading any code, but also have any unloaded documentation loaded passively as a side effect of the read tool (current approach).

A potential solution is to deduplicate explicit AGENTS.md reads against subsequent autoloads.

This functionality can be recreated with plugins, and I had Claude recreate it as a plugin with deduplication of explicit reads here. The main constraint of this approach is that the built-in dynamic AGENTS.md resolution can't be disabled currently, so I'm forced to use a different filename. However, I think I like my output format better for my needs because auto-loaded localized documentation feels semantically different than a "system-reminder," so I may continue using it even if my suggestion here goes through. An option to disable the built-in auto-loading would let me use AGENTS.md as the filenames still with my plugin, so that might be a nice addition as well.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Feb 13, 2026
  2. github-actions commented on Feb 13, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • Feature Request titles should start with [FEATURE]: prefix. Current title: "Dynamic AGENTS.md resolution has no low-cost trigger for intentional loading" should be "[FEATURE]: Dynamic AGENTS.md resolution has no low-cost trigger for intentional loading"

    Please edit this issue to address the above within 2 hours, or it will be automatically closed.

    If you believe this was flagged incorrectly, please let a maintainer know.

  3. changed the title [-]Dynamic AGENTS.md resolution has no low-cost trigger for intentional loading[/-] [+][FEATURE]: Dynamic AGENTS.md resolution has no low-cost trigger for intentional loading[/+] on Feb 13, 2026
  4. github-actions commented on Feb 14, 2026

    @github-actions
    Contributor

    This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

    Feel free to open a new issue that follows our issue templates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

discussionUsed for feature requests, proposals, ideas, etc. Open discussionneeds:complianceThis means the issue will auto-close after 2 hours.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions