> ## Documentation Index
> Fetch the complete documentation index at: https://help.bottari.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

Find the message you see in the app, then follow the steps under it.

## Claude Code isn't ready

### **No subscription model is ready**

This banner sits above the composer when Claude Code can't run on this computer. The line under it says why:

* **Claude Code isn't installed on this device.** — press **Connect Claude**. Bottari installs Claude Code and then opens the Claude sign-in in your browser.
* **Claude Code on this device isn't signed in.** — press **Connect Claude** and finish the sign-in in your browser.
* **Claude Code on this device is too old. Update it to 2.1.306 or later.** — press **Update in Terminal**.

### **Claude's sign-in has expired on this device. Connect again to continue.**

Your Claude sign-in on this computer ran out. Press **Connect Claude** and sign in again in your browser. Your session continues where it stopped.

### **Claude's sign-in has expired on the runner device. It has to be renewed there — on that device, open Settings › Dev environment › This device in Bottari and sign in (or run `claude auth login` in a terminal).**

The session runs on someone else's computer, and Claude's sign-in has expired there. Only that person can fix it: on their computer, **Settings** › **Dev environment** › **This device**, then sign in to Claude again. Someone with full access can also **Take over** the session to run it on their own computer.

### **Claude hit its usage limit. Switch to another model to keep working, or come back after it resets.**

Your Claude subscription reached its usage limit. This is your Claude plan's limit, not Bottari's. Wait until it resets, switch the session to another model, or choose **Sign in with another account** to continue with another Claude account.

### **Claude Code stopped partway**

Claude Code stopped in the middle of an answer. Press **Resend** to try again. If it keeps happening, open **Details** on the message and check **Settings** › **Dev environment** › **This device**.

## The session is on hold

### **…’s device is offline, so this session is on hold**

The session runs on its assignee's computer, and that computer is offline. It continues when that computer comes back online. If you have full access, you can **Take over** the session and run it on your own computer.

If the session's repository is only on that computer, you see **Can't take it over yet** until its owner pushes the repository to GitHub.

### **… is offline, so this session is on hold**

The session runs on another computer of yours that is offline. Choose **Continue here** to run it on this computer.

## Limits

### **Your team reached its session limit, so new sessions can’t be started**

Your team is on the **Free** plan and has created as many sessions as it allows. See [Plan and limits](https://help.bottari.ai/en/11-account-and-settings.md#plan-and-limits).

### **Your team reached this month's Bottari AI usage cap. Your own Claude Code subscription still works.**

@Bottari in channels and pages used up your team's AI budget for this month. Sessions aren't affected — they run on your own Claude subscription.

## Claude's service

### **The model provider is having trouble (HTTP …). This usually clears on its own — resend in a moment.**

Claude's service is having trouble. It usually clears on its own; press **Resend** in a moment, or open **Check provider status**.

### **This model hit a rate limit (HTTP …). If it keeps failing, a plan or spend limit may be the cause — check your provider account.**

Your Claude account is sending too much at once, or your Claude plan's limit was reached. Wait a moment and resend.

## Claude in Chrome

### Browser extension is not connected

Claude says this when it can't find the Claude in Chrome extension for this computer's Claude Code. Claude Code finds the extension through the Claude account and organization it's signed in to, so the extension has to be signed in to the same ones — the same email in a different organization doesn't connect. The Claude desktop app can still use the extension when they differ, because it connects to Chrome directly.

1. Ask Claude in the session which account and organization this computer's Claude Code uses. It reads them for you. In a terminal on the computer that runs the session, `claude auth status --json` shows them too (`email` and `orgName`).
2. In Chrome, open the Claude side panel. If it's signed in to a different account or organization, log out there, log back in and choose that organization.
3. If the extension isn't installed, install it from [claude.ai/chrome](https://claude.ai/chrome) and sign in the same way.
4. Send your request again.

## Agent database

### The agent stopped on a to-do

If a to-do's card says the agent's device couldn't open its session several times, check that you have edit access to that session and that no other computer is running it, then turn the agent off and on again from the bar at the top of the database.

## Still stuck?

Send a note from **Send feedback** at the bottom of the sidebar.

<sub>Bottari manual 13 pages (#940)</sub>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.