Running It on Your Own Computer

The fastest way to meet OpenClaw is to install it on the computer in front of you. A few minutes later you are chatting with it. Before you leave it there for good, it is worth knowing what you give up, and what you put within the agent's reach.

The rule

Your own computer: ideal for trying it, poor for always-on.

Why it works well

• Nothing to rent and no monthly bill. No remote machine to look after.
• Running in minutes, which makes it ideal for experimenting, learning, and a personal assistant that only you use.

Why it falls short

• It sleeps when your computer sleeps. Close the lid and the Gateway stops: no replies, no heartbeats, no cron jobs.
• Nothing outside can reach in. Home networks block incoming connections by default. Chat apps such as Telegram still work, because the Gateway reaches out to them, but anything that has to reach in, such as a webhook from GitHub, gets stuck at your router.
• It shares a machine with your life. The agent can run commands and read files. On your personal computer, that puts it next to your documents, browser sessions and saved keys. This is why the security checklist recommends an isolated machine, whether a VPS, a virtual machine or a dedicated device, for anything beyond trying it out.

If you do run it locally, treat it as a single-user setup and lock it down:

• keep the Gateway bound to localhost, and set a strong, random auth token;
• keep API keys in environment variables, never written into config files;
• run OpenClaw as a normal user, not as root (the all-powerful administrator account);
• keep the sender allowlist to just you, and turn on device pairing so unknown devices cannot connect;
• run openclaw security audit --deep after any config change, and update OpenClaw regularly.

The shortcut

Ask three yes-or-no questions: Must it work while my computer sleeps? Must something outside my network reach it? Will it touch anything I would hate to lose? Any "yes" means it should move off your personal computer.

Drills

Answer fast — trust the rule.

Remember

• Your own computer: ideal for trying it, poor for always-on.
• Three questions (sleeps? reached from outside? touches precious things?). Any "yes", move it.
• Still lock it down: localhost, a strong token, keys in environment variables, a normal user, an allowlist of one.