[DOCS] Terminology mismatch between Changelog and Memory docs regarding `@include` vs `@path`
Documentation Type
Unclear/confusing documentation
Documentation Location
https://code.claude.com/docs/en/memory#claudemd-imports
Section/Topic
The "CLAUDE.md imports" section within the Memory documentation.
Current Documentation
"CLAUDE.md files can import additional files using @path/to/import syntax."
What's Wrong or Missing?
There is a discrepancy in terminology between the official documentation and the release changelog. The changelog for version 2.1.2 refers to this feature as the "@include directive" (specifically: "Fixed binary files... being accidentally included in memory when using @include directives in CLAUDE.md files").
However, the documentation page at https://code.claude.com/docs/en/memory never uses the word "include" or the string "@include". This leaves it unclear to the user whether @include is a required keyword/directive, or if the @ symbol itself is what the changelog is referring to as the "include directive."
Suggested Improvement
The documentation should be updated to use consistent terminology. If the @ prefix is technically considered the "include directive," the documentation at https://code.claude.com/docs/en/memory#claudemd-imports should explicitly state:
"CLAUDE.md files can import additional files using the@include directive (e.g.,@path/to/import)."
If @include is a literal string that can be used (e.g., @include path/to/file), that should also be documented.
Impact
High - Prevents users from using a feature
Additional Context
- Related Changelog Entry (v2.1.2): "Fixed binary files (images, PDFs, etc.) being accidentally included in memory when using @include directives in CLAUDE.md files"
- Current Documentation (Memory): https://code.claude.com/docs/en/memory
- Example of Clarity: Many pre-processors ( like C or SASS) clearly define their
@-rules or directives by name to avoid confusion with general pointers or paths. Explicitly naming the@symbol as the "include directive" would align the docs with the developer terminology used in the changelog.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