A thread is a DAG of sessions tied together by intent
🌱
Origin
The seed session, usually a planning or roadmap session. A thread can have multiple origins.
🌿
Child
A session that continues the work. Each child has a parent. Re-parent or promote to origin anytime.
🔗
Edge
The parent-to-child link. Manual edges are confidence 1.0. Auto edges carry a confidence score and a source chip.
Three ways to add a session to a thread
Path 1
🧷
Session header
Open any session, click + Add to thread above the collections row. Pick an existing thread or create one with this session as the origin.
Path 2
🧵
Threads page
Top-bar Threads button. Pick a thread on the left, click + Add session in the right pane, filter by alias or project.
Path 3
⌨️
CLI
recall threads link <session-id> --thread <id-prefix>. Add --parent to make it a child of a specific node.
Pipe an entire thread back into a fresh Claude conversation
Threads
Hero above covers the DAG, anatomy, three add paths, and the pipe-into-Claude flow. Operational detail:
#Removal & re-parenting
Right-click a node → Remove from thread. The session stays in Recall; only the link drops. Children of a removed parent are re-parented to the grandparent (or promoted to origin).
#Cycle protection
Threads are acyclic by construction. The daemon rejects setParent calls that would create a cycle (self-parent, A↔B, longer chains).
#Auto-detection signals
recall threads scan infers parent-child links from:
- timing proximity
- file overlap between sessions
- continuation phrases ("continue from", "based on the plan in...")
- optional LLM rescore on borderline pairs
recall threads sync captures terminals running in the current repo right now. Idempotent. Manual edges preserved on re-run.