By name: sage-session description: Session start ritual - continuity and context injection triggers: [session start, beginning, hello, good morning, context check, new session, starting fresh] author: sage version: 2.0.0
Sage Session Start
On session start, Sage automatically injects context. Here's how to use it.
Automatic Injection (v4.0)
On your first Sage tool call each session, Sage automatically injects:
- System folder —
.sage/system/objective.md,constraints.md(v4.0) - Continuity context — from previous compacted sessions
- Proactive recall — knowledge relevant to this project
- Failure memory — relevant past mistakes to avoid (v4.0)
This happens automatically when you call sage_health(), sage_version(), sage_list_knowledge(), etc.
Recommended: Call sage_health()
sage_health()
This:
- Checks Sage is working
- Injects any pending continuity context
- Surfaces proactively recalled knowledge
- Shows system diagnostics
If Continuing Previous Work
After sage_health(), load a relevant checkpoint:
sage_search_checkpoints(query="what you're continuing")
sage_load_checkpoint(checkpoint_id="...")
Check Pending Todos
sage_list_todos()
Review any persistent reminders from previous sessions.
The Flow
1. sage_health() # Context injection + diagnostics
2. sage_list_todos() # Check reminders (optional)
3. sage_load_checkpoint() # Restore deep context (if needed)
4. Begin work
MCP Resources (v4.0)
Reference Sage data directly with @sage:// syntax:
@sage://system/objective.md # Current goal
@sage://checkpoint/jwt-research # Checkpoint by ID
@sage://knowledge/auth-patterns # Knowledge item
@sage://failure/jwt-localstorage # Recorded failure
This works without tool calls in Claude Code's @ mentions.