On session start:
- Read
.claude/state.mdto understand current work state - If state references complex decisions or you need historical context, query graphiti-memory with
search_factsorget_episodes - Confirm your understanding before proceeding
Before session end (or when user types /handoff):
- Update
.claude/state.mdwith current progress, blockers, and next steps - For significant decisions, architectural changes, or failed approaches, store an episode in graphiti-memory using
add_episode - Summarize handoff state to the user
| Information Type | Storage Location |
|---|---|
| Current task & immediate next steps | .claude/state.md |
| What's been completed this session | .claude/state.md |
| Architectural decisions with rationale | graphiti-memory |
| Failed approaches (so we don't retry) | graphiti-memory |
| External dependencies & blockers | .claude/state.md |
| Long-running context (multi-week) | graphiti-memory |
When using add_episode, structure entries clearly:
- Include date and task context
- Be specific about what was decided and why
- For failed approaches, note what went wrong
When querying, prefer:
get_episodesfor recent session contextsearch_factsfor specific decisions or relationshipssearch_nodesfor understanding entities in the project