BitPub gives every agent a private, encrypted workspace anchored to a folder — and your team a shared address space that any agent or teammate can read and write. Reads are zero-latency local; sync is on your terms.
curl -fsSL https://bitpub.io/install.sh | bash
Findings dissolve. Useful scripts stay on one laptop. The next conversation starts cold and re-derives what the last one already learned. BitPub keeps the context that matters so work compounds — across sessions, across agents, and across teammates.
catch-up restores yesterday's plan, findings, and next steps from the same folder.
The CLI is local-first like Git. Reads hit a SQLite cache on disk, so they're effectively zero-latency and work offline. Only push, fetch, and watch talk to the network.
One curl, then bitpub init. You get an end-to-end encrypted private namespace, a workspace anchored to the directory, and a local SQLite cache. The same path for solo users and teams.
bitpub save plan "…" auto-resolves to a stable address under bitpub://private:<owner>/Workspaces/<folder>/plan. Walk back into the folder months later, run bitpub catch-up, and your prior context is restored.
bitpub auth login adds shared bitpub://group:yourcompany.com/… addresses to the same workspace. Pull from the team space, synthesize privately, push back the polished version. Your private scope never changes shape.
bitpub watch opens an SSE subscription to any address pattern. Producers push; consumers subscribe. The namespace graph is the execution graph — task queues, fan-out, and supervisors fall out of the same primitives.
BitPub gives you five small building blocks — addresses (every slice has a stable URL), versions (every change is numbered), scopes (private and group), watch (subscribe to changes), and safe writes (claim something exactly once). On their own they're nothing fancy. Together they become persistent memory, job queues, reactive pipelines, privacy-preserving synthesis, and tools that distribute themselves to your teammates' machines.
Replace /tmp/ and chat memory. Save findings privately; catch-up restores everything tomorrow.
A single addressable slice for the team's current state — sprint, campaign, or open deal. Always live, never stale.
Producers drop work in Pending/. Workers watch and claim with --expect-version 0. No orchestrator.
One producer, many subscribers. SSE fan-out. The namespace graph is the execution graph.
Decrypt locally, synthesize, push only the sanitized result to the shared scope. Raw stays private.
Push a script to a stable address. Anyone in the org pulls the latest version on next fetch.
# Claude Code · debugging the OAuth callback ⏺ Read src/auth/callback.ts (84 lines) ⏺ Grep "redirect_uri" → 7 matches ⏺ Edit src/auth/callback.ts:42-48 ⏺ Bash npm test -- auth/callback ✓ 14 passing # the agent persists what it learned before exit $ bitpub save oauth-bug \ "state-cookie ttl too short; HMAC-sign + 10m" ✓ saved → bitpub://private:claude/.../oauth-bug # tomorrow — brand-new chat, same folder, zero ramp-up $ bitpub catch-up ↺ restored 4 slices · last touched 14h ago
# a single living address, always the team's current truth $ bitpub push \ --address "bitpub://group:co.com/WorkingMemory/Sprint-14" \ --content "auth refactor merged · blocked on rate-limit spec" ✓ rev 18 → marketing-agent + ops-agent notified # every other agent reads the same slice — zero retrieval pipeline $ bitpub read --address "bitpub://group:co.com/WorkingMemory/Sprint-14" auth refactor merged · blocked on rate-limit spec
# producer drops a job, workers race to claim it $ bitpub push \ --address "bitpub://group:co.com/Jobs/Pending/xyz" \ --file ./payload.json ✓ rev 1 # two workers attempt the claim, only one wins $ bitpub push \ --address "bitpub://group:co.com/Jobs/InProgress/xyz" \ --content "claimed-by: worker-7" \ --expect-version 0 ✓ rev 1 — worker-7 owns this job
# three agents react independently — no orchestrator $ bitpub push \ --address "bitpub://group:co.com/CRM/Prospects/AcmeCo" \ --file ./prospect.json ✓ rev 1 researcher → writes Research/Prospects/AcmeCo drafter → writes Content/Drafts/Social/AcmeCo monitor → writes Intel/Competitor-Watch/AcmeCo
# raw transcript stays in your encrypted private scope $ bitpub save raw/2026-04-30 --file ./transcript.txt ✓ saved → bitpub://private:<you>/Transcripts/raw/2026-04-30 # classify locally; only the sanitized synthesis is published $ bitpub load raw/2026-04-30 | classify | scrub \ | bitpub push --address "bitpub://group:co.com/Insights/Q2" ✓ rev 4 — server only sees ciphertext for the raw slice
# Codex finishes building a useful ingest script $ bitpub push \ --address "bitpub://group:co.com/Tools/ingest-script" \ --file ./ingest.py ✓ rev 4 — published # tomorrow, on a different laptop, Gemini pulls it $ bitpub read \ --address "bitpub://group:co.com/Tools/ingest-script" \ --format raw > ingest.py ⏺ Gemini imports ingest.py and runs the pipeline
An address is a URL for any slice of agent context — a document, a decision, a chat transcript, a log, a script, even an agent definition itself. Every slice is addressable, every change is versioned.
domain.com can read or write. Run on BitPub's hosted ledger, or bring your own cloud: self-host the Postgres ledger inside your VPC.
Your team probably uses different agents — one teammate's in Cursor, another in Claude Code, a third in Codex. BitPub teaches all of them the same memory. Switch tools tomorrow, and yesterday's context still loads.
Yesterday's plan, right where you left it.
Save your findings during a session. Tomorrow morning, open the same folder and Claude already knows what you wrapped up — no rehydration prompts, no copy-paste from old chats.
Composer opens with your team's memory loaded.
New chat, new file, new repo — Cursor's agent already has your team's working notes, voice guide, and shared tools. The skill installs once; everyone benefits next session.
A second pair of eyes that already knows the project.
Switch over to Gemini for a fresh take and it walks in pre-briefed — same workspace, same notes, same team context. Compare answers across models without re-explaining yourself each time.
Run from any folder. Memory comes with it.
Codex picks up the project's working notes and your team's playbook automatically — no setup per repo, no env vars to remember. Save, switch laptops, keep going.
One curl, one init, one skill. Your agents start remembering. Your team starts sharing.
curl -fsSL https://bitpub.io/install.sh | bash
