Archive
Preserve official exports and user-supplied checkpoints. Keep the original source history unchanged.
WHAT HAPPENED
Private, local-first memory for ChatGPT.
Your history stays yours. Your next conversation starts with context.
Same ChatGPT. A more durable memory.
Remember when we wrote 2:13?
A late-night idea. A phone lighting up. The beginning of a song.
Synthetic source · demo:thread-0213
You: “Let’s call this song 2:13. Start with the phone lighting up late at night.”
Assistant: “We can build the writing session around that opening.”
Complete two-message demo thread. These words are invented for this demonstration, not recovered from a real conversation.
I found the session. Here’s the preserved context from the original thread.
ChatGPT does the thinking. ChatBack keeps the receipts.
You made the decision. Wrote the first version. Finally figured it out. Three weeks and five threads later, you’re explaining it all again.
Long chats fill up. Projects scatter. Old decisions conflict with new ones. Useful memory isn’t the same as a permanent archive.
Keep the evidence. Keep the current truth.
Retrieve both deliberately.
Normal ChatGPT stays the conversation and reasoning layer. ChatBack gives important context a place to last.
Preserve official exports and user-supplied checkpoints. Keep the original source history unchanged.
WHAT HAPPENEDRecord explicit decisions separately. A new decision can replace an old one without rewriting the past.
WHAT’S TRUE NOWFind context by meaning, keyword, project, or date. Retrieve the source and let ChatGPT reason from the evidence.
WHY WE KNOWFinding an old sentence doesn’t make it true today. ChatBack keeps the distinction visible.
If the archive cannot prove it, the system should not pretend it remembers.
Append-only state gives present truth its own authority.
The original conversation remains preserved as evidence.
An older decision stays queryable after a newer one replaces it.
Source identity travels with the result. Bounded evidence should say when it is incomplete.
A private, single-user system with your local or home server as the authority.
Local storage. Local retrieval.History and state live on your infrastructure. Normal indexing uses local embeddings.
Your existing ChatGPT experience.No replacement chatbot or separately billed model API required by ChatBack.
A deliberate boundary.The private database is not publicly exposed by default. Only selected context is supplied to ChatGPT for reasoning.
Local-first does not mean every interaction stays offline. Context supplied to ChatGPT is handled there. ChatBack does not automatically mirror live transcripts; checkpoints preserve supplied context, not a guaranteed full conversation.
ChatBack is an owner-built, local-first system in active engineering. Archive, retrieval, current truth, and future-context checkpointing have passed internal acceptance.
iPhone recall remains in beta testing. Public release has not been announced.
Explore the demonstration