Get started
Start with an existing toolkit and use it in a project. Building a toolkit from scratch is optional.
Before you start
Section titled “Before you start”Have a project folder, an internet connection, and a coding app installed on the computer you will use. Check Downloads for an available Code Config build and Coding apps for your app’s setup method. Sign in to the coding app separately from your code-config.com account.
Sign in and choose a toolkit
Section titled “Sign in and choose a toolkit”Open the web app and sign in. Complete any account or billing step shown there; Billing and your plan explains the trial and subscription.
Open Toolkits and choose a starter toolkit that fits your work. Check its Contents and Configuration tabs. Note the name of one supported skill or command so you can check it after launch.
If none of them fit, use a Community toolkit or create your own.
Set up your computer
Section titled “Set up your computer”Choose one method. Each ends with this computer connected to your account.
- Install Code Config and open it on the computer you will use.
- Choose Connect this computer, then Sign in with browser.
- Check the code and approve the connection in your browser. Return to Code Config; it continues automatically.
Check: this computer appears under Settings → Computers in the web app. You can skip the project scan for this first launch.
Open your project in a coding agent that can run commands on this computer. Paste this prompt into the agent.
## 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.
Approve the sign-in link the agent gives you. Let it complete setup, then tell it the name of the toolkit you chose when you signed in. Ask it to select that toolkit for this project and confirm the selection. Setup may otherwise use a default.
Prefer an existing local credential or a private terminal prompt when a tool needs a key. A value pasted into agent chat is also part of that chat transcript.
Check: the agent reports setup finished and gives you a launch command. Keep that command for opening your project.
Install the CLI, open a new terminal, then run:
csc --versioncsc loginApprove the displayed code in your browser. On a server, use the remote sign-in instructions.
Check: the command confirms the connection, and the computer appears under Settings → Computers in the web app.
Open your project with that toolkit
Section titled “Open your project with that toolkit”Choose Start a session, select your project folder, select the toolkit you chose when you signed in, and choose your coding app and its account. Check the toolkit name before launching.
For Cursor, choose Cursor → Set up and open to write toolkit files into the project. See Cursor for the separate Cursor Agent workflow.
Confirm the agent selected the toolkit you requested. End the current coding session and run the launch command it provided from your project folder. Setup does not change an already running coding session.
Cursor users need project configuration setup before starting Cursor Agent. A Cursor Agent launch does not write toolkit files.
Open a terminal in your project folder. List your toolkits and find the ID beside the name you chose:
csc toolkit list --jsonReplace <toolkit-id> below with that ID. This connects the current folder and saves the toolkit as its default:
csc project set --toolkit <toolkit-id>Then open your coding app. For Claude Code:
csc launch claudeUse the coding-app guide for other apps and account setup. Without the project default above, a bare launch command could use a different toolkit. Connecting a folder is optional for local launches, but this step makes the example’s toolkit selection explicit.
Check your tools
Section titled “Check your tools”Confirm that the coding app opened the correct project. Find the skill or command you noted when you chose the toolkit, using the app’s tool interface, and try it on a small task. For an MCP server, check the server’s connection in the coding app before relying on it.
Read Action needed and Notes on this launch. An app can open while a tool still needs setup or is unsupported. Follow the named action; MCP setup and Troubleshooting cover common problems.
Find and add tools to customize your toolkit.