{ "@context": "https://schema.org", "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2025-09-23-globs-in-agents-md/#webpage", "@type": [ "WebPage", "ArchiveComponent" ], "articleBody": "Your [`AGENTS.md` files](https://ampcode.com/manual#AGENTS.md) can now include other context files dynamically, with glob mentions and filters, so you can give more granular guidance to the agent.\n\nFor example, to apply language-specific coding rules:\n\n1. Put `See @docs/*.md` anywhere in your `AGENTS.md` file.\n\n2. Create a file `docs/typescript-conventions.md` with:\n\n ```markdown\n ---\n globs:\n - '**/*.ts'\n ---\n\n Follow these TypeScript conventions:\n\n - Never use the `any` type\n - ...\n ```\n\n3. Repeat for other languages.\n\nThere's nothing special about `@docs/*.md`; you could instead mention `@.agent/rules/*.md` or `@.cursor/rules/*.mdc` or anywhere else you want these rules to live.\n\nThese @-mentioned files with `globs` will only be included if Amp has read a file matching any of the globs (in the example above, any TypeScript file). Use `/agent-files` (CLI) or hover over `X% of 968k` (editor extension) to see the guidance files in use.\n", "authors": [], "captured_at": "2026-10-04T12:50:30.804479567+00:00", "category": "programming", "content_html": "

Your AGENTS.md files can now include other context files dynamically, with glob mentions and filters, so you can give more granular guidance to the agent.

\n

For example, to apply language-specific coding rules:

\n
    \n
  1. \n

    Put See @docs/*.md anywhere in your AGENTS.md file.

    \n
    2. \n
  2. \n

    Create a file docs/typescript-conventions.md with:

    \n
    ---\nglobs:\n  - '**/*.ts'\n---\n\nFollow these TypeScript conventions:\n\n- Never use the `any` type\n- ...\n
    \n
    3. \n
  3. \n

    Repeat for other languages.

    \n
    4. \n
\n

There's nothing special about @docs/*.md; you could instead mention @.agent/rules/*.md or @.cursor/rules/*.mdc or anywhere else you want these rules to live.

\n

These @-mentioned files with globs will only be included if Amp has read a file matching any of the globs (in the example above, any TypeScript file). Use /agent-files (CLI) or hover over X% of 968k (editor extension) to see the guidance files in use.

\n", "content_markdown": "Your [`AGENTS.md` files](https://ampcode.com/manual#AGENTS.md) can now include other context files dynamically, with glob mentions and filters, so you can give more granular guidance to the agent.\n\nFor example, to apply language-specific coding rules:\n\n1. Put `See @docs/*.md` anywhere in your `AGENTS.md` file.\n\n2. Create a file `docs/typescript-conventions.md` with:\n\n ```markdown\n ---\n globs:\n - '**/*.ts'\n ---\n\n Follow these TypeScript conventions:\n\n - Never use the `any` type\n - ...\n ```\n\n3. Repeat for other languages.\n\nThere's nothing special about `@docs/*.md`; you could instead mention `@.agent/rules/*.md` or `@.cursor/rules/*.mdc` or anywhere else you want these rules to live.\n\nThese @-mentioned files with `globs` will only be included if Amp has read a file matching any of the globs (in the example above, any TypeScript file). Use `/agent-files` (CLI) or hover over `X% of 968k` (editor extension) to see the guidance files in use.\n", "dateCreated": "2026-10-04T12:50:30.804479567+00:00", "date_created": "2025-09-23T00:00:00+00:00", "date_modified": "2025-09-23T00:00:00+00:00", "date_published": "2025-09-23T00:00:00+00:00", "description": "Your AGENTS.md files can now include other context files dynamically, with glob mentions and filters, so you can give more granular guidance to the agent. For example, to apply language-specific coding rules: Put See @docs/.md anywhere in…", "external_url": "https://ampcode.com/news/globs-in-AGENTS.md", "git": { "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e", "path": "items/ampcode-com/2025/09/2025-09-23-globs-in-agents-md.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/ampcode-com/2025/09/2025-09-23-globs-in-agents-md.md" }, "id": "urn:aggr:item:1572f8241a73249f8c85245c09b758a2974dd771", "isBasedOn": { "@id": "https://ampcode.com/news/globs-in-AGENTS.md" }, "mainEntity": { "@id": "https://ampcode.com/news/globs-in-AGENTS.md", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2025-09-23-globs-in-agents-md/#webpage" }, "dateModified": "2025-09-23T00:00:00+00:00", "datePublished": "2025-09-23T00:00:00+00:00", "headline": "Globs in AGENTS.md", "timeRequired": "PT1M", "url": "https://ampcode.com/news/globs-in-AGENTS.md", "wordCount": 136 }, "name": "Archived snapshot: Globs in AGENTS.md", "preview": null, "reading_minutes": 1, "replicated_at": null, "source": "ampcode-com", "source_name": "Amp News", "summary": "Your AGENTS.md files can now include other context files dynamically, with glob mentions and filters, so you can give more granular guidance to the agent. For example, to apply language-specific coding rules: Put See @docs/*.md anywhere in your AGENTS.md file. Create a file docs/typescript-conventions.md with: --- globs: - '**/*.ts' --- Follow these TypeScript conventions: - Never use the `any` type - ... Repeat for other languages. There's nothing special about @docs/*.md; you could instead mention @.agent/rules/*.md or @.cursor/rules/*.mdc or anywhere else you want these rules to live. These @-mentioned files with globs will only be included if Amp has read a file matching any of the globs (in the example above, any TypeScript file). Use /agent-files (CLI) or hover over X% of 968k (editor extension) to see the guidance files in use.", "tags": [], "temporalCoverage": "2026-10-04T12:50:30.804479567+00:00", "title": "Globs in AGENTS.md", "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2025-09-23-globs-in-agents-md/", "word_count": 136 }