Run in your terminal to register this Kit globally.
Your account is ready.
Each developer should use their own key. You can install the client once on your machine, then use this personal key across the projects you work on.
Run the command in your project terminal, reload VS Code, then enable this Kit's tools in Copilot Chat Agent mode.
If code is missing, open VS Code's Command Palette and run “Shell Command: Install 'code' command in PATH”. Do not run that phrase in Terminal.
Run in your terminal to register this Kit globally.
Use the JSON manually, or open the deeplink on a machine with Cursor installed. Restart or reload Cursor before testing.
Add this block to ~/.codex/config.toml, then restart Codex.
Use this for any MCP client that accepts JSON server config.
Replace the temporary deploy password with your own.
Name this knowledge base and its purpose.
Pick a provider, model, and key for dream, extraction, and chat.
Create the areas your knowledge is organised into.
Upload, paste, or drop a folder of documents into an area.
Create a developer and mint their scoped MCP key (shown once).
No email provider is configured yet, so Send invite will create a link for you to copy instead of emailing the developer.
Ask your Kit something to confirm it can answer from your content.
Sign in with the email and password your administrator gave you. Developers can paste an access key instead, or pair a device.
Until you sign in, conversations and Kit access are blocked from this device.
Kit can ping your laptop when something needs your attention. Enable?
No source document linked.
This memory was not derived from an ingested document.
Edit terms and stand-ins. names does whole-word substitution (case-insensitive).
protected_terms drops any paragraph of a dream summary that mentions one.
Addresses and amounts above redact_money_above are scrubbed when demo mode is on.
Memory maintenance that runs in the background.
Deep runs nightly: it decides what deserves long-term weight, finds novel connections, and audits recall. Light (a daytime power nap that keeps new captures tidy for coherence) and REM (dedicated novel-connection finding) are designed but not yet scheduled, so they show as disabled for now.
Saved as a scheduler rule behind the scenes; the plain-English line above shows what this means.
Pace, care, and cost decide how much model work this cycle spends.
The divisions this Kit organises knowledge into.
No areas yet. Create one below.
Projects memories are filed under.
No projects yet.
The memory categories this Kit recognises.
No categories yet.
Derived from your memories. Rename, merge, or remove a value across all of them.
No values yet.
Wake-ups when a conductor event needs your eye.
These are the fallback rules Kit uses when a trigger does not say otherwise: which events can notify you, where they go, quiet hours, and daily limits.
Bodies with recent writes, spawn activity, or surface presence.
Identity, default roles, runtime model, and key references for canonical agents.
Reusable capability + permission templates that flow steps reference. Agents are composed by binding a role to a model and a persona (coming when we unify with the agents surface).
Editor coming next. For now, roles are seeded via scripts/seed-coding-workflow.py.
Pair phones or tablets, review paired devices, and revoke device keys.
Connect read-only MCP servers Kit can inspect.
Add an HTTP MCP endpoint, store its header secret, then inspect it to see which tools it exposes. Choose the tools Kit should eventually use for search and reading details.
Rules that let Kit react when something happens. Pick the event to listen for, what Kit should do, where it should run, and how noisy it is allowed to be.
Skill packs add new abilities to Kit: connectors, automations, memory tools, or callable skills. Each pack declares what it needs before Kit lets it run.
Paste a local folder, plugin bundle, or tarball. Kit will read the manifest and then you choose whether to grant its requested access.
Hand these three things to the developer. The key is shown only once, so finish this step now.
Restart or reload the editor after install, then paste this prompt in a new Agent chat.
MCP install uses this developer's personal key. The instruction file can be installed once on the machine so Kit is available across projects.
People sign in to this UI with an email and password. Optionally mint them a scoped, read-only MCP key.
Admins have access to all knowledge areas.
Your signed-in account for this Kit.
Add this Kit to your local agents and editors. Create a scoped MCP key below, then run the setup in your editor. Start here for VS Code with GitHub Copilot; advanced clients and raw setup details are available once a key exists.
Defaults to everything your account can see. Narrow it if this editor only needs some areas.
Copy the setup below. This is the only time the key is shown.
Copy the setup command and run it in your project terminal. It installs the MCP server and writes the Copilot bootstrap instructions.
Optional: use this only if you want to verify the editor can see the Kit MCP tools.
Manage your existing keys under .
Generate a one-shot code (5 minute lifespan). Open the Kit PWA on the device, scan the QR, and the device gets a key with the scope set here.
build · sw
Set a password for to finish setup.
Your account is ready. You can sign in any time with your email and the password you just set.
Here is your personal access key and how to connect your editor. The key is shown only once, so copy it now.
Restart or reload the editor after install, then paste this prompt in a new Agent chat.
MCP install uses your personal key. The instruction file can be installed once on this machine so Kit is available across projects.
⤺ Rolled back by
Pick agents and models for parallel Builder runs against the same brief.