session-bridge

To preserve session context across sessions, you need a mechanism that reads a canonical file at session start and writes updates at session end. This Skill maintains a continuous work narrative by managing a SESSION.md file, restoring in-progress tasks, next steps, and blockers automatically.

Session management prevents context drift by applying hard caps to the archived data, limiting files to 300 lines with a 72-hour TTL. Older sessions are archived to a predictable path, ensuring cross-project continuity without accumulating stale or oversized context.

Yes, you can safely archive session workflows because the system scans for secrets before writing any updates to the context file. This security check ensures sensitive information is detected and prevented from entering the archived session history.

The best way to promote session context is using a 2-of-3 policy workflow that identifies candidates for a permanent configuration file. It marks suitable session entries for promotion without auto-promoting, requiring manual review before integration.

Yes, session archiving supports a dry-run option when writing updates at session end. By default, updates are written on-demand, and the dry-run mode allows you to preview the context changes before they are committed to the file.

You should avoid automated session continuity if your workflow cannot accommodate a 300-line context cap or 72-hour TTL limit. These hard caps are enforced to prevent context drift, making it unsuitable for projects requiring unbounded session memory.