The Code Config app

You build toolkits in the web app, but your coding app runs on your computer. The Code Config app connects the two. When you start a session, it fetches the toolkit you picked, sets it up the way your coding app expects, and opens the app in your project.

For example, you add the Figma MCP server to Plantpal: marketing in the browser. The next time you start a marketing session on your laptop, Code Config brings the change down and Claude Code opens with Figma ready.

Choose the desktop app or the terminal

Why it matters: both do the same job, so pick whichever fits how you work.

• The Code Config app gives you a launcher window, a list of your running sessions, and settings for this computer. Most people start here.
• csc does the same from the command line. Use it on a server or anywhere you don’t want a window.

Both share the same computer connection and the same toolkits. Installing the software and connecting the computer to your account are two separate steps.

Start a session

In Code Config, choose Start a session, then pick your project, toolkit, coding app, and account. Check the toolkit name before you launch.

A session is one run of a coding app that Code Config started for you. Code Config lists your sessions so you can find and return to them.

Get started walks through a complete first launch.

How toolkit changes reach your computer

Why it matters: edits you make in the web app only reach a coding app when it starts.

Every launch checks for toolkit updates before it opens the coding app. To pull changes without launching, run:

csc sync

Only what changed is downloaded. A session that is already running keeps the tools it started with, so start a new one to use your edits. An app opening doesn’t prove every tool is ready; sync and launch results tell you about any problems.

What stays on your computer

Your account holds your toolkits, the repositories you take tools from, your projects, and your connected computers. That’s the part you edit in the browser and share with your workspace.

Your keys and the location of each project folder stay on the computer that has them. They are never part of a toolkit, so a toolkit doesn’t carry them to another computer.

Privacy and analytics covers your analytics choice and what a configuration export contains.

Add another computer

Install and connect Code Config on that computer too. Then choose its project folder, coding-app account, and any keys its toolkits need. Connecting a second computer doesn’t copy projects or keys from the first one.

The web app’s computer list shows whether each computer is online right now and whether its Code Config is up to date. A connected computer can be asleep; that’s normal.

Next

Manage your computers.