Connect a project and choose defaults
Connect a project when you want it to open with the same toolkit every time, show up ready to pick in the Code Config app, or be opened from the web app.
For example: connect bakery-website and set its Default toolkit to Bakery site. Every session you start there now has copywriting and SEO tools, and you never pick by hand.
Before you start
Section titled “Before you start”Connect your computer, and have the project folder on it. Any folder works; it doesn’t need to be a Git repository.
Connect a folder in the Code Config app
Section titled “Connect a folder in the Code Config app”Why: this is the quickest way when the folder is already on the computer in front of you.
- Open Code Config and choose Add local project.
- Type the folder path, or choose Browse… and pick the folder.
- Choose Add. Nothing is saved until you do.
Got lots of projects? Choose Scan for projects during setup, or Settings → Sync projects later. Pick the parent folder, tick the projects you want, and confirm. Nothing is added until you confirm.
Connect a project from the web app
Section titled “Connect a project from the web app”Why: useful when you’re in the browser already, or when you want to connect a GitHub repository.
Open Projects → Map project and choose a GitHub repository or a local folder. For a local folder, choose the computer, then finish picking the folder in Code Config on that computer.
Each computer confirms its own folder. Connecting a repository in the web app doesn’t download it onto your computers.
Set the project’s default toolkit
Section titled “Set the project’s default toolkit”Why: so you don’t have to remember which toolkit belongs to which project.
Open the project in Projects and change Default toolkit. Every launch in that project uses it, unless you pick a different toolkit for one launch. Leave it unset to use your workspace default.
Toolkit selection order shows the full order a launch follows.
Connect and set the default from the terminal
Section titled “Connect and set the default from the terminal”In the project folder, run:
csc project set --toolkit <toolkit-id>Replace <toolkit-id> with the toolkit’s ID or its name, as csc toolkit get lists them. The command-line reference lists the commands.
To connect a different folder, add --path <path>. If a repository isn’t on this computer, clone it with Git first and connect the folder it creates.
csc project get --json shows a folder’s project and the toolkit a launch from it uses. csc project delete --json clears the folder’s default toolkit, so a launch from it goes back to the workspace default.
A project can also have its own account for each coding app. From the folder, csc project set --account <account> sets the account a launch from it opens in that account’s app, and csc project delete --host <claude|codex> clears that app’s account and keeps the toolkit. The account is kept on this computer only, and a launch uses it when the account mode is Project; Coding-app accounts and models explains the choice.
Check it worked
Section titled “Check it worked”- The project appears in Projects.
- The toolkit’s Usage tab lists the project.
- When you start a session, Code Config shows your toolkit with This project’s default toolkit as the reason.
Launch from the web app, or open the project from Code Config on your computer.