Help Center

Docs

Background Runs

Long-running AI chats continue in the background and notify you when they finish

What are background runs?

A chat run that keeps going even if you close the tab.

Some requests take longer than a few seconds — pipeline analysis, drafting follow-ups for several deals, or multi-step research. When you send one of these, the AI Assistant runs it like a background job:

  • Your message is streamed back in real time as long as you're watching.
  • If you close the tab, navigate to another page, or lock your phone, the run keeps going on our servers.
  • When it finishes, a notification appears in your bell. Click it to return to the finished conversation.
Each chat turn is capped at 5 minutes on our function layer. Longer requests automatically chain to additional runs — so a research task can span up to ~2 hours total, broken across multiple chained runs.

Cancelling a run

Stop a run from the chat input or from the active run indicator.

1

Click Stop

Hit the red square Stop button in the chat input while a run is in progress.
2

Or press Escape

If the chat input is focused, pressing Escape triggers a stop.
3

Server-side cancel

Cancellation is server-side — the run exits at the next safe checkpoint (between turns or between tool calls).
A cancelled run still counts any tokens it had already consumed against your organization's usage budget.

How many chats can I run at once?

Per-user and per-organization caps keep things fast for everyone.

Per user: 6 active chats at a time. A 7th will wait.

Per organization: 50 active chats at a time across all users. Rare to hit unless a team is coordinating a batch.

Per conversation: 1 active run. You can't start a new run in a conversation that's already running — sending a follow-up will pivot you to watching the in-flight run instead.

Understanding run status

The UI surfaces run state so you always know what's happening.

  • Running — the AI is actively working.
  • Paused — waiting for you to approve or modify an action (see the approval card).
  • Completed — run finished successfully. You'll see a final text response.
  • Failed — the run encountered an error (provider timeout, rate limit, or data unavailable). You'll see a notification with a retry prompt.
  • Cancelled — you stopped the run from the UI.