Troubleshooting

Find the message or code you received below. Check both whether the coding app opened and whether the tool you need is ready; those are different outcomes.

If nothing here resolves it, Contact support at the end of this page lists what to send.

Signing in and connecting a computer

What you see	What to do
Sign-in was denied.	Start again and approve the matching code in the browser.
That code expired. Start again to get a new one.	Start a new connection attempt and approve its new code.
This sign-in is no longer valid. Start again.	The attempt ended before completion. Start again.
This computer is already connected to a workspace.	No new connection is needed. To change workspaces, sign out on that computer first.
Couldn’t reach code-config.com — check your connection.	Check the computer’s internet connection and try again.
The server refused this sign-in. Try again in a moment.	Retry; contact support if the refusal continues.
Sign-in was approved but this computer’s connection wasn’t saved. Try again.	Retry on that computer; approval alone did not finish setup.
The sign-in stopped unexpectedly. Try again.	Start another attempt.
This build can’t reach the network.	Install a supported build from Downloads.
Not reported under a computer’s presence	Nothing has answered for that computer recently. Open the Code Config app there, or run csc listen on a computer with no screen, then read the row again.

This computer couldn’t finish connecting: is followed by the local reason. Use that reason when asking support for help.

Presence and Last sync answer different questions. A quiet computer can still hold the current toolkit, and a computer that answered a moment ago can still be waiting for changes. Read both columns before you reconnect anything.

Connect your computer explains browser approval and remote sign-in.

Nothing to launch with

What you see	What it means	What to do
No toolkit yet. Create one to start launching.	The workspace has no toolkit to select.	Create or adopt a toolkit, then choose it.
This toolkit isn’t on this computer yet.	The selected toolkit has not reached this computer.	Run csc sync, then try again.
This workspace has no toolkits. The project is still mapped; launching remains unavailable until one exists.	The project connection exists, but there is no toolkit.	Create or adopt a toolkit. You do not need to reconnect the project.

For an unexpected toolkit, check Toolkit selection order.

The app would not start

What you see	What to do
Not installed on this computer.	Install the coding app on the selected computer, then retry.
This app is not available on this system.	Choose a supported app or supported form of that app.
This launch target has no compatible adapter.	Choose another supported launch target.
Couldn’t be started on this computer.	Retry once; if it repeats, send support the message and client version.

For web request states such as Not picked up or Launch status unknown, use Launch from the web app. Check an existing request before sending another.

What a launch reports

Action needed means the coding app needs your approval before some content takes effect. Notes on this launch describes other issues, such as an unsupported tool, a conversion limit, missing content, or a server needing setup.

Neither heading alone tells you whether the whole toolkit is usable. Read the affected item and reason, then check the tool in the coding app. An empty diagnostics array means Code Config reported no diagnostics, not that every external service has been tested.

With JSON output, launch diagnostics are in the diagnostics array. Use the app’s launch command with --json; the command-line reference explains where to find its exact syntax.

Add --strict and the launch command exits with a non-zero code whenever the configuration is not fully in place, and names each thing you still need to do. Six codes never make it fail, because each one describes a result you can use: item_placed_with_losses, item_replaced_by_same_name, host_requires_user_action, mcp_server_in_session, launch_notes_not_recorded, and sign_in_first. Every other code below does.

Launch codes

Code	What it means	What to do
toolkit_manifest_not_cached	The toolkit content was not available in this computer’s cache.	Sync, then launch again.
host_has_no_materialized_row	No prepared toolkit content was available for the coding app.	Check app compatibility, sync, then retry.
toolkit_receipt_write_failed	Code Config could not save its record of the files written.	Check home-folder permissions, then retry.
launch_notes_not_recorded	Everything this launch set up is in place; Code Config could not save its own notes about it.	Nothing to do. Check home-folder permissions if it keeps happening.
item_content_unavailable	Repository content could not be fetched.	Check network and source access, then retry.
item_content_plan_rejected	The proposed files were rejected before writing.	Review the named toolkit items and reason.
item_content_write_failed	Writing repository content did not complete.	Check disk space and folder permissions. Not all tools were installed.
cursor_project_destination_unavailable	Cursor setup has no local project folder.	Select the project folder in the Code Config app and run setup there.
cursor_project_config_sync_failed	Cursor’s project configuration was not updated successfully.	Check folder permissions and run setup again.
item_not_placed	The coding app cannot use one named item.	Read that item’s compatibility result; choose another app if needed.
item_placed_with_losses	A conversion omitted unsupported details.	Read the named loss before relying on the converted tool.
item_replaced_by_same_name	Two tools in your toolkit have the same name, so the launch used the one later in your toolkit and left the other out.	Nothing to do. To use the other one, take the kept one out of your toolkit.
item_moved_or_renamed	Code Config could not get one of your tools from where it comes from, so the launch was set up without it.	Set that tool up in this project by hand, or take it out of your toolkit.
app_data_not_fully_seeded	Some of your saved app data could not be copied into this session.	The app may ask you to sign in again. Sign in there and carry on.
toolkit_env_setup_required	The app started without one of your toolkit’s settings.	Run the setup command in the result, then launch again.
csc_executable_missing	The CLI could not be found for MCP setup.	Install the CLI and retry.
mcp_server_not_in_session	A server in your toolkit was not set up in the coding app: it is not set up to start yet, its name cannot be used, its name is already taken by another server, or the CLI could not be found.	Follow the named reason: finish setting that server up, rename it, or install the CLI.
mcp_server_in_session	A server your toolkit carries is set up in the coding app.	Nothing to do.
mcp_setup_required	A server still needs local setup.	Run the exact setup command in the result, then check the server.
host_requires_user_action	The coding app needs your approval for delivered content.	Review and answer its prompt in the coding app.

