Skip to main content
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

Work survives your 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.

Work can start without you

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.

One agent, every surface

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.

Nothing is processed on your device

The agent reads your documents server-side. Documents are not downloaded to your computer for processing, and no provider credentials ever reach your browser.

​
What happens when you send a message

1

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.
2

Checks run before any model is called

Casa Conect confirms that your organization’s subscription is active, that the chosen model is allowed, and that there are credits to pay for the work.
3

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”.
4

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.

​
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, an approval or a browser takeover, 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. 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

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.
Agent sessions and other background work run on a managed job platform operated by a specialist provider, listed under 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.
Sessions reach Casa Conect’s data over private network links, not the public internet, and authenticate with short-lived credentials rather than stored passwords.
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.
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.
For the full picture, read Hosting and infrastructure, AI data handling and Agent safety.

​
Troubleshooting

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.
This is a display problem, not a failure of the work. Refresh the page to see the saved result.
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.