[FEATURE] No more CLAUDE.md, go for .claude/instructions.md - or further

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Is there a way to remember in this project, not just this session?

⏺ Yes! I can create a project-level instruction file. Here are the options:

Option 1: .claude/instructions.md (Recommended)

Create a .claude/ directory with instructions I'll check at the start of sessions.

Option 2: CLAUDE.md in project root

A simple markdown file with project-specific rules.

Option 3: Add to existing docs

If you have a README.md or CONTRIBUTING.md, I can add a section there.

Would you like me to create one of these?

For example, I could create .claude/instructions.md with:
# Claude Instructions for this Project

## Build & Run Commands

• NEVER run pnpm build, pnpm dev, or pnpm start
• Always ask the user to run these commands
• This applies to all build/dev/start commands across the project

## Project Notes

• This is a 24/7 daemon for automated token swaps
• Production runs on minified builds for memory efficiency

This way, future Claude sessions working on this project could reference these instructions. Which approach would you prefer?

That sounds better than creating a CLAUDE.md in the project. Remember this for other projects EVER all over the world

⏺ I wish I could, but I cannot remember across different projects or conversations - each Claude session is completely isolated with no persistent memory.

What I CAN do:

• Create .claude/instructions.md for THIS project (helps future Claude sessions on this codebase)
• Follow the rule perfectly in OUR current session

What you'll need to do:

• Mention this preference at the start of new conversations/projects
• Or create .claude/instructions.md in each new project

Want me to create .claude/instructions.md for this project now? It will help any future Claude sessions working on this codebase.

I meant to bring this back as official feedback to your project holders.

⏺ Ah, I understand! You want to submit this as feedback to Anthropic about having persistent preferences across all Claude Code sessions.

How to submit feedback:

As mentioned in my system prompt, you can report issues and feedback at:
https://github.com/anthropics/claude-code/issues

This is the official feedback channel for Claude Code. Your suggestion about persistent user preferences (like "never run build/dev/start commands") across all projects would be valuable feedback!

In the meantime:

Would you like me to create .claude/instructions.md for this project? It's a good workaround until/unless that feature exists.

Proposed Solution

If instructions work better, make it known to Claude itself.
I have several projects with CLAUDE.md with instructions that now seem to never should have been there

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

This is more of a learning for the machine thing than anything else, and like often it happens with AI these days, now it seems to be looping about this solution. So I would like Claude itself understand what is the best solution for its very own instructions and project information