Everything so far happened in your browser. This lesson takes it to your disk, safely, and then beyond your machine: to a colleague, to a repository and to a company.
Review the plan
Open Changes in Config Studio for Claude Code. It has two parts:
- Changes lists every key you moved off its default, with what it was and what you made it
- What it writes lists every file in the plan, across every surface you included, with its full contents
Read it once from top to bottom. It is the moment to notice a rule in the wrong file, or a surface you meant to leave out. The bar at the top counts the changes, the surfaces and the files to write.
Take the files or the script
Three ways to take the plan away:
| Button | What you get |
|---|---|
| Download the files | Every file in one zip, with a note saying where each goes |
| install.sh | A shell script that writes all of the files |
| Copy the script | The same script, on your clipboard |
The script is meant to be read before you run it. What it does:
- Copies anything already at one of its paths into a timestamped backup folder (by default in
~/.benibix-backups/), before touching it - Merges into JSON files instead of replacing them, so every key you did not set stays exactly as it was. For that it needs
python3, and it stops without writing anything if Python is missing - Writes an
undo.shinto that backup folder, and prints both as its last lines, so you can find them
To put things back, run bash ~/.benibix-backups/<time>/undo.sh with the folder it printed: it copies back every file that was there and removes every file the script created.
Save and share the plan
Save this plan downloads your choices as a JSON file. Load a plan reads one back in, replacing what you have set. Start over clears it all, including what this browser saved, after a second click. Use it to:
- Keep your setup, and rebuild it on a new machine in a minute
- Send a colleague your setup to review before they install it
- Keep variations, like one plan for personal projects and one for client work
Roll it out to a project
For a team, put the shared parts in the repository:
.claude/settings.jsonfor shared permissions and hooks./CLAUDE.mdfor the project's instructions.claude/agents/,.claude/skills/for shared agents and skills.mcp.jsonfor shared MCP servers
Memory (CLAUDE.md), Agents, Skills, Commands, Output styles and MCP servers have a project scope under Where it lives: choose it, and the plan writes those files into the repository (name its folder under Repository for the project files in Changes). Permissions, Settings and Hooks always write ~/.claude/settings.json, so for a shared .claude/settings.json copy their blocks from the preview into the repository's file. Everyone keeps their own ~/.claude for personal taste, and .claude/settings.local.json for their exceptions.
Enforce it for a company
Managed policy (administrators) writes the file an administrator deploys and users cannot override: /etc/claude-code/managed-settings.json on Linux, /Library/Application Support/ClaudeCode/managed-settings.json on macOS, C:\Program Files\ClaudeCode\managed-settings.json on Windows. It holds the keys a user cannot override, and the levers that stop a fleet.
Those levers are also in Try it under Turn it off, for the ten minutes when something is wrong and you want it stopped, not understood. You pick what to cut (every hook, MCP servers, tools, and more) and it writes the exact block, with what each one costs you. It belongs in the managed file, because a switch a user can undo is not a switch.
Keep the setup healthy
A setup ages. A few habits keep it right:
- After a Claude Code update, re-read your plan in the studio and check the badges of the settings you rely on
- Run What is actually set up here? on a repository you just cloned, to see what its
.claudebrings - When something is ignored, ask Which file is deciding this? before you change anything
That was the last lesson. You can now set up every surface Claude Code reads, test it, install it safely and share it. If something is missing or wrong, the Feedback button in the studio's bar goes straight to the issue tracker.