Run Paperclip without leaving your laptop on.

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.