session-tracker

To maintain agent session context across restarts, rolling checkpoints and concise summaries are written to SeleneDB at completion. This ensures prior context is captured and automatically injected into new sessions via a SessionStart hook.

Tracking multi-agent collaboration history is handled through agent registration, heartbeat updates, and built-in timeline queries. This prevents premature session reaping and surfaces active peers alongside recent work summaries stored in SeleneDB.

Yes, you can use SeleneDB to search past session summaries and decisions. The skill provides built-in history, search, and timeline queries that let users and agents review recent work and trace artifact chains directly.

Agents load previous session context automatically through a SessionStart hook that injects recent summaries, active milestones, and open findings. This ensures new agent sessions start informed without manual context retrieval.

Session tracking works for debugging and project design sessions by applying rolling checkpoints to capture outcomes and next steps. This provides continuity for project work and reviews across multiple agent restarts and collaborations.

When an agent shuts down, a clean shutdown process shares the final session summary and deregisters the agent. This releases active intents, provides short-term visibility, and prevents the session from being prematurely reaped.