demo

Watch ThreadRecall bring context back.

Ask with trecall:, and ThreadRecall brings the right captured AI conversation into your current tool, so you do not have to repeat old thinking.

Basic recall demo. ThreadRecall pulls the relevant conversation into the current AI workspace, saving context and tokens.

01 — everyday recall

Never lose a chat.

"I closed the chat window. A week later, I need the answer again."

captured automatically while you work
searchable by keyword or meaning
find it by what you said, not what app it was in

Even if the original chat is closed, buried, or deleted from view, the useful context is still searchable locally.

Recent conversations

Claude · Oct the best strategy for rebase vs merge depends on team...

ChatGPT · Sep you can handle this with a custom hook that watches...

Gemini · Aug for monorepo tooling, Nx and Turborepo handle module...

Search your conversations

⌕ rebase strategy

Claude · Oct the best strategy for rebase vs merge depends on team...

ChatGPT · Sep you can handle this with a custom hook that watches...

Gemini · Aug for monorepo tooling, Nx and Turborepo handle module...

Search your conversations

⌕ rebase strategy

Match found

Claude · Oct the best strategy for rebase vs merge depends on team...

ChatGPT · Sep you can handle this with a custom hook that watches...

02 — cross-app memory

Work across AI apps.

"I brainstormed in ChatGPT, refined in Claude, and implemented in Codex."

Claude, ChatGPT, Codex, Gemini, and Perplexity
context flows between them
one search covers all

Your work does not live in one AI app. ThreadRecall gives Claude, ChatGPT, Codex, Gemini, and Perplexity a shared memory layer.

Captured from

ChatGPT brainstorm

Claude refinement

Codex implementation

Linking context

ChatGPT

Claude

Codex

Context restored

⟡

Thread recovered

pricing redesign · 3 apps · 14 sessions

ChatGPT Claude Codex

All sessions searchable from one place.

03 — obsidian sync

Feed your second brain.

"I want my AI conversations to become part of my knowledge system."

connects to your Obsidian vault
one note per session, auto-tagged by topic
lives alongside your own notes

Optional Obsidian Sync turns AI sessions into linked notes you can keep, search, and build on.

Recent sessions

Claude · Nov Let's walk through a pricing model for the B2B tier...

ChatGPT · Nov Here's how I'd structure the onboarding flow for new...

Codex · Oct The rate limiting middleware should run before the auth...

Syncing to Obsidian

Pricing model — B2B tier

session from Claude, 3 Nov

#pricing #b2b

Rate limiting design

session from Codex, 1 Oct

#backend #api

Obsidian Sync

Pricing model — B2B tier

session from Claude · linked to [[Strategy notes]]

#pricing

Rate limiting design

session from Codex · linked to [[Backend 2025]]

#api

04 — decision recall

Remember decisions.

"What did I decide about pricing / roadmap / design direction?"

search by topic or project
find the reasoning, not just the answer
works across months of AI conversations

ThreadRecall helps recover the reasoning behind decisions, not just the final answer.

Older conversations

Perplexity · Jul Freemium conversion benchmarks: median 3–5% for B2B...

ChatGPT · Aug The roadmap priority for Q3 should focus on retention...

Claude · Sep On the pricing direction: the annual plan makes more...

Search your conversations

⌕ pricing direction

Perplexity · Jul Freemium conversion benchmarks: median 3–5% for B2B...

Claude · Sep On the pricing direction: the annual plan makes more...

Search your conversations

⌕ pricing direction

Decision context

Claude · Sep annual plan makes more sense — lower CAC, better LTV

Reasoning from 3 months ago, still searchable.

05 — project continuity

Restart a project.

"I haven't touched this in three weeks. Where did I leave off?"

Memory Brief surfaces recent context
see what was decided last
continue without re-explaining the project

Pick up long-running work without rereading every old chat or explaining the project from scratch.

Project sessions

Perplexity · Apr Research: PKCE vs implicit grant — current best practice...

Claude · Apr Architecture review: Postgres for primary, Redis deferred...

Codex · May Implemented PKCE handler — token rotation logic done...

Generating Memory Brief

Memory Brief

Using Postgres + deferred Redis

Auth: PKCE flow, not implicit

Loading more context

Memory Brief

Memory Brief — API project

Using Postgres + deferred Redis until scale requires it

Auth: PKCE flow, not implicit grant

Next step: rate limiting + API key rotation design

Ready to continue →

Ready to try it?

ThreadRecall is available in early access on Apple Silicon Macs.

Join early access →