Session Skill (Unified)

Consolidates all session-related functionality into one skill.

Usage

/session              # Show available options
/session list         # Show active sessions
/session inbox        # Check incoming messages
/session broadcast "message"  # Send message to all sessions

Subcommands

/session list - List Active Sessions

Shows all active Claude Code sessions in the current project.

📋 Active Sessions

| Session ID | Status | Last Activity |
|------------|--------|---------------|
| abc123     | active | 2 min ago     |
| def456     | idle   | 15 min ago    |

/session inbox - Check Inbox

Checks for incoming messages from other sessions.

📬 Session Inbox

| From | Time | Message |
|------|------|---------|
| abc123 | 5m ago | "Ready for review" |
| def456 | 10m ago | "API implementation done" |

/session broadcast "message" - Broadcast Message

Sends a message to all active sessions.

/session broadcast "Review complete, ready for merge"

Capabilities

Memory Optimization (CC 2.1.49+)

From Claude Code 2.1.49 onward, memory usage when resuming sessions has been reduced by 68%.

Best Practices for Long Session Management

Automatic Session Naming (CC 2.1.41+)

Running /rename without arguments automatically generates a session name from the conversation context. Makes session identification easier in workflows that involve long sessions or frequent --resume.

Efficient Workflow Example

# Implementation phase 1
claude "Implement authentication"
# → 1 hour later

# Resume session (memory-efficient)
claude --resume "Add password reset feature"
# → 1 hour later

# Resume again
claude --resume "Add tests"

Memory Management Recommendations

Memory efficiency has greatly improved — actively leverage session resumption.

Codex 0.123.0 session shell / terminal Fix

In Codex 0.123.0, stale proxy env is less likely to be restored from the shell snapshot, and Unicode / dead-key input in VS Code WSL terminal and keyboard input have been fixed in the main binary. The harness does not add a proxy snapshot scrubber or key input wrapper — it inherits the main binary fixes automatically.

When to Use

• Session initialization (/harness-init)
• Session resume/fork (/work --resume, /work --fork)
• Memory persistence (automatic)
• Cross-session communication (/session broadcast)

Execution Flow

1. Session Initialization

/harness-init
    ↓
├── Load project context
├── Initialize session.json
├── Load previous session memory (if exists)
└── Display session status

2. Session Control (from /work)

/work --resume
    ↓
├── Check session.json exists
├── Load session state
└── Continue from last checkpoint

/work --fork
    ↓
├── Create new session branch
├── Copy relevant context
└── Start fresh with context

3. Memory Persistence

Session end
    ↓
├── Extract learnings (gotchas, patterns)
├── Update .claude/memory/*.md
└── Prepare handoff summary

4. Cross-Session Communication

/session broadcast "message"
    ↓
├── Find active sessions
├── Write to session.events.jsonl
└── Notify all sessions

Files Managed

Migration Note

This skill consolidates:

• session-init → Session initialization
• session-memory → Memory persistence
• session-control → Resume/fork control
• session-state → State management & communication

The individual skills are deprecated but still work for backward compatibility.