cross-session-knowledge-threads

To keep documentation context persistent across sessions, use durable knowledge threads that accumulate entries, decisions, and partial work. This allows ongoing investigations to remain accessible and resume exactly where they left off.

Tracking decisions and ongoing work across phases is best handled by cross-referencing durable knowledge threads with related phases and seeds. This preserves context and enables seamless resume operations for complex investigations.

You create cross-session threads by opening a thread with a descriptive title and appending notes, findings, or questions. Manage them using lifecycle operations like list, search, resume, and close to maintain structured documentation.

Yes, you can search and filter persistent knowledge threads by tags or status. This allows you to quickly locate specific decision-tracking entries or ongoing investigations stored within the durable thread structure.

You need cross-session knowledge threads when topics span multiple sessions or phases but are not phase-specific. They provide a structured way to accumulate context and decisions for work that cuts across the project.

Yes, cross-session thread management works without external dependencies. It uses a durable structure to store entries and supports lifecycle operations natively, ensuring context accumulation remains self-contained.