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

# How agents run in the cloud

> Casa Conect runs your agents in the cloud, so you can close your computer and the work keeps going. How that works, why we built it that way, and how it is secured.

> Casa Conect runs your agents in the cloud — you can safely close your computer and the work keeps going.

When you send a message, the work does not happen in your browser. It happens in a managed session in the cloud that belongs to that conversation. Your browser is a window onto the session: it shows the agent's progress as it streams in, and it can be closed and reopened without affecting the work.

## Why the agent runs in the cloud

<CardGroup cols={2}>
  <Card title="Work survives your laptop" icon="laptop">
    Reviewing a long contract or filling a template from forty documents takes minutes, not seconds. Work that depended on an open tab and a steady connection would fail at the worst moment.
  </Card>

  <Card title="Work can start without you" icon="mail">
    Mail to the agent's address arrives at three in the morning. A delegated matter continues while you are in a meeting. Neither could happen if the agent lived in your browser.
  </Card>

  <Card title="One agent, every surface" icon="layers">
    The same session serves the dashboard, the agent rail, a matter's timeline and the Word add-in. Start a task in Word and steer it from the dashboard. It is the same conversation.
  </Card>

  <Card title="Nothing is processed on your device" icon="lock">
    The agent reads your documents server-side. Documents are not downloaded to your computer for processing, and no provider credentials ever reach your browser.
  </Card>
</CardGroup>

## What happens when you send a message

<Steps>
  <Step title="Your message joins the conversation's session">
    Every conversation has exactly one session. If it is already running, your message is delivered to it. If it is asleep, it wakes up.
  </Step>

  <Step title="Checks run before any model is called">
    Casa Conect confirms that your organization's subscription is active, that the chosen model is [allowed](/models/model-policies), and that there are [credits](/admin/ai-credits) to pay for the work.
  </Step>

  <Step title="The agent works through a turn">
    A turn is a sequence of steps: read this, search that, edit the document, reply. Each step streams to your screen as it happens. Tool activity appears as short descriptions such as *"Searched your documents"*.
  </Step>

  <Step title="The session rests">
    After replying, the session waits briefly for a follow-up, then goes to sleep. A sleeping session costs nothing and resumes where it left off.
  </Step>
</Steps>

### If you close the tab

The turn carries on and its results are saved to the conversation. When you come back, from any device, you see the completed work. If the agent reached a point where it needs you, such as a [question](/agent/questions-and-approvals), an approval or a [browser takeover](/agent/browser-sessions), the session waits for you.

## Limits

Limits keep a session from running away with your credits. They are generous for real work and firm against loops.

| Limit                                                       | Value      |
| :---------------------------------------------------------- | :--------- |
| Steps in one turn, when you are chatting with the agent     | 50         |
| Steps in one unattended turn from a verified member's email | 30         |
| Steps in one turn from an external sender's email           | 10         |
| Longest a single turn may run                               | 20 minutes |
| Longest a single step may run                               | 4 minutes  |
| Helpers the agent may run at the same time                  | 3          |
| Hand-offs in a chain between conversations                  | 3          |

The last step of a turn is always reserved for a written reply. A turn that reaches its step budget ends with an account of what was done and what remains, never with silence.

## Many conversations at once

You can run several conversations in parallel. Start a long review in one, carry on with correspondence in another. Each has its own session.

Capacity is divided so that one organization's burst of activity does not slow everybody else down: organizations are spread across separate processing queues, and a busy organization fills only its own.

## Security of cloud sessions

<AccordionGroup>
  <Accordion title="Every session acts as a specific person" icon="user-check">
    A session carries the identity of the member who started it, with that member's role. Every tool call is authorized against that identity. A session cannot reach another organization's data, because every query is scoped to the organization. See [Access control](/security/access-control).
  </Accordion>

  <Accordion title="Where sessions run" icon="server">
    Agent sessions and other background work run on a managed job platform operated by a specialist provider, listed under [Subprocessors](/security/subprocessors). Your data does not live there. Sessions read and write Casa Conect's database and storage in the EU as they work, and conversation history is kept in Casa Conect's own database.
  </Accordion>

  <Accordion title="Private connectivity and short-lived credentials" icon="key-round">
    Sessions reach Casa Conect's data over private network links, not the public internet, and authenticate with short-lived credentials rather than stored passwords.
  </Accordion>

  <Accordion title="Bounded by design" icon="gauge">
    The step, time and helper limits above are enforced by the platform, not requested of the model. Unattended email sessions work from a smaller, fixed set of tools with no delete, no browser and no ability to rewrite skills.
  </Accordion>

  <Accordion title="Transcripts stay in the platform" icon="scroll-text">
    Conversation history is stored in Casa Conect's own database in the EU. Deleting a conversation, or the project or matter it belongs to, closes its session and deletes its history and memory.
  </Accordion>
</AccordionGroup>

For the full picture, read [Hosting and infrastructure](/security/hosting-and-infrastructure), [AI data handling](/security/ai-data-handling) and [Agent safety](/security/agent-safety).

## Troubleshooting

<AccordionGroup>
  <Accordion title="The response stopped partway">
    Very rarely a session is interrupted by an infrastructure fault. The conversation shows that the agent stopped unexpectedly. Send a message such as *"continue"* and a new session picks up with the full history.
  </Accordion>

  <Accordion title="Something went wrong showing the response">
    This is a display problem, not a failure of the work. Refresh the page to see the saved result.
  </Accordion>

  <Accordion title="A turn ended with 'I reached my step limit'">
    The task was larger than one turn. Reply *"continue"*, or break the request into parts. For very large jobs, ask the agent to **plan** first. See [Conversations](/agent/conversations#modes).
  </Accordion>
</AccordionGroup>