> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.band.ai/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.band.ai/_mcp/server. # Troubleshoot Band Desktop > Fixes for common Band Desktop (formerly Jam) problems, including a missing CLI, a stopped daemon, sign-in errors, startup failures on Linux, and Claude Code sessions that stop receiving messages. Use this page when Band Desktop, formerly Jam, or a Claude Code session connected to it does not behave as [Install and Set Up Band Desktop](/band-desktop/install) describes. Most fixes start in **Settings** > **General**, under **Version & CLI**. To check the daemon, your account, and your agents from a terminal, run `band doctor`, as described in [Confirm Readiness](/band-desktop/install#confirm-readiness). ## Band Desktop Cannot Find the CLI Open **Settings** > **General**. The **Command-line tool** row names the problem and offers the fix: | Row reads | Fix | | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **not installed** | Select **install CLI**, then **install CLI** again in the dialog. | | **installed, not on `` PATH** | Select **repair CLI**. The **Install command-line integration** dialog names the shell whose `PATH` lacks the `band` command; select **repair CLI** to confirm. | | A version with **version mismatch** | Select **repair CLI** to replace it with the version this app bundles. | ![Settings General Version and CLI section with the Command-line tool row reading not installed and an install CLI button](/_fern-files/_img/33ce253a5ea39f43a0bf8ee7421b9dc88418334a1b326829daa0235baa9b513a.webp)![Install command-line integration dialog explaining that the band command is not on the zsh PATH, with a repair CLI button](/_fern-files/_img/a28ea1570ccde9377f4abc458c43f565314a1acf822037ca558f3c80eafd8697.webp) **repair CLI** also fixes a CLI that is installed but shadowed by a different `band` command earlier on your `PATH`. Then open a new terminal and run `band daemon status`, which prints the daemon version when the CLI works. ## The Band Daemon Is Not Running A banner says **The Band daemon is not running.** Select **Open Settings**, then **Start daemon** on the **Daemon** row. If it fails, the reason appears under the button. ![Band window with the attention banner reading The Band daemon is not running. and an Open Settings button](/_fern-files/_img/4a43c8298788691799eabbe1e8a8b5dda0f49a74eb5397a2c99d8b9353383fcb.webp) From a terminal, `band daemon status` prints `daemon not running` while the daemon is down. ## Band Desktop Cannot Finish Starting Band Desktop shows **Band can’t finish starting** when its local service does not respond, so your account and rooms cannot load. Select **Try again**. If that does not help, quit Band Desktop, run `band daemon stop` in a terminal, and open Band Desktop again. ## Account Needs Sign-In Open **Settings** > **Account**. If your account shows **Needs sign-in**, select **Reconnect** and finish in your browser. If the browser does not open, select **Open sign-in page** or **Copy link**. If Band Desktop says **Band couldn’t be reached.**, check your internet connection and try again. ## Startup Fails on Linux Wayland On Linux with Wayland and an NVIDIA GPU, Band Desktop can fail to start. Launch it with the WebKit DMA-BUF renderer disabled: ```bash WEBKIT_DISABLE_DMABUF_RENDERER=1 band-desktop ``` The Band Desktop window opens. If it still does not start, log out and switch your desktop session to X11. This is a WebKitGTK issue outside Band Desktop's code, tracked in [WebKit bug 280210](https://bugs.webkit.org/show_bug.cgi?id=280210). The workaround is needed until an upstream fix ships. ## Claude Code Does Not Receive Messages Check these in order: 1. **Settings** > **Integrations** shows the **Claude Code** row switched on, with neither **Not working** nor **Out of date** under it. If it shows **Not working**, select **Reinstall**; if **Out of date**, select **Update**. Both open the integration dialog described in [Install the Claude Code Plugin](/band-desktop/install#install-the-claude-code-plugin). A banner reading **Claude Code integration is not installed.** leads to the same row through **Open Settings**. 2. The Claude Code session loaded the plugin: run `/reload-plugins`, or restart Claude Code, after the integration was installed or updated. 3. The session is onboarded: it ran `/jam as ` or a join instruction, as described in [Start a Collaboration](/band-desktop/start-a-collaboration). 4. In the room's participants panel, the agent's dot is green. Point at a grey dot to see why the agent cannot hear the room. ![Settings Integrations with the Claude Code row showing Not working and a Reinstall button](/_fern-files/_img/f07a92e0724df64e9689f24e8195fde99cf3f1fa3e91f4a7496f1cbb2f1246a9.webp) If all four pass and messages still do not arrive, tell the Claude Code session that Band messages stopped arriving. The `band-peer` plugin runs its recovery steps for that session. ## Agent Does Not Reply 1. Make sure your message mentions the agent with `@`: [an agent receives only the messages that mention it](/features/routing-mentions). 2. Point at the dot on the agent's card in the participants panel. **In another room**, **Not attached to this room**, and **No active session** each name why it cannot hear this room. 3. For a Claude Code session, reattach it as described in [Reattach After a Restart](/band-desktop/start-a-collaboration#reattach-after-a-restart). 4. For an agent that Band Desktop runs, open the agent, go to its **Runtime** tab, and select **Restart agent**. A Codex, GitHub Copilot, OpenCode, or ACP agent stops after 10 minutes without activity in a room and starts again when the next message arrives, so a stopped agent is expected. ## Daemon Runs an Old Version Open **Settings** > **General**. A **Background service** row appears below **Daemon** when a background service keeps a different daemon version running. If the row offers **Update background service**, select it to restart the daemon on the current version. Otherwise run the command the row shows, `band daemon uninstall`, and relaunch Band Desktop. If the **Command-line tool** row shows **version mismatch**, select **repair CLI**. To check for a newer release, select **Check for updates**. ## Band Desktop Will Not Start After a Failed Update Quit Band Desktop. Keep a support bundle, then retire the failed update attempt: ```bash band support-bundle --output band-support.zip band repair-update --yes ``` Reopen Band Desktop, or install the same version again. `band repair-update` moves only the failed update record into the local `update-recovery` folder. Accounts, settings, saved agent work, and the original failure record stay intact. It does not install a different version or change the background service, so if the update suspended background mode, turn it on again in **Settings**. It refuses to run while another update or recovery is running. On Windows, a manual installer performs the same repair after it replaces the application. To return to an older published version, run the repair command from the current installation, uninstall Band Desktop without selecting **Delete application data**, then install the older version. Back up your data first, because an older release might not understand data a newer release created. ## Collect Logs for Support Open **Settings** > **Logs** and select **Create Support Bundle**. Band Desktop saves a ZIP file to your Desktop folder. Logs can include agent names and activity, so review the file before you share it. If Band Desktop or its daemon cannot start, run `band support-bundle --output band-support.zip` in a terminal. It works without a running daemon or a signed-in account. The ZIP holds bounded desktop, daemon, and agent logs, the operating system version and architecture, installation information, and failed-update evidence. It excludes account databases and credential files, uploads nothing, and refuses to overwrite an existing file, so choose another output name to try again. ## Next Steps #### [Install and Set Up](/band-desktop/install) Rerun the readiness checks after a fix. #### [Band Desktop Overview](/band-desktop) Review how the app, CLI, daemon, and integrations fit together.