Toolkit selection order
Use this page when a session opened with a toolkit you didn’t expect, or when you want to change which toolkit a project starts with.
The order Code Config checks
Section titled “The order Code Config checks”Code Config uses the first choice it finds, in this order:
| Order | Choice | Where to change it |
|---|---|---|
| 1 | The toolkit you picked for this launch | Tick Use in this launch on a toolkit in the Code Config app, or choose one in the Toolkit box when you launch from the web app. |
| 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, then Change default toolkit. |
A pick for one launch doesn’t change either default. Viewing or editing a toolkit in the web app doesn’t pick it for a launch from the command line.
See which toolkit a launch will use
Section titled “See which toolkit a launch will use”In the Code Config app, the toolkit row shows the toolkit’s name and what chose it, separated by a dot:
| What it says | What chose it | Change it by |
|---|---|---|
| picked for this launch | You did, for this launch only. | Picking another toolkit, or unticking Use in this launch. |
| This project’s default toolkit | The project’s default. | Changing the project’s Default toolkit. |
| workspace default | Nothing else was set, so the workspace default applies. | Changing the workspace default, or giving the project a default of its own. |
In the toolkit list, Default for this project marks the project’s default toolkit and Default marks the workspace default.
If the toolkit includes other toolkits, a second line lists them: Also using: followed by their names.
Change the workspace default
Section titled “Change the workspace default”The workspace default is what a launch uses when nobody picked a toolkit 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. Projects with their own default keep it, and a session that is already running keeps the toolkit it started with.
A launch in a folder that isn’t connected to your account still uses the workspace default.
When there’s no toolkit to use
Section titled “When there’s no toolkit to use”No toolkit yet. Create one to start launching. means the workspace has no toolkit to choose. Create one or use a community toolkit.
This toolkit isn’t on this computer yet. means this computer hasn’t received the toolkit. Sync this computer and try again, or pick another toolkit. You don’t need to replace the toolkit just because this computer is behind.
Other launch problems, such as a coding app that isn’t installed, are covered in Troubleshooting.