session-context

Session Context

Load relevant past session context for the current task, file, or project. Uses CASS to find sessions related to what is being worked on right now, providing historical awareness across all coding agents.

Core Workflow

1. Find the Current Session

Identify the active session for this workspace:

cass sessions --current --json

2. List Recent Sessions

Browse recent sessions for a project:

# Sessions for current workspace
cass sessions --workspace "$(pwd)" --json --limit 10

# All recent sessions
cass sessions --json --limit 15

3. Find Related Sessions by File

When working on a specific file, find sessions that previously touched it:

cass context <path-to-session-file> --json --limit 10

This returns sessions that referenced the same file, including modifications, discussions, and debugging sessions.

4. Find Related Sessions by Topic

Combine workspace filtering with topical search:

# Hybrid search within current project
cass search "<current task description>" --workspace "$(pwd)" --mode hybrid --json --limit 10

# Search with time scope
cass search "<topic>" --workspace "$(pwd)" --days 30 --json --limit 10

# Search across all sources (multi-machine)
cass search "<topic>" --source all --json --limit 10

5. Timeline View

See what happened in a project over time:

# Today's sessions
cass timeline --today --json

# Last 7 days by day
cass timeline --since 7d --json --group-by day

# Last 30 days overview
cass timeline --since 30d --json --group-by day

# Specific agent activity
cass timeline --since 7d --agent claude_code --json

6. Quick Overview via Aggregation

Get a fast summary without loading full results:

# Activity by agent in last 7 days
cass search "*" --json --aggregate agent --week

# Activity by workspace
cass search "*" --json --aggregate workspace --days 30

7. Expand Key Sessions

For sessions that look relevant, pull full message context:

cass expand <source_path> --line <line_number> -C 5 --json

8. Store Context to Memory

After loading relevant context, invoke the mcp__memory__remember MCP tool to store key findings:

• title: Context summary for <file/project>
• content: Key decisions, patterns, or history discovered
• tags: ["cass", "session-context", <project-name>]
• category: "context"

Before storing, recall existing memories on the topic to avoid duplicates.

Use Cases

Starting Work on a File

Before modifying a file, check what past sessions involved it:

# Find the current session
cass sessions --current --json

# Search for related work
cass search "login refactor" --workspace "$(pwd)" --json

Resuming After a Break

Catch up on recent activity in the project:

# What happened recently?
cass timeline --since 3d --json --group-by day

# Quick agent breakdown
cass search "*" --json --aggregate agent --days 3

# Drill into specific sessions
cass expand <path> --line <line> -C 10 --json

Understanding a Decision

Find when and why a decision was made:

cass search "decided to use <technology>" --workspace "$(pwd)" --mode hybrid --json

Multi-Machine Context

Pull context from remote sources:

# Search across all machines
cass search "deployment script" --source all --json

# Search specific remote
cass search "config" --source work-laptop --json

Best Practices

• Use cass sessions --current as a starting point for current workspace context.
• Combine timeline views with targeted searches for comprehensive context.
• Use --aggregate for quick overviews before drilling into specifics.
• Use time filters (--days, --since) to scope context to relevant periods.
• Store discovered context to memory to avoid re-searching in future sessions.
• When context spans multiple sessions, synthesize findings before presenting.

Additional Resources

• Command Reference - Complete CASS CLI v0.2.7 reference