Create and manage toolkits

A toolkit only helps when it holds the tools you actually use for one kind of work. This page shows the quickest way to make one, how to pick tools that earn their place, and how to keep it tidy as your project grows.

New to toolkits? Read Understand toolkits first; it explains why smaller toolkits work better.

Create a toolkit in five steps

1. Open Tool Builder in the web app and search for a tool you want, such as Supabase or Copywriting.
2. Check Works with to make sure it supports your coding app, then select it. Keep searching; the Builder Tray holds everything you select.
3. Open the Builder Tray and choose Create toolkit from selection. Name the toolkit after the work, such as Plantpal: marketing.
4. Choose Review changes, check the setup notes, and confirm.
5. In the Code Config app, choose Use in this launch on your new toolkit and start a session. Ask the agent to use one of the tools to check it’s there.

Already have a toolkit? Choose Add to toolkits in step 3 instead, and pick where the tools go.

Start from a copy of your starter toolkit

Why: your starter toolkits are a good base. Copying one and changing the copy is often faster than starting empty.

How: on My toolkits, open the Efficient Builder row’s menu and choose Duplicate, then rename the copy. On its Contents tab, choose Remove from toolkit on anything this project doesn’t need.

For example, Plantpal: app could start as a copy of Efficient Builder, keep code review and test-first development, and drop the tools Plantpal doesn’t use.

Start from a community toolkit

Why: someone may already have built a good toolkit for the kind of app you’re making.

How: open Community toolkits, check a toolkit’s tools and which coding apps it works with, and choose Save a copy to make it your own starting point. Community toolkits explains when to choose Follow updates instead.

Choose tools that earn their place

• Add a tool when you need it. If you haven’t missed it yet, leave it out.
• Check Works with and Before you add. Works with lists the coding apps that can use the tool. Before you add tells you if it needs a key or a sign-in on your computer.
• Prefer one good tool over three similar ones. Two browser-testing MCP servers in one toolkit make the agent choose between them every time.

Change a toolkit later

Open the toolkit from My toolkits. Its tabs are where everything lives:

Tab	Use it to
Contents	See, add, and remove tools, and the toolkits this one includes. The chips under the heading count the tools of each kind; choose one to show only that kind, and choose it again to show every tool. A tool marked Setup required shows how to add its key in its details.
App Settings	Set supported Claude Code and Codex options. Anything you leave alone keeps the app’s own setting.
Status line	Build the line your coding app shows under the session. Every launch with this toolkit gets it.
Setup & compatibility	Choose the apps this toolkit works with under Compatible apps. An agent in an app you choose finds this toolkit when it asks Code Config for toolkits.
Sources	See which repositories the toolkit’s tools come from.
Usage	See which projects use it by default and which computers have it.
Settings	Change the toolkit’s name and description. A toolkit that follows a Community toolkit has Stop following here.

Share this toolkit, at the right of the tabs, gets a share link or shares the toolkit in Community. Share your toolkit explains both.

On My toolkits, each toolkit’s menu also has Rename, Duplicate, Set as workspace default, and Delete.

Changes apply the next time you launch. A coding app that’s already running keeps the tools it started with.

Build on another toolkit

Why: tools you want everywhere, such as GitHub and Context7, shouldn’t have to be added to every toolkit by hand.

How: on the toolkit’s Contents, choose Add toolkit and pick the toolkit to include. The included toolkit’s tools come along whenever you launch with this one. Contents shows each included toolkit as its own group, in the order a launch applies them, with Move up, Move down, and Remove on its heading. If two of them set the same thing, the one lower in the list wins, and this toolkit is always last.

From a terminal, --include adds an included toolkit to the end of the list, and --remove-include takes one out:

csc toolkit set --toolkit "Web apps" --include "Company base"

A toolkit that’s included somewhere can’t include toolkits of its own, so keep your base toolkit simple. Share common tools with a base toolkit shows the full setup.

Use a toolkit by default in a project

If one project almost always needs the same toolkit, make it that project’s Default toolkit so you don’t have to pick it each time. Connect a project and choose defaults shows how.

Add tools from your own GitHub repository

Why: maybe you’ve written your own skills, or you found a repository of tools that isn’t in Tool Builder yet. Adding the repository makes its tools available to pick, just like any other.

1. Open Tool Builder → Sources → Add repository.
2. Choose Use in this workspace, enter the repository’s GitHub address (such as https://github.com/owner/repository), and set Expected visibility to match it.
3. Choose Verify and add. Code Config checks access and looks for tools in the repository.
4. When you see Discovery complete, choose Open discovered tools in Builder, select the tools you want, and add them to a toolkit.

Adding a repository doesn’t put anything in a toolkit by itself; you still choose which tools to add. Share with everyone is different: it sends a public repository for review so everyone can find it, and it doesn’t add the repository for you.

Private repositories

Set Expected visibility to Private. When asked, approve the code-config.com GitHub App for that repository, then come back to finish. If your GitHub organization needs an owner to approve access, you’ll see GitHub approval requested. Your attempt is saved; come back and finish once they approve.

If no tools are found

Code Config looks for tool files, such as skills, agents, and MCP server definitions. A repository with only app code has no tools to add. If you see Access required, finish the GitHub approval and try again.

Check that your tools load

Saving a toolkit records your choice; the launch is where you see the tools in action.

1. On the toolkit’s Contents tab, confirm the tools are listed.
2. Open the details of each tool marked Setup required, such as an MCP server that needs a key; they show how to add the key. Set up MCP credentials walks through it. A missing key never stops a launch; the launch leaves that server out until its key is on your computer.
3. Start a new launch with the toolkit and ask the agent to use one of the tools.

Tip

A tool marked Limited for your coding app works with some changes; Unwritable means that app can’t use it. Compatibility and setup explains each result.

Limits and details

• The Builder Tray holds up to 100 tools and keeps your selection if you reload the page.
• One selection can go into up to 100 toolkits at once. Selections with MCP servers go into one toolkit at a time.
• Remove from My tools on a source removes the repository from your list. Tools from it that are already in a toolkit stay there.

Next

Connect a project and choose defaults.