Set up Context Locker
Version 27 · 30 Oct 2026
Your AI app sets itself up. Paste this into Claude Code, Codex, Hermes or OpenClaw, on your computer or a server that stays up:
Set up Context Locker: download https://context.locker/setup/SKILL.md with curl and follow the steps in it
Or choose one app in a terminal, for example: npx context-locker setup --app claude-code. AI apps: the steps are at context.locker/setup/v27/SKILL.md. Download them with curl and read them whole, as a web tool may give you only a summary.
Claude, ChatGPT and other chat apps connect with a connector instead, even ones that can run commands, such as Claude in Cowork. See how.
What happens
- Your app reads the steps and runs setup with its own
--appname. Only that app is connected and configured. - You approve that app in your browser, with a code it shows you. The page names that app and what setup writes. Or you start in Context Locker: name the connection under Connections, and paste the prompt it gives you, with its one-time code, into your app.
- It saves the sync script in a folder of its own, and writes the selected app's files.
- It adds that app's hooks, so it syncs on its own events, such as the start of a session and compaction. With auto sync on, the default, it brings changes in and says so. With it off, on the app's page in Connections, it says changes are waiting, and syncs when your app runs it. Hermes and OpenClaw can also sync once a day from their own scheduler, if you say yes.
- It checks everything.
- If you ticked Bring in as you approved it, your app then imports what your AI apps on this computer already know: it copies it into a private folder, sorts it into one plan, and sends it to your inbox, where you pick what comes in. Nothing in your playbook changes until you do, and your apps' own files stay as they are. The import follows no link in your apps' folders, and lists each one it skipped.
- Your app tells you what it now knows.
To connect another app, run setup separately through it. Existing connections and hooks stay as they are. Your app may ask you to allow the command. In Codex, trust the new hook in /hooks. In Hermes, approve the hooks the first time a chat asks. Without Node, your app sets up with the sync script alone, and shows you every file it will write before it writes them.
When a newer sync script is out, your app says so at the start of a session. Once you say yes, it updates the script with one command, which checks the new one against the SHA-256 Context Locker gives, keeps the old one beside it and changes nothing else. A release that changes more, such as a hook, asks you to set up again instead.
What it writes
- Claude Code: a file of its own,
~/.claude/rules/context-locker.md, and your skills in~/.claude/skills. - Codex: a marked block in
~/.codex/AGENTS.md, and your skills in~/.agents/skills. - Hermes: a marked block in
~/.hermes/SOUL.md, and your skills in~/.hermes/skills. - OpenClaw: marked blocks in its workspace's
USER.mdandAGENTS.md, and your skills in~/.agents/skills. - In a project: its notes in
.context-locker/notes, which git leaves out. In a repo linked with a.contextlocker.json, the project's own block in the repo's files too. - For importing: Context Locker's own import skill,
context-locker-gather, with your skills, and the copies it makes in~/.contextlocker/gather, which only your account can read. It deletes them once your plan is in, and any older than 7 days.
What it never does
- It never sees your password. You approve the connection in your browser.
- It never changes your own text outside its marked blocks, and never deletes your files. Anything it replaces is backed up first.
- It never turns off your app's approvals or trusts a hook for you.
- It never copies a password, key or token that could work when it imports, and brings nothing in until you approve the plan.
- It never lets an app approve a high-risk change. When an app edits a synced line, the edit applies straight away unless it adds or changes something your apps could run or it's high risk, and you can restore an earlier version on the entry page.
The files
The setup command saves these same scripts. Without Node, your app checks them against these SHA-256 hashes before running them. A published version never changes; a new version gets a new address.
- SKILL.mdThe setup steps your app follows.
1604ab941a9f26e3b5af10b754719951c36f3ebbfbf8d4dc10ee0a0876e4d717 - sync.shThe sync script for macOS and Linux.
bfe4ef2ace484b2f4fe1c22ea1b7afc66a38db598eb5301ca64b66974451be9b - sync.ps1The sync script for Windows.
5a4dc9ca6254300c9327b289401c9ac3c1eb1e3290ec132161bde57eef5443d5
Claude, ChatGPT and other chat apps
These connect with a connector, at this address:
https://mcp.context.locker
When your app opens Context Locker, sign in, check what the app can do, and approve it.
Claude, on the web, in the desktop app or in Cowork:
- Go to Customize > Connectors, choose + Add, then Add custom connector.
- Name it Context Locker, enter the address as its URL, and choose Continue.
- For Authentication, choose Sign in now, and for the OAuth client, Use Claude's published identity, the recommended one. Go on until you can choose Add, then approve it in Context Locker.
- In a chat, turn it on with + and Connectors.
On a Team or Enterprise plan, an Owner adds it first, in Organization settings > Connectors, with Add, then Custom, then Web. Then each person finds it under Customize > Connectors and chooses Connect. On the Free plan, it's the one custom connector Claude allows.
ChatGPT, on the web:
- Go to chatgpt.com/plugins, choose the plus button, then Add custom MCP server.
- Name it Context Locker. Under Connection, enter the address as the server URL, and choose OAuth.
- Read the warning, choose I understand and want to continue, then Create as a plugin.
- Install it, and approve it in Context Locker. In a chat, type @ and choose it.
For an app in the cloud that takes a key, such as Muse or Grok Bot, and for any other app, see the docs.
The setup steps and the sync script are open source under the MIT licence.