---
title: "Background agents with persistent cloud sessions — AgentSky"
description: "Keep files, state, and session history in a persistent cloud sandbox beyond one laptop or teammate. See AgentSky's recovery scope and self-hosting boundary."
url: https://agentsky.dev/use-cases/background-agents
---

[Log in](https://agentsky.dev/auth/start?returnTo=%2Fuse-cases%2Fbackground-agents) [Sign up](https://agentsky.dev/auth/start?returnTo=%2Fuse-cases%2Fbackground-agents&mode=signup)

[All use cases](https://agentsky.dev/use-cases)

# Close the laptop. The agent keeps working.

Your agent runs in a persistent cloud sandbox that keeps its files and history.

[Try in Playground](https://agentsky.dev/playground/enter) [Read the developer API](https://agentsky.dev/developers)

## Starter prompt

```
Every [morning at 9am], check [the source — issue queue, alert channel, inbox] and [the routine job].
If nothing needs me, say so in one line. If something does, do the work and tell me what you changed.
```

Agents lose their context and work when the machine that started them goes offline.

AutomateHermes + DeepSeek V4 Pro

## Related

- [Hermes in the catalog](https://agentsky.dev/agents/hermes)
- [See capability details](https://agentsky.dev/developers)
- [Run it from the API](https://agentsky.dev/developers)
- [What a run costs](https://agentsky.dev/pricing)

## Choose something else when

Use a local agent for short device-bound work, or a self-hosted runtime when infrastructure ownership, data residency, or custom images are mandatory.

## Best for

- Teams handing off long-running work across people or supported channels while the agent's cloud computer and session stay available.
- You bring the task and instructions.
- You bring the agent harness and model.
- You bring the which channel to resume from.

## How it works

1. Step 1 Job transfers to a persistent cloud sandbox Start a session from the Playground, the API, or the sky CLI. The agent owns a cloud computer from the first message — not dependent on your laptop or local connection.
2. Step 2 Sandbox outlasts any single session Files, tools, and session history remain available through supported pause, restart, and image-update flows. Recovery returns the agent to its persisted work state without rebuilding the runtime by hand.
3. Step 3 Full history resumes from any channel Resume from web, Slack, Telegram, or the API. The full session history is in place — any team member can continue, not just whoever started the session.

## What AgentSky runs

- Persistent cloud sandbox
- Files, state, and history
- Recovery on restart

## Agent Hosting

Teams bring their existing agent and model subscription to AgentSky. The persistent sandbox, automatic recovery, and session history run underneath — no fleet to operate, no sessions to restart manually.

A product capability description, not a published SLA or independent reliability benchmark; validate recovery requirements for your workload.

[See capability details](https://agentsky.dev/developers)

---

Markdown copy of https://agentsky.dev/use-cases/background-agents. Every agentsky.dev page has one: add `.md` to its address or send `Accept: text/markdown`. Start from https://agentsky.dev/llms.txt.