# Give new Claude Code sessions your project facts

> Keep a short CLAUDE.md for recurring project facts, then check which instructions loaded.

Source: https://fullbytedeveloper.com/blog/claude-code-session-memory-template
Keyword: MEMORY
Published: 2026-11-05

A new Claude Code session starts with a fresh context window. The memory docs say project instruction files and auto memory carry information into it [1]. A short `CLAUDE.md` gives you a place to keep facts you keep repeating.

## Write the facts the next session needs

Adapt the example from our MEMORY post to your project. Replace every line that is untrue before saving it in the project root.

```md title="CLAUDE.md"
# Project context

- Stack: Next.js + Postgres
- Auth is done
- Do not redo auth
```

The docs describe `CLAUDE.md` as context the model tries to follow. It does not enforce access restrictions [1]. Use [permission rules to protect secrets](/blog/claude-code-env-lock).

## Check the file in Claude Code

Run the documented command inside a session [1].

```text
/memory
```

You should see the instruction file locations. Select the project file to read or edit it.

## Keep the instructions current

Remove completed-work notes once they stop helping future sessions. Put recurring decisions in concrete sentences. If a rule is ignored, the docs recommend checking for conflicting instructions and confirming that the file loaded [1].

For procedures that deserve their own skill or hook, see [where each Claude Code instruction belongs](/blog/claude-md-where-instructions-belong).

## Sources

1. [Claude Code docs: memory](https://code.claude.com/docs/en/memory)

## Original posts

- [Instagram reel](https://www.instagram.com/reel/De9yS9XlKgH/)
- [TikTok video](https://www.tiktok.com/@fullbytedeveloper/video/7701022991236287762)
- [YouTube Short](https://www.youtube.com/shorts/mpwXCn45VeA)
- [Facebook reel](https://www.facebook.com/reel/1154525877136568)
- [Threads post](https://www.threads.com/@fullbytedeveloper/post/De9xQ1yDlX2)