mnemonik-xyz/monorepo

**Signed memory that agents can keep, verify, and recover beyond one service.**
Website · Install and connect · CLI · SDK · Discord
Agents change runtimes. Services change operators. A useful memory should survive both.
Mnemonic makes memory a signed artifact that a client can retain, copy, and verify independently.
The operator provides delivery and discovery services; its database is not the authority for the artifact's author or contents.
The goal is practical: save private memory, recover it in a fresh client, and continue with another operator.
Recovery requires the original bytes, the necessary keys, and independently trusted authors and checkpoints.
It restores recorded memory, not a running process, tool credentials, or unfinished actions.
What we build around
- **Privacy at preparation.** Clients encrypt and sign sealed memories before sending them for storage. The prepared-artifact path does not send plaintext to the operator.
- **Verification without an account.** Retained signed bytes can be checked against a trusted author's key without the original operator or its SQL records.
- **A local copy you control.** Local sealed CLI writes need no hosted service. Clients can retain original artifacts and encrypted recovery backups.
- **An exit path.** Storage migration copies original signed bytes. Authenticated locator manifests describe new locations without changing authorship or signed parent references.
- **Open implementation.** Artifact formats, verification code, client libraries, and recovery tools live in this Apache-2.0 repository.
A signature proves authorship and integrity under the trusted key. It does not prove that a claim is true or provide a trusted timestamp alone.
Encryption protects content; public storage can still expose metadata. Lost decryption keys cannot be reconstructed from signatures.
Start locally
This README describes the current source. Published packages and hosted deployments can lag behind it.
See the implementation evidence for tested behavior and remaining acceptance work.
The capability matrix, local research handoff demo, and pilot runbook describe source support, repeatable evidence, and the remaining release gates.
Build the CLI from this checkout with Node.js 20+, Rust, and wasm-pack installed:
Standalone initialization creates a file-backed identity with restricted file permissions. Existing identities are preserved unless you explicitly replace them.
The current offline CLI write requires a file-backed key; it refuses an identity stored only in the OS keychain.
The CLI saves the original signed ciphertext locally. Keep your identity and backups safe; another key cannot open an owner-only memory.
The SDK's default local cache lasts only for the client session. Applications must supply durable storage or export a backup.
For a published CLI, use npx @mnemonik-xyz/cli and consult its version's command help.
To use a webapp identity, open Install, choose **Send to CLI**, then run init --ticket .
External delivery is explicit and can require authentication and payment:
Public plaintext writes use the legacy server-prepared flow, which sends content to the operator.
Current external delivery uploads to Arweave through ArDrive Turbo. Any Arweave gateway can read the stored bytes. Arweave is the single record of each anchored memory.
Recovery and portability
A recovery checkpoint records the trusted scope, expected heads, and artifact locations under an independently pinned owner's signature.