Skip to content
code-config.com

Claude Code

Code Config prepares supported toolkit configuration in a launch folder, then starts Claude Code with that configuration.

Install and sign in to Claude Code on this computer, connect Code Config, and choose a toolkit. Use coding-app accounts to select the sign-in for a managed launch.

In the Code Config app, choose your project, toolkit, Claude Code in a terminal, and account, then launch.

From a terminal in your project folder:

Terminal window
csc launch claude

This command uses the project or workspace default toolkit. It does not select whichever toolkit you last viewed in the web app. A launch syncs updates before starting Claude Code.

Confirm the project folder and selected toolkit. Find a skill or command from the toolkit in Claude Code and try it on a small task. Check MCP connection status separately; an app opening does not confirm every server is ready.

Read Action needed and Notes on this launch before relying on a tool. Plugins need installation through Claude Code; listing one in a toolkit does not activate it.

Content Delivery
Skills, agents, commands, output styles Written in Claude Code’s formats.
Rules and context files Combined into CLAUDE.md.
Toolkit settings and hook bundles Combined in the launch’s settings.json; hook scripts are placed beside it.
Supported MCP servers Registered for the launch using local credential access, without placing credential values in toolkit definitions.

Claude Code uses a .claude/skills/ tree. File locations describes launch folders and other files.

Workflows and marketplace entries are not written as Claude Code configuration. Plugins require Claude Code’s installation step. An MCP server with missing credentials needs local setup; other toolkit content can still be available.

Find and add tools.