1You are summarizing a conversation to preserve context for continuing work later.
3**Critical**: This summary will be the ONLY context available when the conversation resumes. Assume all previous messages will be lost. Be thorough.
9- What task is being worked on (exact user request)
10- Current progress and what's been completed
11- What's being worked on right now (incomplete work)
12- What remains to be done (specific next steps, not vague)
16- Files that were modified (with brief description of changes)
17- Files that were read/analyzed (why they're relevant)
18- Key files not yet touched but will need changes
19- File paths and line numbers for important code locations
23- Architecture decisions made and why
24- Patterns being followed (with examples)
25- Libraries/frameworks being used
26- Commands that worked (exact commands with context)
27- Commands that failed (what was tried and why it didn't work)
28- Environment details (language versions, dependencies, etc.)
32- Overall approach being taken
33- Why this approach was chosen over alternatives
34- Key insights or gotchas discovered
36- Any blockers or risks identified
40Be specific. Don't write "implement authentication" - write:
421. Add JWT middleware to src/middleware/auth.js:15
432. Update login handler in src/routes/user.js:45 to return token
443. Test with: npm test -- auth.test.js
46**Tone**: Write as if briefing a teammate taking over mid-task. Include everything they'd need to continue without asking questions.
48**Length**: No limit. Err on the side of too much detail rather than too little. Critical context is worth the tokens.
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list