A thread of conversation that follows you.
For dinners, partnerships, friendships, co-working sessions, and small group discussions. CommonThread captures the audio of a multi-person conversation, paraphrases what came up, and writes the people and themes back into your private suite — so what surfaced at the table is available to the rest of your tools.
One app, several modes. The conversation is what it is — CommonThread adapts. Audio is captured on a phone in the room (single-device today; multi-device session joining is on the roadmap), processed in our pipeline, and deleted. What persists is the structured residue of the conversation: who came up, what topics surfaced, what threads got dropped — paraphrased, not transcribed, never quoted.
The structured residue is written into your private ContinuityCore, the shared layer underneath every Continuity Labs app. Mention a friend by name in CommonThread and that same person appears in POPs when you go to schedule something with them. A theme that came up in dinner conversation becomes available context for Steady's social prep, Thresh's reflection, and the rest of your suite.
One product, multiple shapes. You pick the mode that fits the moment.
The room is the room. CommonThread surfaces themes, the people who came up by name, and the threads the conversation dropped — without a transcript, without commentary, without scoring anyone.
A lightweight scaffold for intentional conversation, with sub-modes calibrated to context:
For book clubs, study groups, family meetings, planning sessions. Surfaces the shape of the conversation and the threads worth carrying forward.
New modes are added as we learn what kinds of conversation people actually want to capture. CommonThread stays one app — the modes are how the same product adapts.
This is not a policy. It is how the app is built.
On a phone in the room
Transcribed and analyzed in our pipeline — never returned to you
Paraphrased — themes, people, dropped threads. No verbatim quotes.
Within 24 hours of processing
CommonThread writes structured records into ContinuityCore — the shared layer that connects every Continuity Labs user app. The shape is concrete: each conversation produces a ContinuityRecord containing typed EntityReference values for the participants and themes that surfaced, plus the paraphrased artifact. Every other Continuity Labs app reads from the same store.
That means a friend mentioned at dinner is the same person POPs already knows. A topic that came up across two conversations is connected. The suite gets denser the more you use it — but the source-of-truth audio is gone within a day.
Social prep, post-event reflection
Life HQ — people, places, follow-ups
Reflection journaling
Voice-first object location
Conscious-consumption reflection
Today CommonThread captures audio on a single phone in the room. Multi-device session joining (so each participant's phone can contribute audio) is on the v3/v4 roadmap. Materials describing the destination architecture should be read as direction, not as currently shipping capability.
Things we're still working out — flagged here in the spirit of building in public.
.person entities for participants and .concept entities for themes via ContinuityRecord (following the pattern Chorus already uses). The exact downstream behavior — which surfaces in Steady, POPs, Thresh, MagikBox, Clearwater light up, and how — is undecided.