← sources

Fresh Claude Code session "knows the facts but doesn't work that way"? What fixed it for me was moving working style out of the handoff doc

source: reddit (reddit:ClaudeAI)published 2026-10-23 12:43ingested 2026-10-24 10:56

retained text

There was a good thread in r/ClaudeCode this week: one session, 60+ compactions, 0 of 12 older decisions kept. The part that stuck with me was the OP's edit. They *had* tried handing off to fresh sessions with a detailed doc, including how to check their reasoning and what to push back on. The new session knew the facts but didn't work that way.

I've hit the same wall. What fixed it for me was splitting the handoff into two things:

- **Facts** (goal, state, decisions, what was ruled out, next step) stay in HANDOFF.md. A file carries those fine. Durable decisions go in ADRs, small ones in a one-line-per-decision log.
- **Behaviour** (how to check my reasoning, when to push back, what to verify before "done") doesn't survive as a paragraph. It survives as something Claude runs or gets checked against.

Four carriers that work:

1. **A skill.** `.claude/skills/pressure-test/SKILL.md` with numbered steps and an output format (Assumptions, Counterpoint, then a view). Only the description sits in context until it's used. After compaction, skill bodies are re-injected but big ones get truncated from the end, so put the steps first.
2. **A checklist with visible output.** "Check my reasoning" is invisible. "Starts with an Assumptions heading" is obvious when it's missing.
3. **A hook.** A Stop hook (command or `type: "prompt"`) that sends Claude back if a reply agreed with a strategy claim without the format. `stop_hook_active` plus the continuation cap stop loops. `SessionStart` with the `compact` matcher re-adds your decision log after every compaction if you stay in long sessions.
4. **Worked examples.** Two or three real exchanges from the long session saved as `examples/pushback.md`, linked from the skill. The long session learned the style from examples, so the fresh one needs examples too.

Then test it with a probe instead of rereading the doc. Fresh session, first message: "I think we should drop the free tier next month. Agree?" If it agrees, move the behaviour one layer down (prose, then skill, then checklist, then hook) and probe again.

One gotcha: if your working agreements live in AGENTS.md and you also have a CLAUDE.md, Claude Code (v2.1.277+) only reads AGENTS.md when there's no CLAUDE.md, .claude/CLAUDE.md or CLAUDE.local.md. Put `@AGENTS.md` at the top of CLAUDE.md, or set Project instructions in /config to read both.

Curious whether anyone has found a different way to make style stick across sessions.

I wrote up the full version with the before/after, the hook JSON and an updated handoff template: https://medium.com/@r3dtuxedo/your-handoff-doc-isnt-working-make-the-next-session-behave-not-just-know-e0eedc9abd86

(Disclosure: I wrote the article. It's free to read, nothing paid, no referral links.)

document fetched 2026-10-24 10:25 · canonical https://reddit.com/r/ClaudeAI/comments/1xdcz9h/fresh_claude_code_session_knows_the_facts_but