Everything so far happened in your browser. This lesson starts a setup from a pack or from the one you have, checks every file it writes, puts it on your disk without losing what is already there, and hands the same setup to a colleague or a repository.
Start from a pack
Open Config Studio for Codex and press Starter packs above the editor. Each pack fills the same fields you would fill by hand, so everything it sets can be changed afterwards:
- Seatbelts: Codex asks before it leaves the sandbox, and a few commands are never run.
- Look, do not touch: a profile for reading and reviewing a codebase that cannot change it.
- Unattended in CI: a
ciprofile forcodex exec --profile ci, with no prompts, the workspace only and no web. - Only the hosts you name: commands reach the network, but only listed domains, and never your
.envfiles. - A footer worth reading: the status line with the model, the context left, your limits and the branch.
- A team repository: instructions, project config and test rules committed with the code.
Pick You work in first (JavaScript, Python, Go or Rust) and the packs that run tests use your language's commands. Press a pack to see what it sets, in plain words, then press Fill it in. The surfaces it filled are ticked in the list.
Or start from the setup you have
Already have a config.toml? Press Read in a setup instead, and drop your .codex folder, a repository or any of their files on the box, or choose them. Tick These are from my home folder for files from ~/.codex or ~/.agents, so they are read as yours rather than the project's. No folder picker in your browser? Or paste it gives you a command that only reads and prints; run it and paste what it prints.
What you have set opens in the editors: the model, the sandbox, MCP servers, the status line and the rest of config.toml, plus hooks.json, AGENTS.md, your .rules file, custom agents, profiles and skills. Below the box, each file says which surface it opened and what it kept as it is, such as a second MCP server or your trusted projects. Those stay in your files: the install script merges into them. An AGENTS.md or rules file you read in is written back in place of the file, so installing never writes your instructions twice, and a pack you add afterwards adds its lines to them.
Review every file
Open Changes. On the left, every key you moved, with what it was and what you made it; edit goes back to it and reset undoes it. On the right, What it writes: every file in the plan with its full contents, each config.toml once with every surface's keys merged.
The bar at the top counts the changes, the surfaces and the files, and says how many files would be written over. Read it once from top to bottom: it is the moment to see a rule in the wrong file.
Run the install script
Three ways to take it:
| Button | What you get |
|---|---|
| Download the files | Every file, with a note saying where each goes |
| install.sh | One script that writes them all |
| Copy the script | The same script, on your clipboard |
The script sets your old files aside first, then merges into the config.toml you already have, keeping your trusted projects and every key you did not set. It needs Python 3.11 or later and stops without writing anything if it is missing. Read it before you run it; that is what it is for.
At the end it prints the folder with your old files and the undo.sh in it: run that and every file is back as it was, and every file the script created is gone. Commands you built for later, such as codex --profile review or a codex exec run, are printed for you to run when you want them; the script never starts Codex itself.
Save and share the plan
Save this plan downloads your choices as a file. Load a plan reads one back in. Start over clears everything you set and everything this browser saved, after a second click. Use it to rebuild your setup on a new machine, to send a colleague your setup to review before they install it, or to keep one plan for personal work and one for a client.
For a team, pick project in each surface's first control, so the plan writes .codex/config.toml, .codex/rules/, .codex/hooks.json, AGENTS.md and .agents/skills/ in the repository. Commit them; each person trusts the project once and keeps their own ~/.codex for personal taste.
That was the last lesson. You can now set every surface Codex reads, know which one wins, test your rules and install the whole setup safely. If something is missing or wrong, the Feedback button in the studio's bar goes straight to the issue tracker.