Bring an existing setup

Bring over the tools you need without replacing your entire setup at once. Start with one project and a small toolkit, then compare it with the coding app you already use.

Before you start

Keep a backup of configuration you maintain yourself. Complete Get started, and check your coding-app guide for the files Code Config writes.

Choose what to bring over

1. List the skills, commands, agents, and MCP servers you rely on for this project.
2. For tools supplied by GitHub repositories, add those repositories, select the tools, and place them in a toolkit.
3. Review App Settings for settings supported by Claude Code and Codex. Not every option in an existing configuration has an equivalent toolkit setting.
4. Set up required credentials on this computer. A credential you already have does not reach a toolkit’s tool just because the names match.
5. Launch the project with the new toolkit explicitly selected and verify the tools one at a time.

Adding a repository does not import local, unpublished files. Use the CLI reference and your installed CLI’s help to check the local import commands available in that build. Review the proposed content before applying it; do not upload ordinary project files as a substitute for importing tools.

Reuse a coding-app sign-in

A coding-app account is separate from your code-config.com sign-in. For a Claude Code account already signed in on this computer:

csc account add --host claude --name personal --import-current

This copies the account’s existing sign-in into a Code Config account folder. It is not a complete import of every tool or setting. Coding-app accounts and models covers other account options.

What to check before switching

Check that the tools load, credentials work, and the model and permissions are appropriate. Read any conversion notes. Leave your previous setup available until the new launch works for your actual task.

For Cursor, setup writes selected toolkit files into the project and records the files it owns. Cursor Agent launch does not perform that setup. Review Cursor before running it against an existing project.

For Codex, toolkit settings are applied to a launch copy. User choices such as approvals can be carried back when the run ends; see Codex.

Next

Choose the project’s default toolkit after you have checked the new setup.