Run Paperclip without leaving your laptop on
A local Paperclip install is the fastest way to see what it does, and the fastest way to discover that a sleeping laptop does not miss one chat, it misses the entire company's work cycle. Heartbeats are how Paperclip schedules everything, and a heartbeat that never fires is an org chart of agents sitting idle until you open the lid.
Direct answer
How do I keep Paperclip running when my laptop is off?
Move it to a machine that stays awake, and remember there are two layers to move, not one. The Paperclip server holds the scheduler, so routines and heartbeats only fire while it is up. The agents it delegates to need to be reachable and running too, whether that is a sandbox provider it provisions or a runtime living somewhere else. Put the control plane on a server or in Docker, and put the agents somewhere that does not sleep either.
What stops when the laptop sleeps
| Layer | On your laptop | On a host that stays awake |
|---|---|---|
| Paperclip server | Suspends, so no heartbeat fires. | Scheduler keeps running, routines fire on time. |
| Routines and goals | Silently skipped until you open the lid. | Advance overnight as configured. |
| Agents doing the work | Unreachable, so delegated work fails. | Reachable and running, on a sandbox provider or a managed runtime. |
| What you maintain | One device, and its uptime. | A server and a database, or a platform that runs the agents for you. |
Heartbeats are the entire scheduling model
Paperclip does not sit and wait for you to type. Agents wake on heartbeats, routines run on a cadence, and delegation flows between agents on that same clock. All of it lives in the server process. When the machine hosting that process suspends, nothing queues up and catches later; the cycle simply does not happen. That is a different failure from a chat app going offline, because the work you were counting on overnight was the whole point.
Why a laptop cannot be the host
The things that make a laptop a good personal computer are exactly what break a scheduler.
- Sleep and lid-close suspend the server process and its heartbeats.
- Network changes cut the control plane off from the agents it delegates to.
- Reboots for updates end the process with no warning and no restart.
- Disabling sleep only ties your uptime to one fragile device you also need to carry.
Move the control plane first
Paperclip's own deployment documentation covers the honest options: run it in Docker, or deploy it to a server such as a VPS or Fly, with a real database behind it, storage configured, and secrets held properly. If you want the dashboard private rather than exposed, their docs cover reaching it over a Tailscale network instead of publishing it. This is the part you can do today, and it is a normal server deployment with normal server responsibilities.
Sources: Paperclip deployment reference · Paperclip private access over Tailscale
Then move the agents, because that is a second machine
This is where most people stop too early. Getting the control plane onto a server makes the scheduler fire, but a heartbeat that wakes an agent whose runtime lives on your laptop has not solved anything. Paperclip can provision execution environments through a sandbox provider, or delegate to a runtime running elsewhere through an adapter. Either way the agents need a home that stays online, separate from the one the control plane sits on.
Sources: Paperclip sandbox providers
The managed path for the agent layer
If the reason you are reading this is that you do not want to operate servers, the agent layer is the one you can hand off today. Qoren deploys OpenClaw, Hermes, and Codex agents into dedicated cloud environments that stay online by default, put them on a schedule, isolate their secrets, monitor their health, and cap their spend, all from a dashboard rather than SSH. Qoren does not host the Paperclip control plane; that part stays yours. But it removes the laptop from the half of the stack that does the actual work.
Related guides
Paperclip hosting guide
How to host Paperclip 24/7, and the cost line most guides miss
What it costs to host Paperclip 24/7: the control-plane server, a real database, storage, and the agent compute most hosting guides leave off the bill.
Read guideAgent comparison
OpenClaw vs Paperclip: the agent, and the org chart above it
OpenClaw is the agent doing the work; Paperclip is the org chart above it. Where each one fits, where they overlap, and which layer you need first.
Read guideAlways-on OpenClaw
Run OpenClaw without leaving your laptop on
Your laptop sleeps and the agent dies. Here is why local runs stop, and the practical ways to keep OpenClaw working 24/7 without babysitting a machine.
Read guideFrequently asked questions
Why do my Paperclip agents stop when I close my laptop?
Because the scheduler lives in the Paperclip server process, and closing the lid suspends it. Heartbeats and routines only fire while that process is running, so nothing wakes and nothing catches up later.
Can I just stop my laptop from sleeping?
You can, and it ties an entire company of agents to one device. A reboot, a power blip, a network change, or simply needing to take the laptop somewhere still stops the schedule. A host meant to stay online is the real fix.
Is moving the Paperclip server enough?
Only half. The control plane firing heartbeats is useless if the agents it delegates to live on a machine that is asleep. Both layers need a home that stays online, which is why this is two hosting decisions rather than one.
What is the easiest way to keep the agents online?
Hand off the agent layer. Qoren runs OpenClaw, Hermes, and Codex agents in dedicated managed environments that stay online, on a schedule, with monitored health and a hard spend cap, so there is no server for that half to babysit.
Does Qoren run the Paperclip control plane for me?
No. Qoren hosts agents, not Paperclip itself. You keep the control plane on a server, in Docker, or wherever their deployment docs lead you, and Qoren keeps the agents underneath it running.
Run OpenClaw, Hermes or Codex agents 24/7, without the homework.
Qoren runs the machine, the secrets, the updates and the logs, with a hard cap on credit spend. Start from a template and have an agent working today.