Claude Code
Install and activate first — Getting started covers both. Without a
key the wiring below succeeds and the server refuses with E_NO_KEY the moment your editor
starts it.
kscope init wires Claude Code when ~/.claude or ~/.claude.json exists.
Wire it
Section titled “Wire it”cd ~/your-projectkscope initRestart Claude Code, then ask it to search your memory.
What init writes
Section titled “What init writes”| What | Where |
|---|---|
| MCP entry | ~/.claude.json, under projects, then the project’s absolute path, then mcpServers, as kaleidoscope |
| Instructions | CLAUDE.md, between kaleidoscope-manager markers |
| Skill | .claude/skills/use-kaleidoscope/SKILL.md |
| Receipt | ~/.claude.json.kaleidoscope-owner.local-<code>.json, one per project, and a .kaleidoscope-instruction-owner.json beside each instruction file and skill |
| Backup | ~/.claude.json.kaleidoscope-backup, when the file was already there |
{ "projects": { "/absolute/path/to/your-project": { "mcpServers": { "kaleidoscope": { "type": "stdio", "command": "/absolute/path/to/kscope", "args": ["mcp", "--profile", "your-project"] } } } }}This is Claude Code’s local scope: the entry applies to this project only.
init writes it for every existing checkout of the repository, the main one and
each worktree, and for the folder you ran it in. In a worktree you make later,
kscope where says to run kscope init there.
your-project is the profile init creates for the project, named after its
folder. With an npm install, the command is ~/.kaleidoscope/bin/kscope, a copy
of kscope that updates itself when you update kscope.
A project set up by an earlier version keeps its user-wide entry, under
mcpServers at the top of ~/.claude.json, and the default profile.
kscope init says so, and names the command that gives the project its own
vault.
Skills go to .claude/skills/ here. Codex and OpenCode read .agents/skills/.
Check it
Section titled “Check it”kscope profile launch your-project{"version":1,"transport":"stdio","command":"/absolute/path/to/kscope","args":["mcp","--profile","your-project"],"tools":["search","remember"],"environment":{}}Match args against the project’s entry in ~/.claude.json. command is the
kscope you ran, which is not the copy the entry names after an npm install.
Claude Code’s tool list should hold search and remember under
kaleidoscope, and nothing else.
Remove it
Section titled “Remove it”Delete each of these, and the receipt beside it:
- the
kaleidoscopeentry under your project’smcpServersin~/.claude.json - the marked block in
CLAUDE.md .claude/skills/use-kaleidoscope/
Your memory stays. Connect an editor or agent covers every editor at once.