Toolkit selection order
Code Config uses the first available choice in this order:
| Priority | Choice | Where to change it |
|---|---|---|
| 1 | The toolkit selected for this launch | Which toolkit? in the Code Config app, or the toolkit picker in web launch options. |
| 2 | The project’s default toolkit | Open the project in Projects and change Default toolkit. |
| 3 | The workspace default | Settings → Workspace in the web app. |
A one-time choice does not change either default. Viewing or editing a toolkit in the web app does not select it for a local CLI launch.
Choose the workspace default
Section titled “Choose the workspace default”The workspace default is what a launch falls back to when nobody chose a toolkit for this launch and the project has no default of its own. Open Settings → Workspace in the web app and choose Change default toolkit.
The new default applies to later launches across the workspace. Each project keeps its own default, and a coding session that is already running keeps the toolkit it started with.
Read the selected toolkit
Section titled “Read the selected toolkit”The Code Config app displays:
Using: <toolkit> · <source>The source is this launch only, project default, or workspace default. Change the choice at that source, or select a different toolkit for this launch.
A local launch in a folder that is not connected to your account can still use the workspace default.
When the toolkit is unavailable
Section titled “When the toolkit is unavailable”No toolkit yet. Create one to start launching. means the account has no toolkit to choose. Create one or use a Community toolkit.
This toolkit isn’t on this computer yet. means this computer has not received the selected toolkit. Sync this computer and retry. Do not replace the toolkit just because this computer is behind.
These are toolkit-selection problems. Other launch failures, such as a missing coding app, are covered in Troubleshooting.