# Kaleidoscope

> Local native memory for agents. Your memory lives in a vault on your machine, and every editor or agent you connect shares one profile through a command-line tool and a long-lived stdio MCP server. Kaleidoscope is not released: nothing installs from a registry, and signing in does not work.

- [Documentation](https://memory.kleosresearch.xyz/docs/): what Kaleidoscope is, and which page answers your question
- [Getting started](https://memory.kleosresearch.xyz/docs/getting-started/): the five commands you will run, in order
- [Give your agent the skill](https://memory.kleosresearch.xyz/docs/skill/): how an agent is told Kaleidoscope exists, and the four files it installs
- [Install](https://memory.kleosresearch.xyz/docs/packages/): the two package names, what is inside them, and why you cannot install them yet
- [CLI reference](https://memory.kleosresearch.xyz/docs/cli/): every `kaleidoscope` command and flag
- [MCP reference](https://memory.kleosresearch.xyz/docs/mcp/): the two tools an agent sees, `search` and `remember`, and how to call them
- [Integrations](https://memory.kleosresearch.xyz/docs/integrations/): Codex, Claude Code, Cursor, OpenCode, LangChain, LangGraph, Claude Agent SDK, OpenAI Agents SDK, CrewAI, and any standard MCP client
- [Security](https://memory.kleosresearch.xyz/docs/security/): what is isolated from what, what is not signed, and how to report a vulnerability
- [Privacy](https://memory.kleosresearch.xyz/docs/privacy/): what stays on your machine, where a credential would be kept, and what this website itself does
- [Licenses and terms](https://memory.kleosresearch.xyz/docs/legal/): Apache-2.0 and CC BY 4.0 are in force; the product terms are unreviewed drafts
- [Privacy notice](https://memory.kleosresearch.xyz/docs/legal/privacy-notice/): an unreviewed draft of the production privacy terms, not in force
- [Security policy](https://memory.kleosresearch.xyz/docs/legal/security-policy/): an unreviewed draft of the disclosure and supported-version policy, not in force
- [Support policy](https://memory.kleosresearch.xyz/docs/legal/support-policy/): an unreviewed draft of the support scope and response targets, not in force
- [Account](https://memory.kleosresearch.xyz/docs/account/): you do not need an account, and you cannot create one yet
- [Operations](https://memory.kleosresearch.xyz/docs/operations/): back up your memory, move it, uninstall, and delete a vault safely
- [Platforms](https://memory.kleosresearch.xyz/docs/compatibility/): which platforms Kaleidoscope is for, and the one thing Windows does differently
- [Benchmarks](https://memory.kleosresearch.xyz/docs/benchmarks/): two separate experiments — on the larger corpus, twelve times the memories at the same answer quality; on the smaller one, level with mem0 at 24% fewer tokens
- [Status](https://memory.kleosresearch.xyz/status/): whether anything is available, whether anything is down, and what has actually been run
- [Public agent skill](https://memory.kleosresearch.xyz/SKILL.md): how an agent should retrieve and write memory
- [Agent instructions](https://memory.kleosresearch.xyz/agent-instructions.md): the short pointers Kaleidoscope installs into AGENTS.md, CLAUDE.md, or a Cursor rule
- [Status record](https://memory.kleosresearch.xyz/status.json): the same status these pages state, in machine-readable form
- [Platform support record](https://memory.kleosresearch.xyz/platform-support.json): which platforms have been run on and which have only had a compiler check
- [Full CLI help text](https://memory.kleosresearch.xyz/reference/kaleidoscope-cli.txt): the complete `kaleidoscope` help output
- [Tool reference](https://memory.kleosresearch.xyz/reference/kaleidoscope-mcp.json): the fields of the two tools an agent sees

Kaleidoscope has only ever been run on one kind of machine: a Mac with Apple Silicon. On that machine you can run a build you already have, connect Claude Code, Codex, OpenCode, Cursor, a standard MCP client or an agent framework to it, and have them all share one local memory. You cannot install it from npm or PyPI, because neither package is published; you cannot download a build for any platform; and you cannot sign in, because no sign-in service is configured and every account command answers `provider not configured`. macOS on Intel, Linux on x86_64 and arm64, and Windows on x86_64 have had a compiler check for the memory engine and nothing more — nothing was ever assembled into a program for them and nothing has been run there. Windows on arm64 has not had even that, and on Windows creating a new vault is refused on purpose until its filesystem work lands. Three connections carry a limit: Codex's configuration entry is written, read back and removed exactly, but Codex offers no way to confirm it then starts the server; Cursor's configuration and project rule are written and removed exactly, but Cursor has never been launched against them; and the agent frameworks were run against stand-in models rather than a live provider. Nothing has been driven through an editor's graphical interface. Nothing is signed for release. Apache-2.0 covers the public code and CC BY 4.0 covers this documentation, and both are in force; the product terms — the engine licence, the privacy notice, the security policy and the support policy — are unreviewed drafts that no counsel has read, and none of them is in force. There is no support commitment and no published security contact yet. Hosted memory does not exist: there is no service, endpoint, API or waitlist, and nothing syncs your memory anywhere. Benchmark results are stated in plain words on the benchmarks page; the full benchmark method is not published yet, and there is no build you could reproduce it with. The memory engine ships as proprietary object code, and its source is not in any public surface.