Close the laptop. The agent keeps working.
AgentSky runs your agent in a persistent cloud sandbox that retains files, state, and session history across supported pause, restart, and image-update flows. This runtime has completed 40,835 tasks across 10 agent stacks without a local machine to keep alive. Any authorized teammate can resume from web, Slack, Telegram, or the API.
Agents lose their context and work when the machine that started them goes offline.
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.
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.
How it works
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.
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.
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.
See capability details