claude-code - 💡(How to fix) Fix Feature Request: Native support for AGENTS.md and .agents/skills/ as portable alternatives to CLAUDE.md and .claude/skills/ [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#50778Fetched 2026-04-20 12:13:17
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1

Claude Code is the only major agent CLI that doesn't recognize the emerging community standard of AGENTS.md + .agents/skills/. Cursor, Aider, Continue.dev, Codex, and others converge on this layout for portability. Supporting it natively would let a single repo work across every agent tool without maintaining parallel instruction files.

Root Cause

Claude Code is the only major agent CLI that doesn't recognize the emerging community standard of AGENTS.md + .agents/skills/. Cursor, Aider, Continue.dev, Codex, and others converge on this layout for portability. Supporting it natively would let a single repo work across every agent tool without maintaining parallel instruction files.

Fix Action

Fix / Workaround

  1. .agents/skills/ dual-discovery: alongside ~/.claude/skills/ and ./.claude/skills/, also scan ~/.agents/skills/ and ./.agents/skills/ for SKILL.md files. Merge into the skill registry. On name collision, prefer .claude/ (Claude-specific takes precedence).
RAW_BUFFERClick to expand / collapse

Summary

Claude Code is the only major agent CLI that doesn't recognize the emerging community standard of AGENTS.md + .agents/skills/. Cursor, Aider, Continue.dev, Codex, and others converge on this layout for portability. Supporting it natively would let a single repo work across every agent tool without maintaining parallel instruction files.

Proposal

  1. AGENTS.md dual-read: when Claude Code loads project instructions, check for AGENTS.md in the same directories it currently checks CLAUDE.md. If both exist, concatenate AGENTS.md content first, then CLAUDE.md content (explicit per-project override). If only one exists, use it.

  2. .agents/skills/ dual-discovery: alongside ~/.claude/skills/ and ./.claude/skills/, also scan ~/.agents/skills/ and ./.agents/skills/ for SKILL.md files. Merge into the skill registry. On name collision, prefer .claude/ (Claude-specific takes precedence).

  3. .agents/hooks/, .agents/commands/: optional follow-on for hook and slash-command portability. Lower priority than steps 1 and 2.

  4. Zero breaking changes: projects with only CLAUDE.md see no behavior change. Projects with AGENTS.md only get it honored automatically. Projects with both get deterministic precedence rules.

Prior-art evidence of demand (all 5 currently open, unanswered)

  • #6235 (3,639 thumbs-up): "Feature Request: Support AGENTS.md"
  • #31005 (117 thumbs-up): "Support for AGENTS.md and .agents/skills/, the community has been asking since April"
  • #12925 (96 thumbs-up): "Linear Integration: Assign issues to Claude Code to trigger cloud agent sessions" (adjacent; portability matters)
  • #10238 (133 thumbs-up): "Add support for subdirectories in skills" (skill-discovery adjacency)
  • #25045 (58 thumbs-up): "allow skills to programmatically rename sessions" (portability adjacent)

Why this is not a duplicate

  • #6235 is the original request but has no formal proposal. Anthropic has not responded in the issue thread.
  • #31005 asks for both AGENTS.md and .agents/skills/ but is a follow-up ask, not a consolidated design.
  • No existing issue proposes the specific dual-read + dual-discovery + precedence model above.
  • This FR consolidates the five related asks into one actionable spec that Anthropic can implement or explicitly decline with rationale.

Use case (specific, not hypothetical)

A user maintains a multi-agent workflow: Claude Code for implementation, Cursor for pair-programming refactors, Aider for batch refactors, Codex for one-shot script generation. Every project currently needs:

  • CLAUDE.md (Claude Code)
  • AGENTS.md (Cursor / Aider / Codex)

These files contain 80%+ overlapping content. When the user updates one, they must remember to mirror to the other. This is a known friction point across the community, and the 3,987 thumbs-up on #6235 alone is evidence that the scale is not niche.

Adding AGENTS.md dual-read in Claude Code would eliminate the duplication for projects that opt in, while preserving full backward compatibility for projects that use only CLAUDE.md.

Acceptance criteria

  • AGENTS.md in a project root is read alongside CLAUDE.md with documented precedence
  • .agents/skills/ is discovered alongside .claude/skills/ with documented precedence
  • Docs page at code.claude.com/docs/en/memory updated to cover both paths
  • A simple example repo demonstrates running the same skill on Claude Code AND Cursor without duplication
  • Closing notes on #6235 and #31005 reference this FR

extent analysis

TL;DR

Implementing AGENTS.md dual-read and .agents/skills/ dual-discovery in Claude Code will allow for better portability and reduce duplication across agent tools.

Guidance

  • Review the proposed dual-read and dual-discovery approach to ensure it aligns with the existing architecture and requirements of Claude Code.
  • Consider the precedence rules for handling both AGENTS.md and CLAUDE.md files, as well as .agents/skills/ and .claude/skills/ directories.
  • Evaluate the potential impact on existing projects and users, ensuring that the changes do not introduce breaking changes or compatibility issues.
  • Develop a plan for updating documentation and providing examples to demonstrate the new functionality.

Example

No code snippet is provided as the issue focuses on proposing a design and functionality change rather than a specific code implementation.

Notes

The proposal aims to address a known friction point in the community and has gathered significant support. However, it is crucial to carefully consider the implementation details and potential implications to ensure a seamless integration.

Recommendation

Apply the proposed workaround by implementing AGENTS.md dual-read and .agents/skills/ dual-discovery in Claude Code, as it addresses a widely recognized need for portability and reduces duplication across agent tools.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING