Concepts and boundaries

The boundary that matters is your local memory versus your account metadata — not merely whether you are signed in.

Local engine

The proprietary native engine owns the memory algorithm, the canonical vault on your machine, the graph, ranking, and the stdio MCP behavior. Its source is not part of the public CLI, client, integration, or skill surfaces.

Manager and profile

The kaleidoscope command creates profiles, validates the engine launch descriptor, edits host configuration safely, runs offline diagnostics, installs agent guidance, and carries the account and device commands. A profile may hold one explicit account UUID reference locally; that changes neither its vault identity nor its credentials.

What gets installed

You install one package for your language — the npm package or the Python package — and it brings in a second package built for your platform. The language package holds the full public client, the typed resolver that finds the installed payload, and the kaleidoscope and kscope commands. The platform package holds the manager and the proprietary engine as object code. Neither one contains engine source, and neither downloads anything at install time.

One profile, every tool

Codex, Claude Code, Cursor, OpenCode, framework clients, and generic MCP clients are consumers of the same profile. They do not become separate memory stores merely because their configuration formats differ.

Account identity

Signing in is designed to link a product account and a device. The account protocol rejects memory fields and absolute local paths before transport. Signing out or unlinking is not a vault operation, and must not be read as consent to upload memory.

Hosted memory

A hosted service is a later product requiring separate authorization, tenant isolation, retention, residency, deletion, sync, billing, and incident-response contracts. It does not exist, and signing in does not opt you into it.