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

# Parked chats and limits

> Why idle chats park, how to resume them, and the default limits on turn length and running chats.

Remote chats run in the cloud. Newly parks chats you aren't using and applies a few default limits. None of this loses your saved work.

## Parked chats

By default, a Remote chat parks after about 15 minutes with no messages and no preview actions. Parking is like the chat falling asleep. The chat header shows "Parked — your next message resumes it".

* **These keep a chat awake:** a turn the agent is still working on, or a native build that's still running.
* **These don't:** watching the preview, or a question from the agent that's waiting for your answer.

## Resume a parked chat

Do either of these:

* **Send a message.** The chat wakes up and the agent works on your message.
* **Use a preview action,** such as opening the Web view or clicking **Start my simulator**.

Waking up can take a moment. Your code and the packages your app uses are kept.

Your simulator ends when a chat parks. When you come back, **Resume** starts a fresh device. See [Using the cloud simulators](/preview/simulators).

If you use Developer mode, **Stop** in the Sessions list parks a running chat too. See [Settings and Developer mode](/account/settings).

## One-hour turn limit

By default, a single turn can run for up to one hour. If the agent reaches that, you see:

"This turn reached its one-hour limit. Your saved work is safe; send another message to continue."

Send another message and the agent picks up from there. Time the agent spends waiting for your answer to one of its questions doesn't count toward the hour.

<Tip>
  Turns that reach the limit are usually trying to do too much at once. Break the work into smaller requests. See [Prompting tips](/build/prompting-tips).
</Tip>

## How many chats can run at once

By default, up to 3 Remote chats can be starting or running at the same time across your organization. Parked chats and Local chats don't count.

If you start another chat while 3 are running:

* The new chat may wait as **Queued** or **Starting** until another chat finishes or parks, then start on its own.
* Or you see "You’ve reached the active session limit. Your prompt is saved as a draft." Your message isn't lost. Choose **Free a slot** to find a running chat you can stop, or wait for another chat to finish or park. Then choose **Retry** to send it.

If no slot frees up in time, the chat shows "You already have as many sessions running as your plan allows. Finish one you are done with, then try again." Stop or finish a chat you no longer need, then try again.

## Local chats on your Mac

In Local chats (Mac): the chat runs on your Mac, so it depends on your Mac being awake and online. If your Mac sleeps or loses its connection, the chat shows **Disconnected** and then **Parked**. Nothing is lost. Open the Mac app again and send a message to continue. See [Local chats on your Mac](/mac/local-chats).

## Changing the limits

You can't change these limits yourself. If they get in the way of your work, [contact support](/help/getting-help).

## Related

<CardGroup cols={2}>
  <Card title="Chatting with the agent" icon="comments" href="/build/chatting-with-the-agent">
    Stopping and queueing messages.
  </Card>

  <Card title="Messages explained" icon="circle-info" href="/help/messages">
    What chat and preview messages mean.
  </Card>
</CardGroup>