Use a shared toolkit

Use a shared toolkit to start from someone else’s tools. Saving it to your account and using it in a coding app are separate steps.

Find and save a toolkit

1. Open Community → Toolkits in the web app, or open the share link you received. Public toolkit pages can be previewed without signing in.
2. Review the description, contents, source repositories, coding-app compatibility, and publisher. In Community, filter by use case, app, or content type.
3. Choose Use or Use this toolkit. Sign in when prompted; the selected listing is retained through sign-in.
4. Choose Follow updates or Save a copy, then confirm.
5. Open Toolkits and find your newly added toolkit.

Follow updates notifies you about future published versions. Save a copy creates an independent copy with no update relationship. Both produce your own editable toolkit, and neither updates it automatically later.

Use it in your project

Check the new toolkit’s Configuration tab for compatibility and setup needs. Connect your computer if it is not connected.

In the Code Config app, choose your project and explicitly select the new toolkit before launching. To make it the usual choice, set the project’s default toolkit.

Adding the toolkit does not automatically change a project’s default or a coding app that is already open. For Cursor, use Set up and open to write supported tools into the project.

Check it worked

Confirm the toolkit is in your account, then find and try one of its tools in a new launch. Review the setup and conversion notes; a tool listed in the toolkit may not have loaded.

Take a newer version

A followed toolkit can show Community update available. Open its source listing and use the newer version to create a new toolkit. Your earlier toolkit, including your edits, remains unchanged.

Compare and test the new toolkit. Change your project’s default only when you are ready to use it. There is no automatic merge of your edits with the publisher’s changes.

If the source disappears

A withdrawn, reviewed, or blocked listing can stop being available for new use. Existing saved toolkits are not deleted; followed toolkits report the source status. A copy does not depend on an ongoing update relationship.

The interface has no license-selection step. Review the source repositories and the Terms; the missing selector says nothing about a source’s own use requirements.

Next

Find and add tools to customize your copy.