eidos : timestore :: git : GitHub
Hosted Timestore is in early access. Mac app 0.2.0 is a notarized DMG (Timestore.dmg). It mounts a Finder drive — File Provider — and syncs files between Macs you sign in. Private accounts encrypt them on your Mac before upload; keys are unlocked by OPAQUE sign-in. Standard accounts are not end-to-end encrypted. Trusted mode (FSKit) does not ship in that DMG.
An agent run — prompt, plan, edits, transcript — is real in the open core today, across processes on one machine, when the CLI and hook recorded it. The app does not record that transcript. Walk-up resume of an AI run is where this is going. It is not what every download does today. Live process state never comes back. You hold the keys on Private accounts and in the open core.
Open core is free and self-hostable. Hosted file sync is live in early access. Agent-run resume needs the CLI.
Open core ↗ · You hold the keys on Private accounts and in the open core · Self-host anytime · No vendor VM
In plain terms: close your laptop mid-task, open another machine, and your run — your code and the AI conversation — is already there, exactly. The two terminals below are the real proof; the line under each step says what just happened.
serving on 127.0.0.1:4399
One local process. No cloud. No credentials.
You do real work — an agent run, edits, a test.
recorded run 666e8a4c… → resume with: eidos resume 666e8a4c <dir>
One checkpoint captures files + transcript + provenance as a single run.
2 file(s) rehydrated → /tmp/restore (byte-identical)
A second process on this machine. The Mac app does not record this transcript — the CLI and hook do.
(no output)
diff -r returns nothing. Byte-for-byte identical.
honest_limit: files + transcript rehydrated exactly; LIVE PROCESS STATE (RAM, ports, servers) is NOT restored.
And it tells you the truth: your bytes and your conversation — not a running server.
note: this local coordinator is in-memory — it forgets on restart.
The hosted coordinator is the durable one. It is operating in early access, for files. This demo is still the CLI.
“The run died when I switched machines — the plan, the context, the half-finished edit, gone.”
timestore: Hosted early access syncs the files to the other Mac. The transcript follows only when the CLI and hook recorded the run — the DMG does not do that recording.
“I hand-write a handoff file, or paste the same context into a third tool for the fifth time today.”
timestore: Claude Code pins sessions to an absolute path — so cross-machine resume breaks by design. The CLI can record the run as the portable unit. The Mac app does not, yet.
“git GC'd the code I refactored away. It's genuinely gone.”
timestore: Chronos keeps the history on the Mac that saw the work, and Restore can put a deleted file back there, with undo. Recovery of a deletion from another Mac is not available yet.
The Mac app records file history as you work (Chronos). A run tagged with the agent, prompt, and transcript is recorded by the CLI and hook — that part is not in the DMG.
A synced filesystem and a version-control timeline are the same problem: replicating a content-addressed DAG. The hosted coordinator does that for early-access Macs. The loopback coordinator is the zero-cloud one, and it forgets on restart.
Open the other Mac and the files are there. The transcript comes back when the CLI recorded the run, on that machine's processes — not as a live server, and not from the DMG alone. Private accounts encrypt on your Mac before upload. Standard accounts are not end-to-end encrypted.
Hosted early access syncs files to another Mac you sign in. Private accounts encrypt them on your Mac before upload; keys are unlocked by OPAQUE sign-in. Standard accounts are not end-to-end encrypted. A checkpoint with the conversation attached resumes across processes in the open core, on one machine.
CLI proof: cli/test/checkpoint-resume.ts, zero cloud. The notarized Mac app syncs the Finder drive. It does not record the agent transcript. Live process state never resumes.
In the open core, the standard paths store only ciphertext, paths redacted. Private accounts encrypt Drive content on your Mac before upload. Standard accounts are not end-to-end encrypted: the operator can read Standard-account Drive content. Read the whole core, run it yourself, self-host the coordinator. Choosing timestore means choosing not to operate it — never to be trapped.
Per-path encryption keys; a key-holder resumes transparently, a non-holder fails closed (cli/test/ciphertext-default.ts). The core has zero runtime dependencies — only node:crypto. Verify it in seconds.
Which agent, which prompt, which model, did it pass its tests — when the CLI recorded the run. Deleted files this Mac saw can be restored, with undo. A deletion only another Mac recorded is not recoverable from here yet.
Conflicts are kept and surfaced, never silently merged. Today you resolve one by restoring an earlier point. Keep mine and Take theirs are not functional yet. The reconciler is property-tested at 50,000 triples.
File sync to your other Mac is live in early access. The whole agent run — transcript included — is the open-core CLI today, and the direction of hosted, not a claim the DMG already keeps.
| Restores the working tree | On your own second machine | Local-first, no vendor VM | You hold the keys | Per-run provenance | |
|---|---|---|---|---|---|
| timestore | ● | ●† | ● | ●‡ | ● |
| Claude Code /rewind | chat only* | path-pinned ✗ | ● | — | ✗ |
| Cursor cloud agents | in their VM | their VM ✗ | ✗ | ✗ | ✗ |
| jj / Sapling | y (local) | single-machine ✗ | ● | ✗ | ✗ |
The zero-cloud self-tests are the open core, and you can run them. Our hosted coordinator is already operating for early access. If you self-host your own Convex, R2, and NATS, those cloud-live tests stay red until you provision them — we show you that, we don't hide it.
eidos coordinator serve --port=4399
eidos checkpoint --flush
eidos resume <id> /tmp/restore
diff -r ./proj /tmp/restore # → no outputOn the open-core standard record, resume, and daemon paths the coordinator holds only ciphertext, paths redacted. That is not the hosted Standard account.
You hold the keys on Private accounts and in the open core. Private accounts sign in with OPAQUE and a mandatory recovery key, shown once, and encrypt Drive content on your Mac before upload. Open-core scope keys use a sealed device key, a scrypt floor, and Shamir 2-of-3. Standard accounts are not end-to-end encrypted: the operator can read Standard-account Drive content.
(Software custody. Secure Enclave / Touch ID is not in the shipping Mac app.)
The open-core secrets engine hands the agent a lease and can refuse it later with a kill-list.
(Crypto-shred of an account is designed, not live. Account deletion is suspended and does not shred keys.)
Read it, run it, self-host the coordinator. Hosted early access operates that same engine — it is not a second codebase.
The open core is free. Hosted Solo and Team checkout, and the customer portal, are in signed-in Settings. We are not publishing prices here. Storage is enforced: free 1 GiB, Solo 50 GiB, Team 500 GiB. There is no per-plan device, seat, or repo cap.
Open core
Free, forever
Yours to run. No card.
Hosted · Solo
Early access
Sign up. Both account types. Price is in Settings, not here.
Hosted · Team
Early access
Shared folders. No public price.
Hosted Free (sign in): 1 GiB. That quota is a signed-in hosted plan, separate from the open core.
/sign-up offers both account types (Private via OPAQUE, Standard via Clerk). /sign-up, /sign-in, and /downloads/Timestore.dmg work only while this site is served behind app-timestore. A standalone deploy does not serve them.
What's live — Self-host, the Mac app, hosted sync, accounts, team folders, Restore, and Settings checkout. No public price. Account deletion is suspended. SOC 2 has not started. The full ledger is on security — see the status.
Yes. The open core runs with zero cloud. Hosted early access is live: sign in, install Mac app 0.2.0, and mount the Finder drive. Recording an agent run with its transcript still needs the CLI and hook — the DMG does not do that.
When the CLI and hook recorded a run: the files and the transcript, byte-identical, across processes on one machine. Not live process state — RAM, ports, or running servers. The Mac app syncs files between Macs. It does not record the transcript. Walk-up resume of an AI run is the direction of early access, not something every download does today.
Files sync between Macs. Private accounts encrypt Drive content on your Mac before upload; keys are unlocked by OPAQUE sign-in. You hold those keys, and the recovery key is mandatory and shown once. Standard accounts are not end-to-end encrypted: the operator can read Standard-account Drive content. Standard accounts sign in with Clerk. In the open core, you hold the keys: the standard record, resume, and daemon paths store ciphertext, and a non-key-holder fails closed.
The core is open and self-hostable. Choosing hosted means choosing not to operate it. Account deletion in the hosted app is suspended: a request does not revoke devices, shred keys, or delete rows. Crypto-shred of an account is designed, not available.
No. Conflicts are kept and surfaced, never silently merged. Today you resolve one by restoring an earlier point. Keep mine and Take theirs are not functional yet.
Early access, not a certification. Accounts, hosted file sync, team folders, Restore, and Settings checkout are live. Reviews run on the web; the Mac app says review on the web. SOC 2 has not started. Windows, Linux, and iOS apps do not ship. Trusted / FSKit does not ship in the Mac app.
Try the open core, or sign in to hosted early access. We'll never pretend the DMG records an agent run, or that a price on this page exists.
Or try the open core ↗ right now — free, self-hostable, zero cloud.