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

# Performance & speed tips

> Option A — Workspace won't finish loading.

## Symptoms

* You see **We're having trouble getting your workspace ready. Check your connection and try again.**
* A chat takes a long time or shows **\{count} chats processing…**
* A banner reads **Reconnecting…** during a response.
* The app feels generally sluggish.

## Likely causes

* A [slow or unstable internet connection](/help/chatting-with-chief/working-offline-draft-preservation).
* A [long, multi-step request](/help/answer-depth-chiefs-agents/deep-intelligence-research-mode) that genuinely takes time to compute.
* Many things running at once (several chats processing in the background).
* A stale browser tab or a connectivity drop mid-session.

## Solution

<Frame>
  <img src="https://mintcdn.com/chief-2d405d1a/ZjT7ckngTj8rjHF7/images/help/chat-stop-generating.png?fit=max&auto=format&n=ZjT7ckngTj8rjHF7&q=85&s=0013ec85ee01fe187100316e4dffff23" alt="Chief troubleshooting - Stop Generating to halt a slow answer and re-send" width="760" height="240" data-path="images/help/chat-stop-generating.png" />
</Frame>

**Option A — Workspace won't finish loading.**

1. Check your internet connection — the message itself points here: "Check your connection and try again."
2. Refresh the page. If it still hangs, close the tab and re-open Chief in a fresh tab.

**Option B — A single chat is slow.**

1. Long, complex prompts take longer. You can [safely leave the page while Chief works](/help/chatting-with-chief/running-chats-in-the-background-browser-notifications) — it shows "You can safely leave this page while I work." Click **Notify me** to get a notification when it finishes.
2. If an answer is clearly stuck, click [**Stop Generating**](/help/chatting-with-chief/regenerating-or-stopping-a-response) and re-send a simpler, more focused prompt.
3. [Narrow your chat scope](/help/the-prompt-bar-scope/setting-the-scope-of-a-chat-using-files-labels-collections-concepts) to the specific Files you need rather than your whole Project so Chief has less to sift through.

**Option C — Everything feels slow.**

1. If you see the **Reconnecting…** banner, wait for your connection to recover — submissions pause and your draft is saved.
2. Let background work finish — when several "chats processing…" are running, new requests share resources.
3. Close unused tabs and use a normal (non-private) window on a secure (https) connection for the most reliable streaming and notifications.

<Tip>
  💡 **Pro-Tip:** For a big job, send your prompt, click **Notify me**, and step away — Chief keeps working in the background and pings you when the answer is ready.
</Tip>

## Still stuck?

If Chief is consistently slow on a good connection, email **[support@chief.bot](mailto:support@chief.bot)** with roughly when it happens and what you were doing.

## FAQ

<AccordionGroup>
  <Accordion title="If I close the tab, do I lose the answer Chief is generating?">
    No. Chief tells you "You can safely leave this page while I work." Click **Notify me** first so you get a heads-up when it finishes, then re-open the chat to see the full answer.
  </Accordion>

  <Accordion title="Why does it say &#x22;Notifications are not available in this browser&#x22;?">
    [Notifications](/help/account-settings/notification-preferences) need a normal (non-private) window and a secure (https) connection. Switch to a standard window on https and try **Notify me** again.
  </Accordion>

  <Accordion title="My answers are slow only on certain prompts.">
    Complex, multi-step questions over lots of knowledge naturally take longer. Narrowing your chat scope to just the relevant Files usually speeds them up.
  </Accordion>
</AccordionGroup>