Understand toolkits
A toolkit is a reusable collection of tools you want to use together in a coding app. For example, several frontend projects can share one toolkit, while database work uses another.
The three things to distinguish
Section titled “The three things to distinguish”| Term | Meaning |
|---|---|
| Tool source | A repository containing tools you can choose from. |
| Toolkit | The tools and supported settings you have selected for a kind of work. |
| Project | The folder containing the work you will use those tools on. |
Adding a repository makes its tools available to your account. Adding a tool to a toolkit selects it for use. Neither action connects a project folder or writes configuration to a computer.
What a toolkit can contain
Section titled “What a toolkit can contain”Toolkits can hold skills, agents, commands, rules, context files, output styles, workflows, MCP servers, hook bundles, and plugins. They can also contain supported app settings for Claude Code and Codex.
Not every coding app can use every type of content. Check an item’s Works with result and the coding-app guide. A tool being in a toolkit does not guarantee that the selected coding app can use it or that its credentials are ready.
Choose or customize one
Section titled “Choose or customize one”Start with a starter toolkit, use a shared toolkit, or create your own. Use Tool Builder to find tools and add your selection to a toolkit.
You can choose any toolkit for a launch. Without an explicit choice, Code Config uses the project’s default, then the workspace default. Toolkit selection order explains where to change each choice.
When changes take effect
Section titled “When changes take effect”Editing a toolkit saves a new version. A computer gets updates during sync, including before a launch. Start a new launch to use the updated configuration; an already running coding app is not changed by editing the web app.