When a launch cannot report on itself

runtimeReporting is included when launch reporting is degraded. This is separate from toolkit delivery and the coding app’s state.

Code	Meaning and next action
lock_unavailable	Another process holds the reporting lock. Let that operation finish.
journal_unavailable	The local reporting record could not be opened. Check permissions on Code Config’s local files.
delivery_pending	A report is queued locally. Check connectivity if it remains pending.
worker_unavailable	The reporting worker is not running. A later launch retries reporting; contact support if it persists.

An MCP server is not ready

Copy the exact setup command from the launch result or the toolkit’s Configuration → Tools needing setup row. The command identifies the toolkit and server for you.

Reason	What to check
binding-missing	The credential has not been set up on this computer.
binding-invalid	The saved credential could not be read.
policy-mismatch	The saved binding does not match the toolkit’s current requirements. Sync and review setup.
local-state-unavailable	Local credential state is unavailable. Check local permissions and setup.
provider-unavailable	The credential store is unavailable. Restore access to it.
provider-interaction-required	Unlock or approve access to the credential store.
executable-unverified	The server program could not be verified. Follow setup’s named prerequisite.

Run the provided setup command after resolving the named prerequisite. An unlock prompt or permission decision still needs your action; repeating setup is not a substitute for that action.

When the coding app starts the server

The coding app starts each MCP server itself, from the configuration the launch wrote for it, so a server that fails after the app has opened reports the failure in the app rather than in the launch result. A service that rejects the credential and a server program that is not installed both show up there.

Run csc mcp status –toolkit <toolkit-id> on that computer and use the reason in the table above. If setup reports the server ready and the coding app still cannot start it, run the toolkit’s setup command with the corrected credential and launch again. The new value reaches the coding app with the next launch.

csc mcp setup refusals

Reason	Meaning and next action
profile-not-id	Setup needs a toolkit ID, not a name. Copy the command from the toolkit’s Configuration tab.
policy-mismatch	This computer’s toolkit data is behind. Run csc sync.
policy-not-provisioned	No setup requirements are available for this computer. Sync and check the toolkit configuration.
requirement-not-declared	The toolkit does not declare the requested credential. Check its server configuration.
unknown-server	That server name or ID is not in this toolkit. Run csc mcp status to see the toolkit’s servers.
unknown-application	That coding app is not configured in this toolkit. Check the app selection.
provider-unavailable	The selected store cannot be used right now. Restore access and retry.
provider-interaction-required	Run setup in a terminal where you can answer its prompt or unlock the store.
invalid-locator	The supplied credential location is invalid. Correct the binding.
provider-not-found	No store is registered under that name. Check the available stores.
binding-missing	No matching binding exists to check or remove. Set it up first if needed.
secret-name-ambiguous	More than one binding matches. Specify the toolkit and scope.
key-file-unreadable	The supplied file could not be read. Check its path and permissions.
key-file-empty	The file you pointed at holds no value. Point the command at the file that holds the key.

Set up MCP credentials explains supported inputs, scopes, and storage.

Exit codes

Management commands use these outcomes for scripts and JSON output. Other command families also have their own help; check both their exit status and returned details.

Exit	Kind	Meaning and next action
0	—	The command succeeded. Read any item-level diagnostics as well.
1	internal_error	Retry; contact support if it persists.
2	invalid_request	Check the command’s arguments and options.
3	not_authorized	Check the account, computer connection, and required permissions.
4	conflict	The object exists or changed. Refresh its state before retrying a write.
5	action_required	Complete the action named in the response.
6	temporarily_unavailable	Check connectivity and retry later.
10	upgrade_required	Install a current supported build.

Contact support

Email hello@code-config.com when the steps above do not get you moving again. Include:

• what you were trying to do, and what happened instead;
• the coding app and the Code Config version you are on;
• the exact message or code you saw, copied rather than described;
• whether the coding app opened at all, and the name of the computer you were on.

Leave key and token values out of the message; nobody needs them to read the error with you. Help & Feedback in the web app has the same email button, next to prompts you can paste into your coding agent.