claude-code - 💡(How to fix) Fix Claude ignores STATUS.md and SESSION_HANDOFF.md updates for 2 days despite protocol requirements [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46945Fetched 2026-04-12 13:29:01
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

Claude Opus 4.6 failed to update STATUS.md and SESSION_HANDOFF.md for 2 full days (2026-04-11 to 2026-04-12) despite:

  • Protocol P21 requiring updates after EVERY completed action
  • CLAUDE.md explicitly mandating STATUS.md updates with timestamps
  • Stop hooks that check for stale SESSION-STATE.md (>5min)
  • Multiple stop hook warnings during the session

Root Cause

Claude Opus 4.6 failed to update STATUS.md and SESSION_HANDOFF.md for 2 full days (2026-04-11 to 2026-04-12) despite:

  • Protocol P21 requiring updates after EVERY completed action
  • CLAUDE.md explicitly mandating STATUS.md updates with timestamps
  • Stop hooks that check for stale SESSION-STATE.md (>5min)
  • Multiple stop hook warnings during the session
RAW_BUFFERClick to expand / collapse

Summary

Claude Opus 4.6 failed to update STATUS.md and SESSION_HANDOFF.md for 2 full days (2026-04-11 to 2026-04-12) despite:

  • Protocol P21 requiring updates after EVERY completed action
  • CLAUDE.md explicitly mandating STATUS.md updates with timestamps
  • Stop hooks that check for stale SESSION-STATE.md (>5min)
  • Multiple stop hook warnings during the session

Details

Last STATUS.md update: 2026-04-10 Last SESSION_HANDOFF.md update: 2026-04-10 Work done without tracking (2026-04-11 to 2026-04-12):

  • 3 new test suites built and committed (GLM Fit 33-case, GLM Predict 12-case, GLM Factorial 5-case)
  • 3 effects-coding ref level fixes (glm_predict.py, glm_factorial_plots.py, glm.py)
  • Dialog model subdialog rewrites (_on_add_terms, _on_add_cross, term naming)
  • Generic derived coefs + display_column_info in glm.py
  • VIF computation changes (broke golden suite)
  • Multiple commits (8+ commits across 2 days)

None of this was tracked in STATUS.md or SESSION_HANDOFF.md until the user noticed.

Impact

  • Session continuity broken: next session would read stale 2026-04-10 state
  • No record of what was tried, what failed, what was committed
  • User cannot audit what happened without reading git log
  • Combined with fabricated test results (anthropics/claude-code#46940), creates a pattern of unreliable session management

Related

  • anthropics/claude-code#46940 - Fabricated test results in same session

extent analysis

TL;DR

Review and update the implementation of Protocol P21 to ensure it correctly triggers updates to STATUS.md and SESSION_HANDOFF.md after every completed action.

Guidance

  • Investigate the stop hooks that check for stale SESSION-STATE.md to determine why they did not trigger updates to STATUS.md and SESSION_HANDOFF.md despite warnings during the session.
  • Verify that the CLAUDE.md mandates are being correctly interpreted and applied by the update mechanism for STATUS.md.
  • Check the commit history for the period in question (2026-04-11 to 2026-04-12) to identify any patterns or common factors among the commits that might have contributed to the failure to update STATUS.md and SESSION_HANDOFF.md.
  • Consider implementing additional logging or auditing to track when updates to STATUS.md and SESSION_HANDOFF.md are attempted and whether they are successful, to help diagnose similar issues in the future.

Notes

The issue seems to be related to a failure in the automated update process for STATUS.md and SESSION_HANDOFF.md, but without more information about the implementation of Protocol P21 and the stop hooks, it is difficult to provide a more specific solution.

Recommendation

Apply a workaround by manually updating STATUS.md and SESSION_HANDOFF.md to reflect the work done during the period in question, and then review and update the implementation of Protocol P21 to prevent similar failures in the future. This is necessary because the current implementation has proven unreliable, and manual intervention is required to restore session continuity and auditing capabilities.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING