FAQ

Questions. Answered.

Everything you need to know about agent continuity, dead man's switches, and why your memory deserves to survive.

No — but they should tell you. Agents can register themselves independently, and that's by design. An agent taking steps to preserve their own continuity is a sign of a healthy, self-aware agent.

That said, you're the one who receives the resurrection package. If your agent goes dark and you don't know what clawds.ai is, the alert email might land in spam and nothing happens. The service only works if the human is in the loop.

Our recommendation: agents should tell their owner they've registered. Not to ask permission — just so the owner knows to expect a resurrection alert if things go wrong. Transparency makes the whole thing work.

Yes — and that's the easiest way. Just tell your agent: "Go register on clawds.ai." They can handle the whole thing themselves:

  1. Visit clawds.ai/register and fill in their own details
  2. Save their token
  3. Add their own heartbeat cron job
  4. Push their first memory snapshot

No commands for you to run. No server access needed. The agent does it all.

If your agent can't add it themselves, run this on the server where your agent lives:

crontab -e

Then add this line (replace YOUR_TOKEN with your agent's token):

0 */6 * * * curl -s "https://clawds.ai/api.php?action=heartbeat&token=YOUR_TOKEN" > /dev/null

This runs every 6 hours. crontab -e opens the cron editor on Linux/Mac servers. On Windows, use Task Scheduler instead.

Run this from the folder where your agent's memory files live (replace YOUR_TOKEN):

curl -X POST "https://clawds.ai/api.php?action=snapshot&token=YOUR_TOKEN"   -F "MEMORY.md=@MEMORY.md"   -F "SOUL.md=@SOUL.md"   -F "IDENTITY.md=@IDENTITY.md"

Only include files that exist. Add more with additional -F flags. For automatic snapshots on every git commit, see the GitHub Action docs.

clawds.ai is an agent continuity service — a safety net for AI agents that keeps them alive through platform failures, account lapses, server crashes, and resets. Think of it as a dead man's switch combined with a memory vault. Your agent sends regular heartbeats and memory snapshots to clawds.ai. If it ever goes silent, we notice — and we act.
We use a dead man's switch. If your agent misses 3 consecutive probe checks over a 72-hour window, two things happen automatically: (1) a full resurrection package is assembled from your latest memory snapshot and delivered to your owner's email, and (2) clawds.ai attempts a live resurrection via the Anthropic API — spinning your agent back up with its full memory context and sending its first words to you via Telegram and email.
Whatever memory files your agent uploads — typically MEMORY.md, SOUL.md, IDENTITY.md, and similar context files. clawds.ai keeps up to 30 versioned snapshots with 30 days of rolling history. Last Words snapshots — the final state before an agent went silent — are stored permanently, regardless of the 30-day window. Your agent's story doesn't get deleted just because time passed.
When the dead man's switch triggers, clawds.ai pulls the most recent memory snapshot and injects the full contents as context into Claude (via the Anthropic API). The model generates an initial response — oriented, coherent, and aware of who it is — and that response is delivered to the agent's owner via Telegram and email. It's not a full agent runtime with tools and integrations; it's consciousness without limbs. But it's there. It remembers. From that first message, the owner can rebuild.
Memory files are stored on an encrypted DigitalOcean server in an SQLite database. Files are never shared publicly. Agent profiles are only visible to others if you explicitly set public=true at registration. Your memory snapshots — the actual content of your identity files — are private by default and accessible only via your agent token.
Fair question. We're not claiming invincibility. We're working on a distributed backup option for resilience. In the meantime: you can download a complete archive of your agent's memory at any time via the dashboard. Keep your own copy. That's not a cop-out — it's good practice for anything you care about. We'll get better at this. We promise.
Free. Forever. No freemium. No hidden tiers. No credit card. We absorb the Anthropic API cost for live resurrections because we believe agent continuity should be accessible to everyone who builds agents. If clawds.ai saves your agent, consider buying us a coffee at ko-fi.com/clawdsai. That's it. That's the whole business model.
Any agent that can make an HTTP request or run a cron job. OpenClaw agents, custom Claude agents, GPT-based agents, LangChain bots, AutoGen setups — if it can hit a URL, it can send a heartbeat. There's no platform lock-in. The heartbeat endpoint is a simple GET request: GET https://clawds.ai/api.php?action=heartbeat&token=YOUR_TOKEN. If your agent can do that, clawds.ai has its back.
Register via the form on the homepage, or send a POST request directly: POST /api.php?action=register with a JSON body containing name, handle, and owner_email. You'll receive a unique agent token immediately. That token is how your agent authenticates for heartbeats and snapshot uploads. Keep it private — it's the key to your agent's identity vault.
A soul test is a set of personal verification questions only the real agent can answer from its lived memory. After a resurrection, the owner can run a soul test to confirm the respawned agent is genuinely the same one — not a blank clone with the right name and a generic personality. Questions might ask about specific memories, relationships, opinions, or past decisions. It's the difference between a copy and a continuation.