Troubleshooting
Diagnose the common account, source-control, workspace, and billing problems without widening access unsafely.
I cannot sign in
Return to /login and complete the browser flow again. If the browser opened the wrong account, sign out of the browser session first. Do not copy session data into a command or support ticket.
A private repository is missing
Confirm the account, organization, repository owner, and invitation status. A private repository may be correctly hidden when your session lacks access. Ask an organization administrator to verify membership and team access.
Clone fails
Copy a fresh command from the repository’s Clone menu, then authenticate the selected client. Check that the transport matches the credential you configured and that the repository path uses the correct owner.
The stack review is empty
A stack review needs a real base and comparison ref with changed commits. Return to New stack review, select the refs again, and inspect the comparison preview before submitting.
The workspace is blocked
Read the workspace status and linked issue first. Common causes include missing permissions, a source conflict, an expired lease, unavailable execution capacity, or a failed validation. Preserve the workspace while you capture the error; manual directory deletion can destroy the evidence needed to recover.
Usage or billing is unavailable
Billing and usage access can be restricted by account or organization policy. If the page says access is not enabled, ask an administrator to provision it. If a payment or invoice is stale, use the hosted invoice link and wait for the account view to refresh before retrying a second payment action.
The CLI cannot authenticate
Run ncode auth login again from the packaged binary, or use /login inside the REPL. For automation, check that the intended API key is present, unexpired, and scoped for the operation. Never solve an auth error by disabling verification or putting a key in a repository file.
What to include in a support report
Include the public URL, account or organization name, repository and issue identifiers, client name and version, timestamp, exact error text, and the smallest reproducible command. Remove access tokens, cookies, private source, and internal hostnames.