The local thread foundation.
The development build supports a local workspace, thread capture and entries, versioned working briefs, and context records linked to their selected sources.
It also records conversation-session metadata and accepts bounded imports of explicitly prepared conversation text. A local interface can display retained history and its known gaps.
These are implemented foundations, not a generally available release.
Continuity with better coverage.
Remaining foundation work includes thread forks and undo, data lifecycle and deletion, and broader recovery and volume testing.
Native conversation capture needs separate qualification for each tool. Automatic synchronization, complete history coverage, attachments, and returning context to a tool are not established by the current text-import foundation.
The standard
A useful record should show what it contains, where it came from, and what remains missing.
A connected workflow.
Planned work connects intent to scoped execution, handoffs between qualified AI tools, and results supported by evidence. Branching and reconnection are part of that direction.
These capabilities need implementation and validation before they can be offered as a complete experience. Public release timing, commercial pricing, and a hosted team service have not been announced.
Help us test the right problem.
We are interested in real examples of software work interrupted by context loss, tool changes, or unclear handoffs. Share your workflow when you request early access.
Request early access