Get started

By the end of this page, your coding app opens in your project with a toolkit’s tools ready to use. You don’t need to build anything first: every account comes with two ready-made toolkits, Efficient Builder and Full Auto. Efficient Builder is your default, so you can launch with it and go.

For example, if you’re building a web app, pick a web app toolkit from Community toolkits. Your next Claude Code session starts with its tools already set up.

From sign-in to your first session

1. 1

   Pick a toolkit

   In the web app

   Start with a ready-made one, like Web apps.

   • shadcn/uiSkill
   • SupabaseMCP
   • PlaywrightMCP

2. 2

   Connect your computer

   In the Code Config app

   Sign in once and approve the code in your browser.

3. 3

   Start a session

   In your coding app

   Claude Code opens in your project with the toolkit's tools ready.

You do steps 1 and 2 once. After that, every session is step 3.

What you need first

• A project folder on the computer you’ll use.
• A coding app installed there, such as Claude Code. Sign in to it separately from your code-config.com account. Coding apps covers each one.
• Code Config available for that computer. Check Downloads.

Step 1: Pick a toolkit

Why: the toolkit decides which skills and MCP servers your coding app gets. A toolkit that fits the work gives the agent the right tools and nothing extra.

How: open the web app and sign in. Complete any account or billing step shown there; Billing and your plan explains the trial.

Open Toolkits and choose the one that fits your work: Efficient Builder and Full Auto are there from the start. Check the toolkit’s Contents tab and note one skill or command, so you can check it’s there after you launch.

If it doesn’t fit, use a Community toolkit or create your own. Understand toolkits explains how to choose.

Step 2: Connect your computer

Why: Code Config writes your toolkit into your coding app’s settings on your own computer, so that computer needs to be connected to your account. You do this once per computer.

How: choose one method. Each ends with this computer connected to your account.

Desktop app

1. Install Code Config and open it on the computer you will use.
2. Choose Connect this computer, then Sign in with browser.
3. 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.

Coding agent

Open your project in a coding agent that can run commands on this computer. Paste this prompt into the agent.

Read https://dl.code-config.com/agent and do what it says to set Code Config up here.

Copy

Paste this into the Claude app, Claude Code CLI, the Codex app, or Codex CLI. 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, then let it finish.

When a tool needs a key, the agent asks for it in a private way, such as a secure card or a hidden prompt. A key pasted into the chat becomes part of the chat.

Check: the agent signs you in, puts your toolkit in a folder it can use, and ends with a short message from Code Config about what is ready.

Command line

Install the CLI, open a new terminal, then run:

csc --version
csc login

Approve 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.

Step 3: Start a session with your toolkit

Why: this is the step you repeat every day. Picking the toolkit at launch is what puts its tools in front of the agent.

Desktop app

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.

Coding agent

The agent works with your toolkit in this same conversation, so there is nothing to launch. In a later conversation, the agent brings the toolkit’s latest files before it starts.

Command line

Open a terminal in your project folder. List your toolkits and find the ID beside the name you chose:

csc toolkit get --json

Replace <toolkit-id> below with that ID. This connects the current folder and makes that toolkit the folder’s default, so a launch from this folder uses it; your workspace default stays as it is:

csc project set --toolkit <toolkit-id>

Then open your coding app. For Claude Code:

csc launch --host claude

Use 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.

In a new terminal, Tab completes csc commands for you, toolkit names included.

Step 4: Check the tools loaded

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.

If Code Config shows a step still to take, or notes on the launch, read them. An app can open while a tool still needs setup or doesn’t work in that app. Follow the step it names; MCP setup and Troubleshooting cover common problems.

Next

Create and manage toolkits shows how to change your toolkit or make your own.