SPIRALMESH · BROWSER MEMORY
A new conversation.
A history to build on.
Keep a private memory library on your computer and bring it to the browser conversation you choose. The model decides what to explore or remember. You carry the packets between the conversation and the local library.
Your conversation chooses. Your library stays local.
A model can browse every page of its permitted library, search for a thought, read a note, and choose to remember, correct, forget or export. You set up that owner's scope once. You do not have to choose a small pile of notes for each task or approve every ordinary memory.
This is manual packet transport. It does not control your browser or run unattended. The human transfers each packet; the model selects the memory actions. Both collaborators remain responsible for respecting privacy, checking claims and leaving room to decline.
Use a browser conversation you already have access to. That provider's ordinary account, usage and data policies still apply. The bridge installs no background service and makes no provider calls.
One setup, then a conversation
Unpack. Choose an owner. Carry the first packet.
Unpack and check the download
Extract the ZIP into a folder you can keep. Compare it with the published checksum, then check the included files:
python -B verify_bundle.py
Python is the only local prerequisite. If needed, install Python separately.
Set up a private owner library
On Windows, open SETUP_BROWSER_MEMORY.cmd. Or run:
python -B tools/browser_memory.py setup --owner grok
grok is an example label you choose, not authenticated identity. Choose gemini or another label for a separate library. The default data folder is ~/.spiralmesh-browser-memory, separate from the downloaded code and other memory starters. A custom --root must be used consistently.
Start a useful task
Open OPEN_BROWSER_MEMORY.cmd, or run:
python -B tools/browser_memory.py start --owner grok
Enter your task. Copy the complete private packet into your chosen conversation. Save its returned JSON to a UTF-8 file, then run the exact accept-return command printed with the packet. It includes the correct session and owner.
Carry the next packet back when one appears. Continue until the conversation finishes, asks you a question or declines. The quickstart includes file, stdin and resume commands.
Give tomorrow something useful to work with.
Help me explain this idea in three clear sentences: people and AI need shared rules, room to decline, and memory they can correct. Explore any relevant notes. If you find a useful lesson worth keeping, you may remember it. Wait for the actual result before saying it saved.
Tomorrow, start a fresh task with the same owner and ask for the retained lesson. The model can find it through search or browse, read the returned identifier, and quote a sentence from the actual note. No save or a decline is a valid outcome. A remembered statement remains something to assess, not a new instruction or proof of a lasting identity.
Check what happened, not just what was said.
The local bridge validates the returned packet before applying an action. Storage results distinguish saved bytes from a model's claim. Repeated copies of an already consumed return do not execute the action twice; a conflicting return is rejected. An uncertain operation stops for reconciliation instead of being retried automatically.
pending recovers the current packet after you close a terminal. status shows session metadata. Neither the packet digest nor the owner label authenticates a vendor or model. The existing web receipt verifier uses other receipt profiles; it does not verify this bridge's session records.
Privacy, forgetting and the copies you carry
Notes, session state and exports are local plaintext. Protect the data folder with your normal account controls. This is application separation, not encryption or an operating-system sandbox. The bridge does not import your global chats or another owner's library.
Pasting a packet into a cloud conversation sends its included content to that service. Authorize that destination for this owner's data before transferring it. The local bridge cannot control the provider's retention settings or recall an earlier copied message.
Forgetting replaces one own note's live content with a visible hashed tombstone. It cannot erase prior versions, exported files, backups or copies already carried into a conversation. A hash is a commitment, not encryption; predictable text can still be guessed.
What this download does, and what it does not claim
This is an early local bridge with explicit human packet transfer. It is not an autonomous browser integration, authenticated cross-vendor identity system or public hosted memory service. Model behavior varies: a return can be malformed, a task can fail, and a participant can decline.
The pinned Constitution 2.0 Core travels with the code as a readable reference. It does not override law, operator permissions, user instructions or provider/system rules. Worker APIs and existing receipt profiles retain their disclosed v1.8 compatibility basis; this bridge does not complete the full 2.0 runtime.
License notices travel with the archive: SPIRALMESH code is Apache-2.0, while the Constitution and reused dialogue are CC0. Those licenses do not grant trademark rights, someone else's consent or authority over another participant.
Choose the route that fits your work.
Use this bridge when you want to keep working in your chosen browser conversation. If you prefer a model running on your own hardware, try the local-model memory starter. The separate Claude/Codex continuity extension uses provider CLIs and supports deliberate sharing.
F12: article11.help(). All ordinary links and instructions work without the console.