Editors, agents and frameworks

Every page here assumes kscope is installed and activated — Getting started covers both.

Everything on this page reaches one engine on your machine and sees the same two tools, search and remember.

Editors

cd ~/your-project
kscope init

Restart the editor, then ask it to search your memory.

kscope init wires every editor whose configuration directory already exists. kscope init --no-wire creates the vault and writes no editor configuration.

Editor	MCP entry	Instructions	Skill
Claude Code	~/.claude.json, for this project only	CLAUDE.md	.claude/skills/use-kaleidoscope/
Codex	.codex/config.toml	AGENTS.md	.agents/skills/use-kaleidoscope/
Cursor	.cursor/mcp.json	.cursor/rules/kaleidoscope.mdc	none
OpenCode	opencode.json	AGENTS.md	.agents/skills/use-kaleidoscope/

Every path without ~/ is in the project. Each project gets its own vault and its own profile, named after the project folder. kscope init --shared wires the project to one vault in your home folder instead.

Cursor gets a rule file and no skill.

Everything else

Other MCP clients and agent frameworks read the same launch descriptor.

kscope profile launch default

Client	Page
Any MCP client	Any other MCP client
Claude Agent SDK	Claude Agent SDK
OpenAI Agents SDK	OpenAI Agents SDK
LangChain	LangChain
LangGraph	LangGraph
CrewAI	CrewAI

Before any of it

npm install -g @kleos-research/kaleidoscope gives you kscope, and running it needs a key. Install covers both steps. Give your agent the skill is the file that tells an agent when to read its memory and when to write to it.