state-md-pattern-for-cross-session-continuity
A STATE.md file at the repo root serves as the living cross-session bridge for long-running projects. Protocol for every session: git pull → read STATE.md (current phase, next action, blockers) → scan recent git log → do work → update STATE.md → commit with structured trailers → git push. A fresh Claude instance with zero prior context can pick up coherently from STATE.md alone.
Related
- r-same-cross-session-continuity-protocol
- docker
- r-same-github-repo-created-cross-session-sync-protocol
- r-same-project-location-state-and-wave-status
- openclaw
- cross-session-continuity-via-state-md-git-pull-pattern
- r-same-cross-session-continuity-via-state-md
- r-same-state-md-cross-session-continuity-protocol
- state-md-cross-session-continuity-protocol
- cross-session-continuity-protocol-via-state-md-and-git-log
- r-dash-wave3-commit-fc844de-local-push-blocked