Troubleshooting
Find the message or behavior you see, then apply the fix. Quoted text is what Kosuke shows on screen. Each fix links to the page that covers the feature. If nothing here matches, get help.
Sign-in and setup
| What you see | Cause | Fix |
|---|---|---|
| "That code has expired" or "Too many attempts on that code" | A sign-in code lasts 5 minutes and allows a limited number of tries. | Press Resend code and type the new code. |
| No Promo code field on the Welcome to Kosuke screen | Free credits are claimed once per person, and you already claimed yours. | Create the workspace without it. See Plans and billing. |
| "Connect your workspace AI provider" stays unticked after you connect your own Subscription | The checklist counts only the workspace's Credentials. | An owner or admin connects Anthropic, OpenAI, Z.ai or Moonshot AI in Settings > Workspace > AI Providers. See AI providers. |
| "Authentication Not Configured" banner | The workspace has no usable Credentials. Your own Subscription does not clear this banner. | An owner or admin connects a provider in Settings > Workspace > AI Providers. See AI providers. |
| Settings > Workspace > AI Providers reads "Managed by workspace admins." | Only owners and admins can change workspace Credentials. | Ask an owner or admin. See Members and roles. |
Import
| What you see | Cause | Fix |
|---|---|---|
| The Import Project dialog reads "Connect your repositories" | You have no GitHub Connection yet. | Press Install on GitHub, pick your repositories and authorize Kosuke. If your GitHub organization already has the app, press Connect GitHub under it. See Import a repository. |
| The Import Project dialog reads "Waiting for your org admin" | You asked a GitHub organization owner to install the Kosuke App. | Press Check again once they approve. If the dialog asks you to connect instead, press Connect GitHub. |
| The Import Project dialog reads "Reconnect GitHub to continue" | GitHub no longer accepts your connection. | Press Reconnect GitHub. You can also reconnect in Settings > Your Account > Account. |
| Your repository is greyed out with Install App beside it | The Kosuke App is not installed on that repository. | Click Install App and add the repository on GitHub. GitHub sends you back to the dialog. See Import a repository. |
| Your repository is missing from the list | Your GitHub account cannot reach it. A repository the App does not cover still shows, greyed out. | Check your access on GitHub. |
Deploy
| What you see | Cause | Fix |
|---|---|---|
| "GLM does not run the deploy agent yet" or "Kimi does not run the deploy agent yet" in the Deploy Chat | The workspace has only Z.ai or Moonshot AI Credentials. Deploys run on Anthropic or OpenAI. | An admin connects Anthropic or OpenAI in Settings > Workspace > AI Providers. See Deploy your project. |
| "The deploy model needs usable workspace credentials" | The deploy model's provider has no working workspace Credentials. | An admin connects or reconnects Anthropic or OpenAI, or you pick another deploy model in the Deploy Chat header. See Deploy your project. |
| A warning triangle beside the project in the sidebar, and "Answer the deploy agent..." | The deploy agent asked a Clarification and is waiting. | Answer it in the Deploy Chat. |
| "Deploy failed" in the Deploy Chat, or a red circle beside the project | The deploy could not bring your app up. | Open the Logs tab to see why. Tell the deploy agent what to fix, or press Retry Deploy. See Deploy your project. |
| The settings tabs cannot be edited before the first deploy | The deploy agent writes the first configuration. | Press Edit manually. See Project settings. |
| "Press Redeploy to rebuild the deployment..." in the Deploy Chat | The project's main sandbox is gone. | Press Redeploy. |
| "Project setup not complete" when you start a session | Sessions start only after the project's first successful deploy. | Deploy the project. See Deploy your project. |
Chat sessions
| What you see | Cause | Fix |
|---|---|---|
| No Steer now arrow on your waiting message | The running turn belongs to another member. | Wait. Your message starts the next turn. See Messages, Up next and steering. |
| Messages in Up next stop going out on their own | The last turn was stopped, failed or ended on a Clarification, or the session moved to Under Review. | Send a message, or press Send now on one of your waiting messages. Up next carries on after that turn. See Messages, Up next and steering. |
| "Chat failed" | The turn ended with an error. | Press Try Again. |
| A notice that your Subscription needs reconnecting | The login behind your Subscription expired. | Press Reconnect in AI Providers and sign in again. See AI providers. |
| A notice that another member's Subscription needs reconnecting | The session's Assignee must sign in to their Subscription again. | Ask them to reconnect it, or reassign the session. See Chat sessions and the board. |
| "Connect a Subscription or workspace provider to start chatting" | The session's Assignee has no Provider Access in this workspace. With no Assignee, that means you. | Connect a Subscription, ask an admin to connect the workspace, or reassign the session. See AI providers. |
Preview
| What you see | Cause | Fix |
|---|---|---|
| "Preview paused" | The session's sandbox is paused, because it sat idle or someone stopped it. | Press Start preview, or send a message. See Preview and sandboxes. |
| A "Still there?" card with a countdown | The preview has been quiet for ten minutes and is about to pause. | Press Keep it running. |
| The Sandbox Limit Reached dialog | The workspace runs as many sandboxes at once as its plan allows. | Tick sessions to stop, then press Stop N Sessions & Create New (or & Start, & Restart). See Preview and sandboxes and Plans and billing. |
| "Deployment failed" in the Preview | The project's deploy failed. | Open the project's Settings view, read the Logs tab, and redeploy. See Deploy your project. |
| "Session not started" in the Preview | The session is still in the Backlog. | Start the session. See Chat sessions and the board. |
| No Changes or Files tab on your phone | A phone shows one view at a time: Chat, Preview or Artifacts. Changes and Files need a wider screen. | Open the session on a wider screen. See Desktop app and mobile. |
Pull requests
| What you see | Cause | Fix |
|---|---|---|
| Commit or Push where Open PR should be | Some changes are only in the sandbox. This is normal when the Commits preference is Manual. | Press Commit or Push, then Open PR. See Your account and preferences. |
| No Open PR button at all | The branch has no changes yet. | Ask the agent for a change first. |
| "Branch behind" in the chat header | The Target Branch has moved on. | Press Sync. See Sync with the Target Branch. |
| "PR has conflicts" in the chat header | The branch and the Target Branch changed the same lines. | Press Sync. The agent resolves the conflicts and asks you when one has no clear answer. See Sync with the Target Branch. |
Billing
Owners and admins manage the plan and spend settings in Settings > Workspace > Billing.
| What you see | Cause | Fix |
|---|---|---|
| "Running low on free credits." or "Running low on included usage." | The workspace is close to its limit. | Press See plans or Allow overage. See Plans and billing. |
| "Free credits used up" | The Trial's free credits are spent. | Press See plans and subscribe. |
| "No free credits on this workspace" | Free credits are granted once per person, and whoever created this workspace already claimed theirs. | Press See plans and subscribe. |
| "Included usage spent" | The plan's included usage for this period is spent. | Press Allow overage, or wait until the allowance resets. |
| "Spend limit reached" | The workspace reached the monthly spend limit it set. | Press Raise limit, or wait until the allowance resets. |
| "Payment failed" | The last payment did not go through. | Press Manage billing and update the payment method. |
| "Subscription ended" | The workspace's paid plan was cancelled. | Press See plans and subscribe again. |