Session Notes
Track progress collaboratively
Session Notes
Track blockers, progress, and context across sessions.
What Are Session Notes?
Session notes are a workspace for tracking your current work. Ask your AI to:
- •Note what you're working on
- •Track blockers you hit
- •Record what worked (or didn't)
- •Save context for next time
Unlike decisions (which are permanent), session notes are for current work that might change.
How to Use Them
Set session goals
You: "Note that today I'm working on fixing the login bug and adding rate limiting."
AI: "Added to session goals: Fix login bug, add rate limiting."
Track blockers
You: "I'm stuck. The OAuth callback keeps returning 401. Add this to blockers."
AI: "Added blocker: OAuth callback returning 401."
Record what you tried
You: "I tried changing the redirect URI but that didn't help. Note that in the attempted approaches."
AI: "Noted: Changed redirect URI — didn't resolve 401 issue."
Save progress
You: "Found it! The redirect URI was wrong in the production config. Note that as the fix."
AI: "Noted: Fix found — redirect URI incorrect in production config."
Get a summary
You: "Summarize what we did today."
AI: "Session summary:
- •Goal: Fix login bug
- •Blocker: OAuth 401 errors
- •Tried: Changing redirect URI (didn't help)
- •Fix: Production config had wrong redirect URI"
Session Notes Sections
Ask your AI to add notes to specific sections:
| Section | What to track |
|---|---|
| Goals | What you're trying to accomplish |
| Blockers | Problems you're stuck on |
| Approaches | What you tried (worked or not) |
| Decisions | Quick notes (promote to real decisions if important) |
| Next steps | What to do next |
| Questions | Open items to figure out |
Example phrases
- •"Add to session goals: Implement caching"
- •"Note this blocker: Tests failing intermittently"
- •"Log that we tried X but it didn't work"
- •"Add to next steps: Review PR tomorrow"
Session Notes vs Decisions
They serve different purposes:
| Session Notes | Decisions |
|---|---|
| Temporary, for current work | Permanent, for future reference |
| Quick notes and progress | Documented reasoning |
| "I'm stuck on X" | "We chose X because Y" |
When to promote to a decision
If something becomes a lasting choice:
You: "The Redis approach worked well. Let's make that a real decision so we remember why."
AI: "I'll log decision-23: Redis for caching — fast TTL support, needed for session storage."
Starting a New Day
Begin sessions by checking notes:
You: "What were we working on? Check the session notes."
AI: "From your last session:
- •Goal: Rate limiting
- •Blocker: None open
- •Next steps: Implement middleware, test with Redis"
Workflow Example
Morning
You: "Check session notes and tell me where we left off."
AI: "Last session you were debugging auth issues. Blocker was OAuth 401 errors."
During work
You: "I fixed the auth issue. Remove that blocker and note the fix."
AI: "Removed blocker. Noted: Auth fixed by correcting production redirect URI."
End of day
You: "I'm stopping for today. Save where we are and what's next."
AI: "Session notes updated:
- •Completed: Auth fix
- •Next: Start rate limiting implementation
- •Question: Should we use Redis or in-memory for rate limits?"
Key Phrases
| What you want | What to say |
|---|---|
| Add a goal | "Add to goals: X" |
| Add a blocker | "I'm stuck on X" or "Add blocker: X" |
| Remove a blocker | "Fixed it" or "Remove blocker" |
| Note an approach | "I tried X" or "Note that X didn't work" |
| Get summary | "Summarize the session" |
| Check notes | "What's in the session notes?" |
Key Takeaways
- •Ask explicitly — Tell your AI what to add to notes
- •Use sections — Goals, blockers, approaches, next steps
- •Check at session start — "What were we working on?"
- •Save at session end — "Save where we are"
- •Promote important items — Turn lasting choices into decisions