Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CLAUDE.md with a heading line plus @AGENTS.md is not recognized as a pointer

Open Beginner friendly
#116 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, node.js

Research direction

Start by locating the pointer-detection logic and its existing tests; the issue does not name specific files. Check how it handles a CLAUDE.md containing only @AGENTS.md, then test the same pointer with leading headings and blank lines. Done means those heading-prefixed files are recognized as pointers, while other content remains a separate memory file.

Written by the indexing model from the issue text.

Description

ready-for-pr

Summary

A CLAUDE.md whose content is a heading line plus the import, for example:

# my-repo

@AGENTS.md

is treated as a separate memory file:

warn CLAUDE.md is a separate memory file and will NOT be updated - only AGENTS.md is optimized. To cover both, consolidate: move its content into AGENTS.md and make CLAUDE.md a pointer (a single line: @AGENTS.md).

Claude Code resolves the @AGENTS.md import identically with or without the heading, and a heading is the common convention (Claude Code's own /init and many fleets emit a title line). The pointer check could ignore leading markdown headings and blank lines before deciding the file is not a pointer.

Environment

backpass 0.1.18, Windows 11, Node 22.14.

Suggested fix

In the pointer detection, strip lines matching ^# and blank lines, then compare the remainder to @AGENTS.md.

Dominant language
JavaScript
Stars
1.4k
Forks
114
Avg merge
14h 43m
Merged PRs (30d)
37

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kunchenguid/backpass

All issues in kunchenguid/backpass

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.