Concepts

Five words carry most of these pages.

term	what it is
vault	The .kaleidoscope folder holding your memories and the graph. One per project, on your disk, unless you choose one shared vault.
profile	A named pointer to one vault. A project’s editors are registered against a profile named after the project folder.
engine	The native program that stores, ranks and serves memory, and speaks MCP over stdio.
manager	The setup half — creating a vault, editing editor configuration, installing agent guidance. Compiled into kscope.
account	A product account a device could be bound to. Not something you can create today.

Where your memory lives

Your memories are files in the vault, on the machine that wrote them. None of them is uploaded, and there is no service behind the engine to upload them to. The one server the engine contacts is the licence server, and it receives no memory.

Deleting .kaleidoscope deletes that project’s memory and nothing else. Operations covers moving, inspecting and verifying a vault.

One vault, every agent

Within a project, Claude Code, Codex, Cursor, OpenCode, the framework SDKs and any generic MCP client read the same profile. They see the same memories because they resolve the same vault.

Each editor stores its MCP configuration in a different format. kscope init writes each one and starts every server the same way, with the project’s profile:

kscope mcp --profile your-project

To give every project one vault instead, run kscope init --shared in each. It uses .kaleidoscope in your home folder.

Which vault a command resolves to, when it names no profile, comes from the project directory:

kscope where

What ships

You install one npm package, @kleos-research/kaleidoscope. It pulls in a second package built for your platform.

package	carries
@kleos-research/kaleidoscope	the kscope command, the client, and the resolver that finds the platform payload
the platform package	the engine, as object code, with the manager’s setup half compiled in

Neither contains engine source, and neither downloads anything at install time. Install has the machine requirements.

What does not ship yet

Signing in, binding a profile to an account, and listing or revoking devices belong to a second executable named kaleidoscope, published on no channel. Pages that show its commands mark them as not shipped.

A profile can record one account UUID locally. That changes neither its vault nor its credentials.

There is no hosted memory service, and no Python package you can use — kscope-memory on PyPI is a 0.0.0 placeholder. See Privacy for the boundary in full.