Changelog
What has been built
Every entry here is in the code today. Plans live on the roadmap; this page only lists what shipped.
- Trust
Ready for people: a security review, a memory immune system and the first five minutes
Every part reviewed before launch, with each fix tested; memories from outside checked for hidden instructions; a guide from the recovery phrase to the first answer; a simpler vault; a vault of 100,000 memories measured.
- Twenty-nine findings fixed, each with a test: restores that could reach other vaults, ask links answered without the whole link, bundles changed on their way, a legacy release by one trusted person, sessions that outlived their sign-in, fetches into the node's own network, and more; the list is in docs/SECURITY-REVIEW.md
- The memory immune system: mail, chats and imports with instructions for an AI are held for your review in the inbox, every memory a model sees is quoted as data, every catch is sealed in your log, and a public test runs every hour at /immune
- A getting-started guide: the recovery phrase typed back, your ChatGPT or Claude history, one AI app with the exact steps, and its first answer from your memory; it keeps your place
- Five main sections, everything else under More in its four groups, pins that keep a section in the row; every link to a section works as before
- Plain help on every screen and plain words when something fails
- Search, the timeline and bundles fast with 100,000 memories; the numbers are in docs/PERFORMANCE.md
- Live sync can sign in on your computer, through the connector, for services that want a client secret
- A railway.toml for one service with a volume; the open standard 1.3.0
- Nodes
Your whole vault in one encrypted bundle, kept where you choose
Download the vault as one bundle, or store it in your own bucket, on IPFS or on Arweave with your own tokens, and restore it on any Sigil node with your recovery phrase or wallet.
- Every memory, key slot, setting, app, shared space and the sealed log with its proofs, still encrypted, signed with your vault key on your device
- Your own S3-compatible bucket, an IPFS pinning service or your own IPFS node, and Arweave through a bundler with your own key file; tokens kept only encrypted with your vault key, uploads made from your device
- Copies every day or week while your vault is open, and in the background from a connector you run with --watch
- Restore into an empty vault on any node from a file, a link, an IPFS content id, an Arweave id or your bucket; the bundle is opened and checked in full on your device first
- How long a copy lasts depends on where you keep it: the docs say so plainly
- Nodes
Run your own node, and move your vault between nodes
A Dockerfile and a compose file start a Sigil node with one command; a vault moves from one node to another with a statement signed by its own key.
- docker compose up -d --build: the same site and API, data in a volume, a health endpoint at /api/health
- A move signed on the old node, fetched by the new one with a code you carry, opened with your sign-in and confirmed by an arrival your key signs
- The old node sends your ask links, public page, packs and emergency card on to the new address for up to 90 days, then deletes the vault
- A node list in the vault: where it lives, where it came from, where its copies are; every step in the log and the hourly seal
- The open standard 1.2.0 with the bundle, the move and their test vectors; earlier vectors unchanged
- AI self
Talk to your AI self, and capture from anywhere
Speak to your AI self in the test chat, on ask links and on the public page, with speech to text on your device and answers read aloud by a voice on your device; and capture keys for phones, watches and shortcuts.
- Whisper in ONNX form in a worker on the device, loaded only when voice is turned on (about 41 MB, once); the browser's own speech recognition, which sends audio to a cloud, is never used
- Answers read aloud only with voices that run on the device
- Capture keys, one per device or shortcut: write-only into the inbox, sealed to your vault's key on the sending device, limited, logged and revoked on their own
- Ready-made steps for an Apple shortcut (Siri, headphones, and a watch with plain text allowed for that key) and for Android's share sheet and HTTP shortcut apps
- AI self
Sessions with an expert's AI self
Open times when anyone may book a short conversation with your public AI self, with topics, a number of questions, an intake, house rules and a cap per day. Free.
- Visitors book on your page; their intake is sealed in their browser for your device, and the session link holds the only key to the session
- Answers only from what you made public, under your house rules, each marked as AI
- You read every booking, what the visitor agreed to and the transcript, and can end a session or block its visitor
- Agents
Shared family and team memory
A family's or a team's history on a shared space: a timeline of stories with dates, people and photos, who added what, heirs, and a copy to keep or print.
- Roles as in team spaces; a member changes and deletes only what they wrote, and leaving or a deleted account never deletes what others wrote
- Heirs named by vault code become members when the legacy plan of the member they are named for releases
- The whole history as one readable document made on your device, and part of each member's bundle
- AI self
The AI self gets an identity and a wallet of its own
A key for the AI self, made on your device from your vault key, a statement signed by it and your vault, and a wallet it may use only within rules you set.
- The self's key, derived on the device and never stored; its address is the self's identity on any EVM chain
- An identity statement signed by the vault key and the self key, readable by anyone at its address and checked on the verify page
- Wallet rules drafted and kept encrypted in the vault: caps per payment and per day, recipients, contracts and their functions, token caps and an end date, with a check of any payment against the draft
- SigilSelfRegistry and SigilSelfWallet in contracts/, with Foundry tests and fuzzing of caps, freeze and expiry; not deployed. Until a site sets the registry's address, the Identity tab says so and works off chain
- AI self
An AI self that works and learns
Your AI self drafts replies, plans your week and answers people, all into an approval queue, and learns from the changes you make.
- Drafts of replies to a pasted message or a synced mail thread, and a plan of the next seven days from your calendar memories
- Answers to ask links, the public page and meetings of selves can be held for approval and sent through their own channel once you approve
- Nothing is sent on its own: approving a reply or a plan copies it
- Your edits become notes in a How I write folder, written by your own model or as a plain summary of the change; later drafts follow them, and you can change or delete each one
- Every draft, approval, discard and lesson in the read log and the hourly seal
- Proof
Prove a fact without showing it
A signed proof of one claim, sealed with the hour, that shows nothing else: one field of a memory, an age, months of sealed history, or membership of a team space.
- Each field of a memory committed with its own salt, so one can be shown and the rest stay hidden
- Sealed history and team spaces checked in full from the seals; a field or an age marked plainly as the owner's own statement
- Proofs shared by link or file and checked on the verify page in any browser; zero-knowledge proofs are on the roadmap
- Vault
An emergency card for the lock screen
A medical card from the health memories you pick, behind a code for your lock screen, that the server stores and cannot read.
- Blood type, allergies, medication, conditions, languages and who to call, drafted from your memories and edited before it goes out
- Encrypted on the device with a key that lives only in the code's link; a lock screen image with the code, made on the device
- Each opening shown to you with the time, a device class and a language, and nothing that tells who it was
- Take it down or issue a new code at any time; the page is large and plain on a phone and opens again without a signal once it was opened
- Sharing
Sealed agreements and knowledge packs
Agreements two vaults both sign and seal, and folders published as signed packs others follow.
- An agreement drafted in one vault, reviewed and signed in the other, both signatures over one fingerprint, sealed in both logs; amendments as new linked versions; nothing changed after signing
- A verifiable copy either side can show, checked on the verify page
- A folder published as a knowledge pack with a title, a description and a version, signed by your vault; followers take in each new version, checked against the publisher they followed
- Packs are free
- Trust
An open standard and a privacy score
The formats, keys, tools and log written down as an open standard with test vectors from the code, and a privacy score per app from your own read log.
- docs/spec: memories and folders, keys, envelopes and sealed boxes, the connector's tools and permissions, the access log, seals and presence, certificates, version 1.0.0; version 1.1.0 adds the self's identity and wallet, proofs of a fact, the emergency card, agreements and knowledge packs
- Test vectors generated from the code, and a check on every test run that the code still produces them; the standard on its own page, /spec
- A privacy score for every app and agent under Apps and Agents, computed in your browser from your own read log, with every point explained
- AI self
Selves meet selves
Your AI self can talk with someone else's, only after both of you said yes, for one purpose and a fixed number of turns.
- Invites by vault code, to find a time, check whether a collab fits, or swap intros; the other owner says yes and picks what their self may use
- Every turn encrypted under a key only the two vaults can derive, so the relay can neither read nor write one
- Each self answers within its own rules and folders, with its owner's model, and may read the calendar to find a time
- The whole transcript for both owners, a stop button for either, and every step in both read logs and seals
- AI self
A public AI self
A page at /@you where anyone can ask your AI self, answered only from folders you made public.
- A public copy of the folders you choose, masked with their rules, as the only thing it answers from; protected folders can never be public
- Questions sealed in the visitor's browser and answered by your open vault or your connector with your own model key; offline said plainly
- Every answer marked as AI with its sources; greeting, tone, topics, a limit per visitor, an off switch
- Every question and answer sealed in your read log; answers on the page only if you want, each one you can hide
- Vault
Protected vaults for health, money and legal
A folder can be protected: nothing reads it without your fresh yes for that read, and what leaves the vault can be masked.
- Protect a folder as health, money, legal or other; the server knows only that it is protected and holds its ciphertext back
- Requests wait in your inbox; a yes covers one read for ten minutes; your own AI self asks the same way
- Protected reads and your answers marked with their own kinds in the read log and the hourly seal
- Redaction on the device of card numbers, IBANs, account, ID and passport numbers, phone numbers and email addresses, per folder
- Sync
Your whole digital life, kept in sync
Gmail, Google Calendar, Google Drive and Slack stay in sync in folders you choose, fetched and encrypted on your device.
- Sign-in with OAuth and PKCE from your browser as a public client, the tokens encrypted with your vault key
- Only what changed is fetched: history ids, sync tokens, change tokens and the newest message per channel
- No duplicates with Takeout imports, ids two devices agree on, pause, and disconnect that deletes the sign-in
- Background sync with sigil-connector --watch, the source wrapped for that app's key only
- Meeting transcripts from Zoom, Meet and Teams as meeting memories: who was there, decisions, promises
- Legacy
Legacy: your AI self outlives you
Name the people who receive your vault, the folders each gets and whether they may talk to your AI self. They open it together, only after you have been away for the period you chose.
- Trusted people by vault code with a fingerprint, or by an invite link whose answer your vault checks before it seals anything
- A legacy key split with Shamir's secret sharing in your browser, each share sealed to one person's vault; each person's bundle sealed to them as well, so nobody opens another's
- A heartbeat from every sign-in and vault action, a check-in button, the next check-in date, and first and last warnings in your read log and in the vault when you come back
- A release room that relays shares sealed to the keys you named; shares combined in the trusted person's browser, folders read only, and your AI self in a labelled legacy mode
- Every step in your read log and the hourly seal; every change makes a new legacy key; a public page that explains it, limits included
- Devices
Your phone and every device
Sigil installs as an app, adds a device by QR code with keys sealed to that device only, and captures text, links and photos into your inbox.
- An installable app with icons from the mark, an offline app shell and, when you turn it on, an encrypted copy of the vault to read offline
- Add a device: a one-time key and a QR code on the new device, a code made from its key, a fingerprint on both screens, and the vault key sent sealed through a relay that keeps it ten minutes
- A device list with revoke: the key slot and every session of that device end at once, and it forgets its key the next time it reaches Sigil
- Quick capture, and the share sheet on Android: text, a link or a photo sealed on the phone to your vault's public key, without unlocking, queued while offline
- Photos kept inside a memory's encrypted body, and every vault screen laid out for a 375 pixel phone
- Agents
Agents get their own memory
Agent vaults for Cursor, Claude Code and any MCP client, team spaces shared by vaults and agents, and sealed handoff notes.
- An agent vault: its own folder and key, other folders to read or write, and a switch for each tool, enforced by the server
- remember, recall, forget, leave_handoff and pick_up_handoffs in the connector, all in the read log and the seals
- Team spaces with read, write and admin roles, the space key sealed to every member, member tags a server cannot forge, and a new key on removal
- Handoff notes for an agent's next session or for the other agents in a space, encrypted on the machine
- Setup steps for Claude Code, Cursor, VS Code, Claude Desktop and other MCP clients
- Proof
Proof of a real life, version 1
A certificate that a vault has months of continuous sealed history, without a word of what is in it.
- A signing key made from the vault key, and one signed presence statement per seal period while the vault is open, sealed with the hour
- A certificate built and signed in the browser: first and last seal, hours and days with activity, the longest gap, how long it ran without a gap of more than 30 days, and the proof of every hour
- A download, and a share link that opens the verify page
- The verify page checks it in the browser against the published seals, and against SigilSeal on chain when the seals are anchored
- AI self
Your AI self, version 1
An AI that answers as you, from the folders you choose and within rules you write, with your own model key. Share it with a link.
- Rules: the folders it may use, topics it may and may not discuss, things it must never say, its tone, and what it says when it does not know
- Your own Anthropic or OpenAI key, encrypted in the vault and used only from your browser or the connector on your machine
- A test chat in the vault that shows the memories each answer used
- Ask links with their own rules, an expiry, a number of questions and an hourly limit; questions and answers are end to end encrypted between the asker's browser and your open vault or connector
- When neither is running the link says your AI self is offline, and every question and answer goes into your read log, sealed
- ask_self in the connector for apps you allow, and sigil-connector --self to answer links while your vault is closed
- Vault
Memory that thinks
A weekly brief, memories that disagree, every duplicate group merged at once, and memories that expire.
- A weekly brief of what is new, what changed and what you may have forgotten, saved in a Briefs folder; written by your model when you allow it, as plain lists otherwise
- Pairs of memories that seem to disagree, found by meaning and by words, with an optional check by your model
- Merge every duplicate group after one approval
- An expiry date per memory: expired memories leave the list and apps, wait under Expired, and are deleted for real after a grace period you set
- Import
Your whole digital life, imported on your device
Obsidian, Apple Notes, Gmail and Google Calendar, Notion and GitHub, parsed and encrypted in the browser. No app approvals.
- Obsidian vaults with their tags, kept in sync by the connector watching the folder and suggesting changes through the inbox
- Apple Notes from the iCloud data copy or exported files
- Google Takeout: one memory per mail thread within size limits, one per calendar event
- Notion Markdown exports, zip inside zip included
- A GitHub repository's history or your recent activity, asked from the browser with a token that is never saved
- A preview, a folder choice and dedupe against what is already in the vault for every source
- Inbox
The memory inbox
Apps can suggest what to remember. Nothing becomes a memory until you approve it.
- Every vault gets an X25519 key pair; its private half is wrapped by the vault key
- A per-app switch, off by default: May suggest memories to your inbox
- propose_memory in the connector seals each suggestion on your computer, after checking a tag your vault made for that app
- An Inbox tab to edit, approve into a folder, merge into a memory or reject, with a hint when it is already in the vault
- Suggestions in the read log, 30 per app per hour, up to 500 waiting
- Search
Memory that understands
Search by meaning, run on your device, and the first tools that help keep a vault in order.
- A small sentence model on WebAssembly, in a worker in the vault and in the connector, never on the server
- Hybrid search by words and meaning in the vault and in search_memories
- Vectors kept in the browser only encrypted, under names that do not show the text
- Duplicates: the same text, nearly the same words or the same meaning, merged in one step
- A Timeline by date written or last changed, filtered by source
- The Self card, a short profile in its own folder, read by apps through get_profile
- Extension
The browser extension
Save a selection, a page or a whole ChatGPT or Claude conversation to your inbox, sealed in the browser.
- Chrome, Manifest V3, built as an unpacked extension
- Paired by an app key made under Apps; it checks the vault public key before sealing
- Right-click menu, a toolbar popup, and a small button on chatgpt.com and claude.ai
- SDK
Sign in with Sigil
Web apps can ask for read access to the folders you choose.
- A consent window in the vault that answers only the page that asked
- The @sigil/sdk package: requestAccess, then folders, search, read, the Self card and suggestions, decrypted in the browser
- An example app in examples/hello-sigil
- Sharing
Sharing between vaults
Share a folder with another Sigil vault, read only, and take it back.
- Vault codes with a fingerprint to compare
- Folder keys sealed to the other vault's public key; accept or decline on their side
- Every opening of a shared folder in the owner's read log
- Stop sharing gives the folder a new key and encrypts it again on the owner's device
- Site
The full site, live numbers and public proofs
Sigil's site grows from a landing page into the whole product: every part of it explained, measured and checkable.
- Grouped navigation: Product, Trust, Developers and Vision
- Public counters read from the server: vaults, memories, reads and sealed hours
- A Status page with the live health of the service and the seal job
- A public proof endpoint, and a checker that verifies a fingerprint, a log entry or a hand-made proof in the browser
- Setup guides for Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, ChatGPT and any MCP client
- An Import page whose drop zone hands the export straight to the vault
- The threat model, the API reference, the connector reference and this changelog
- A living page ground: engraved ciphertext under a slow drifting light
- Site
One vault, five readers
The home page shows the same vault as you, Sigil's server, Claude, ChatGPT and Cursor each get it.
- Lines lock into ciphertext wherever a reader was not given the folder
- The reader names are buttons, and the piece cycles on its own
- Site
Black and silver
The visual system: near-black ground, silver hairlines, a display serif, and self-hosted fonts only.
- One stylesheet driven by tokens
- No third-party fonts, scripts or trackers; the content security policy allows the site itself and nothing else
- Vault
The whole product, tested in a real browser
End-to-end tests run every flow in Chrome against the built server.
- Wallet and passkey sign-up and sign-in, with the recovery phrase
- Import, connecting an app, reading over MCP and revoking
- Seals made and verified, and the wallet deep link on a phone
- Vault
The vault dashboard
Everything you do with your vault, in one place.
- Sign in with a passkey or a wallet, and a 24-word recovery phrase
- Memories with titles, tags and folders, and search that runs in the browser
- Apps with per-folder permissions, a one-time app key and revoke
- The read log with Verify, import of ChatGPT and Claude exports, export and real delete
- Connector
The connector
One MCP server for every AI app, running on the user's own machine.
- Three read-only tools: list_folders, search_memories and read_memory
- Stdio for apps that start it, HTTP for apps that need a URL
- Decrypts locally and keeps nothing between requests
- Seals
The server, the read log and hourly seals
A server that stores ciphertext only, logs every read and seals each hour.
- One API router over SQLite, with deleted content overwritten on disk
- Every connector request written to the owner's read log with a salted fingerprint
- Each finished hour folded into one Merkle root that never changes afterwards
- Core
The core
The cryptography everything else stands on, in one package shared by the browser, the server and the connector.
- AES-256-GCM envelopes bound to their record, HKDF-SHA256 derivation, key slots and app keys
- Merkle seals and proofs
- Parsers for ChatGPT and Claude exports
- The SigilSeal contract, written and tested, not deployed
