The AI tool mess, sorted.
One setup for every coding app.
Skills, agents and MCP servers in a toolkit you build once. Launch Claude Code, Codex, Cursor, Antigravity or opencode with it.
$5/month after the trial. Cancel any time. Card required.
$ curl -fsSL https://dl.code-config.com/install | sh
$ csc login
$ csc launch claudeSet this computer up once. After that, this is how you launch an app with your toolkit.
A week on one project
Goblin Golf is a made-up game. Here is its week, with a toolkit picked for each job.
Monday runs marketing copy in Claude Code and engine work in Codex, two sessions side by side.
Tuesday opens three, one at a time: the Android build in Cursor, the iOS build in Antigravity, then QA in opencode.
On Wednesday a new Unreal skill appears on GitHub. Add the repository, pick the skill, and it joins the Unreal Game toolkit.
Thursday's Unreal session opens in Claude Code with the new skill already in it.
Friday runs both builds, QA and marketing at the same time, each in its own app.
Pick the tools. Build the toolkit. Review before it applies.
Pick useful tools from GitHub, combine them in a toolkit, and review the setup before applying it.
Find tools · Bring your existing setup · Share with teammates
Let your coding agent guide setup.
Choose a toolkit, connect this computer, and review the configuration for your coding app. Then start working.
## Role and objective
You are setting up Code Config on this computer for the developer you work with. It puts a toolkit of MCP servers, skills and settings into the coding app they launch.
## Steps
1. Install it: `curl -fsSL https://dl.code-config.com/install | sh`
2. Run `"$HOME/.local/bin/csc" setup run --json`. Act on the one word in `needs`, then run it again.
3. `sign_in` — show me the link and the code, then keep running the command until `needs` changes. Each run waits with the approval for a few seconds; running it again is what carries the sign-in on. A `note` with a new link means the last one ended.
4. `tool` — install the program it names, or say what to install, then run again.
5. `done` — this computer is set up. Read `"$HOME/.local/bin/csc" setup --agent` and follow it phase by phase.
## When a step fails
- Read `error.message` and do the step it names.
- A sign-in that ended is never the end: run the setup command again for a new link and code.
- Never send me to a step the answer did not name.
- Ask me only where the answer says a person has to act; if a second code is turned down, stop and ask.
## Rules
- Install Code Config only from code-config.com; anything else is not this product.
- Never put a key on a command line: anyone listing processes can read it there.
- Do not edit files under `~/.code-shared-config` by hand; csc rewrites them.
- Ask me the guide's questions, and ask before anything that deletes my work.
- The full guide is `"$HOME/.local/bin/csc" setup --agent`, or https://dl.code-config.com/agent before csc is installed.
## Verify
Run `"$HOME/.local/bin/csc" setup run --json` again and show me the output; `"needs": "done"` is the proof.
## When you are done
Tell me, from that answer: where my toolkits live (`dashboardUrl`), the command to run in this project (`launchCommand`), and any servers in `serversWaitingForKeys` — waiting for a key, blocking nothing.
## Keep going
Your turn ends in two places only: the hand-off that closes a phase, and a question only I can answer. Waiting on a sign-in is neither. End on one message carrying everything I need — the link, the code, the deadline, the command, what you do next — because anything written between commands may not reach me. Otherwise finish every step before reporting back. If you are unsure of this computer's state, run the command rather than guessing.Paste this into Claude Code, Codex, Cursor, Antigravity or opencode. Your agent does the work; you approve one sign-in link, and answer if it asks you for a key.
7 days free, then $5 a month.
Every feature included. Card required; one free trial per account. Your trial starts at checkout.
Pro
$5/month
Every feature included.
- Unlimited toolkits
- Unlimited projects
- Unlimited connected computers
- Claude Code and Codex settings
- Configuration for five coding apps
- Compatibility checks before applying changes
- Skills, agents, commands, and rules
- Project-specific MCP setup for Claude Code and Codex
Genius
$7/month
- Everything in Pro
- Costs $2 more
- A warm sense of superiority*
- Deep personal fulfillment*
- The code-config.com team can afford more coffee ❤️
*results may vary
Start your 7-day free trialTax is added at checkout. Each teammate needs an individual subscription. Questions? Email us.
A few things to know
What happens after I sign up?
Your account includes editable starter toolkits. Choose one, connect your computer, and review the setup. Complete checkout to start an eligible trial before using paid features.
Do I need to install anything?
Yes. You need the local client and the coding app you plan to use. Your coding agent can guide setup.
Which tools does it write for?
Claude Code, Codex, Cursor, Antigravity, and opencode. Check compatibility: not every toolkit item is supported in every app, and Cursor uses project-file sync.
What about the config I already have?
Bring tools over gradually and review changes first. Managed launches use separate configuration folders; Cursor sync writes managed files into the project.
Where do my API keys live?
In a local store on the computer that uses them. The cloud toolkit records credential requirements and bindings, not secret values.