Hyperconsciousness
An encrypted, append-only notebook that syncs across your devices and lets an agent read or write only the slice you grant it.
by Louis Beaumont · Built this? Edit this page on GitHub
In short
HC (short for Hyperconsciousness) keeps notes, files and imported records in an encrypted, signed log on your own machines and syncs it between them. You give an agent a grant: which kinds of records, which tags, how sensitive, and for how many days. Through MCP the agent can then save notes and search the records its grant covers, by exact text or by a simple word ranking. Nothing is summarised, merged or forgotten for you: what goes in stays as written, and a writer can replace or withdraw its own notes with a newer version. It's a developer alpha.
Who it’s for
Developers and privacy-minded people who want one encrypted store for their own or their company's records, shared with agents like Codex and Claude Code on strict, expiring terms.
What it remembers
Whatever you or an agent writes or imports: notes, files and folders, and records copied in from chats, Slack, GitHub, documents, meetings and other tools by its ingestion recipes.
- Memory lives
- Your machines (or your company's server)
- API keys
- None
- Works with
- Codex, Claude Code, Any MCP client, CLI, HTTP API
- License
- Open sourceMIT
- Price
- Free
Under the hood
- Who writes memories
- You, a script, or an agent with a write grant. Each note is saved exactly as sent; HC adds no judgement of its own.
- Where they're kept
- An encrypted, signed, append-only log per device, synced between your machines, with a rebuildable encrypted search index.
- How they're found
- Exact text by default, or an optional word-based ranking (BM25), filtered by kind, tag and date and limited to what the grant allows.
- Extra AI calls
- None. It makes no AI calls.
How it works
- 1GrantYou give an agent read or write access to a slice, for a set number of days.
- 2RememberThe agent, or an ingestion recipe, appends notes through MCP.
- 3Encrypt and syncEach note is signed, encrypted and copied to your other devices.
- 4SearchThe agent searches by exact text or word ranking, within its grant.
What stands out
- No AI calls and no keys at all: it stores, encrypts and searches without any model or hosted service.
- Scoped, expiring grants per agent (by kind, tag and sensitivity), with every read and write logged and revocable.
- End-to-end encrypted sync between your own devices, plus a 24-word recovery kit and storage that can hold ciphertext without the keys.
- Corrections that keep history: a newer version hides the old one from search, while the signed log still holds what it used to say.
What it doesn’t do
- It doesn't decide what to keep, pull facts out of a conversation or summarise anything. An agent or a script has to write each note.
- Search matches words, not meaning: a question worded differently from the note can miss it.
- Nothing fades, strengthens with use or gets merged. Notes stay as written until their writer replaces or withdraws them, and withdrawn notes stay in the signed history.
- Grants limit what HC hands out, but they don't sandbox a program that already has your account or keys, and a hosted AI sees the plain text it's given.
- It's an alpha with no independent security audit, and the plain `hc read` command can show a tampered note without warning (MCP reads do check).
Measured against human memory
0 built, 1 partly, 10 not of the Field Guide’s 11 mechanisms
Encoding
Salience
Decides what's worth keeping, and how much, as a memory is written.
Everything written is kept as written; tags and sensitivity levels decide who may read a note, not how much it matters.
Emotion
Gives memories written with feeling more weight.
No emotional weighting.
Storage
Forgetting
Lets unused memories fade over time on its own.
Grants expire, but records don't: nothing fades or is deleted on its own, and a writer has to withdraw a note explicitly.
Interference
When a new memory closely matches an old one, notices and lets the newer one win.
It doesn't compare notes with each other, so near-copies and contradictions both stay. A writer can replace its own note with a newer version, which is graded under correction below.
Retrieval
Retrieval
Remembering something makes that memory stronger.
Every read is logged, but reading a record doesn't change how it ranks; ranking is word matching only.
Association
Links memories, so recalling one brings its neighbours.
A writer can list the records a note came from, and they come back with it, but search doesn't follow those links to bring up neighbours.
Prospective
Brings a memory back at the right time without being asked.
Nothing comes back on its own; recurring tasks and reminders are left to the harness on top. source
Transformation
Consolidation
Reworks memories between sessions: strengthening, merging, reorganising.
There's no pass that reworks, merges or links records between sessions.
Reconsolidation
Corrects a memory when it's contradicted, and keeps what it used to say.
A writer can save a newer version of its own note, or withdraw it; search then shows only the latest, while the signed log keeps what it used to say. Spotting the contradiction is up to the writer. source
Gist
Turns many specific moments into general knowledge.
Writers can label a note as derived, but HC itself draws no lessons or patterns; that's left to the harness on top. source
Schemas
Forms beliefs about people and projects, and weighs new facts against them.
It keeps no profile or summary of a person or project.
Not every system is trying to be a human memory, so a hollow dot isn’t a flaw. It just says what the system doesn’t do. What the mechanisms are.
Hyperconsciousness’s makers haven’t shared what they’re building next, so only today shows here. Makers can add their roadmap the same way they correct an entry.
Compare Hyperconsciousness with the others, side by sideQuestions
- Who is Hyperconsciousness for?
Developers and privacy-minded people who want one encrypted store for their own or their company's records, shared with agents like Codex and Claude Code on strict, expiring terms.
- Where does Hyperconsciousness keep its memories?
Your machines (or your company's server). An encrypted, signed, append-only log per device, synced between your machines, with a rebuildable encrypted search index.
- Does Hyperconsciousness forget?
Forgetting: not built. Grants expire, but records don't: nothing fades or is deleted on its own, and a writer has to withdraw a note explicitly.
- Does Hyperconsciousness correct a memory when it turns out to be wrong?
Reconsolidation: partly. A writer can save a newer version of its own note, or withdraw it; search then shows only the latest, while the signed log keeps what it used to say. Spotting the contradiction is up to the writer. source
- Is Hyperconsciousness open source?
Yes, it's open source. License: MIT. Code: github.com/louis030195/hyperconsciousness.
- Does Hyperconsciousness work with Claude Code?
Yes. Works with: Codex, Claude Code, Any MCP client, CLI, HTTP API.
- Does Hyperconsciousness need an API key?
API keys: None.
- How much does Hyperconsciousness cost?
Price: Free.