A personal AI agent running 24/7 on dedicated hardware is a step change in what an AI assistant can do for you. It manages your email, calendar, and files. It browses the web, runs commands, and builds custom tools. And it is always there, reachable from your phone.
The open-source agent framework OpenClaw makes this possible on a repurposed Windows laptop that would otherwise sit in a closet. This guide covers the ten essential steps to get a production-grade personal agent online. It is not a full reference manual -- it assumes you can fill in the gaps and reach for the error log when something goes sideways.
You will need: a Windows 11-capable laptop (even an 8th-gen i5 with 8 GB RAM works), about three hours of focused time, and $20 to seed your Anthropic account for the first month of operation.
1Pre-Flight Prep (Do This on Your Current Machine)
Before touching the laptop you are about to wipe, set these up on your current computer and save every credential to a password manager:
Two Google accounts. One personal (infrastructure logins: Microsoft account, Anthropic, Brave, Tailscale). One work (the agent's OAuth target for Gmail and Calendar). Both must have 2FA enabled and backup codes saved.
Anthropic API key. At console.anthropic.com, create a key and set a monthly spending limit ($20-50). A runaway loop burns through credits fast.
Brave Search API key. Free tier from brave.com/search/api. About 1,000 searches per month included.
Telegram bot. Talk to @BotFather, create a new bot, save the token. Give it a name you can live with -- this becomes your agent's identity.
2Validate the Device Encryption Key (Critical)
Windows 11 Home silently enables Device Encryption on most modern hardware. During the wipe, after you clear the TPM, the drive will demand a 48-digit recovery key. If you cannot produce it, the wipe stalls.
Before you reset: on the laptop, run manage-bde -protectors -get C: in PowerShell as Admin to find the Key ID. Then go to account.microsoft.com/devices/recoverykey, sign into every Microsoft account that has ever touched this laptop, and match the Key ID. Save the 48-digit number somewhere accessible from another device. Not on the laptop you are about to wipe.
3Wipe and Reinstall Windows
Settings > System > Recovery > Reset PC. Choose Remove everything, Cloud download, and turn on Clean data. Plug into AC power. The process takes 30-60 minutes.
During the reset, press F12 if prompted to clear the TPM. Have that recovery key ready for the next screen.
At OOBE, sign in with your Microsoft account. Decline the bloat: diagnostic data set to Required Only, no personalization, no ad ID. Watch for the "Restore from backup" screen -- the option to start fresh is a small text link at the bottom, not the big Restore button. If you accidentally restore, just re-wipe.
After Windows is up: run Windows Update, restart, repeat until clean. Remove trial antivirus and manufacturer bloat. Keep OEM driver updaters if they exist.
Critical power tweak: Settings > System > Power & battery. Set sleep when plugged in to Never. Power mode: Best performance. In Control Panel > Power Options, set closing the lid to Do nothing. Disable hibernation: powercfg /hibernate off as Admin.
4Install Node.js -- Use v22, Not the Latest
This is the most common gotcha in the entire setup. Node 24, 25, and 26 break OpenClaw's AbortController, causing 30+ second command hangs and gateway instability. Go to nodejs.org/en/download, switch the version dropdown to v22, download the Windows Installer.
During install, check "Automatically install the necessary tools." Reboot after it finishes. Verify:
node --version # expect v22.x.x
npm --version # expect 10.x or 11.x5Install OpenClaw and Run the Onboarding Wizard
As Administrator in PowerShell:
npm install -g openclaw
openclaw --version
openclaw onboardThe wizard walks through: provider (Anthropic), paste your API key, channel (Telegram, paste bot token), web search (Brave, paste API key). When it hits the skill selection list: use SPACE to toggle items on, Enter to confirm. This is easy to miss and the most common multi-select mistake.
Enable: ClawHub, file/shell operations, web browse/fetch, memory/notes. Skip anything you lack API keys for.
For memory search: unless you have an OpenAI, Voyage, or Gemini embedding key, disable it. The agent still has plain-text memory through workspace files. You can enable vector recall later.
When the wizard finishes, immediately re-check the power settings. The installer has been observed to silently flip sleep back to a timed value.
Confirm the gateway is up: visit http://localhost:18789 on the laptop. The Control UI should load.
6Pair Telegram and Set Up Commands
Three things need to line up before Telegram works properly:
Config structure. Telegram must sit under channels.telegram in your config file, not under plugins.entries. If it ends up in plugins, the gateway logs "plugin not found: telegram" and the bot never connects.
Pairing. Send any message to your bot from your phone. It will reply "access not configured." On the laptop:
openclaw pairing list telegram
openclaw pairing approve telegram <code>Command permissions. Your Telegram user ID must be in commands.ownerAllowFrom with the telegram: prefix, or the bot chats happily but ignores all /-commands:
"commands": {
"ownerAllowFrom": ["telegram:123456789"]
}Find your Telegram user ID by messaging @userinfobot. Restart the gateway after adding it.
7Cost and Rate-Limit Hardening (Do This Before You Chat)
OpenClaw defaults are tuned for capability, not budget. On a stock install, a chatty afternoon can burn $20+ and hit Anthropic's Tier 1 rate limit of 30,000 input tokens per minute. Once a session passes ~30K tokens, every request fails forever -- waiting does not help, retrying stacks cooldowns, and switching to Opus masks the problem at 5x the cost.
Run these before the first real conversation:
openclaw config set agents.defaults.contextInjection continuation-skip
openclaw config set agents.defaults.compaction.reserveTokensFloor 20000
openclaw config set agents.defaults.contextTokens 50000
openclaw config set agents.defaults.bootstrapTotalMaxChars 50000
openclaw config set agents.defaults.bootstrapMaxPerFile 15000
openclaw config set agents.defaults.compaction.mode safeguard
openclaw config set agents.defaults.heartbeat.enabled falseThen openclaw gateway restart.
If you ever see rate_limit_error return mid-conversation, your session has grown too large. Start a fresh one with /new. Living in one infinite session is what causes the wall.
8Configure Web Search and the Agent Workspace
Web search needs both of these blocks in your config file, or it fails silently (no error, just empty results):
"plugins": {
"entries": {
"brave": {
"enabled": true,
"config": { "webSearch": { "apiKey": "your-brave-api-key" } }
}
}
},
"tools": {
"web": {
"search": { "enabled": true, "provider": "brave" }
}
}Set up the workspace files in your profile's workspace\ directory. These inject context into every agent turn, so keep them lean:
- IDENTITY.md -- who the agent is, its name and purpose
- USER.md -- who it serves: your name, role, contact info
- SOUL.md -- personality, tone, working preferences
- MEMORY.md -- long-term curated memory you build over time
- TOOLS.md -- environment notes: hosts, API keys, preferences
9Set Up Remote Access with Tailscale
Tailscale creates a private encrypted network so you can reach your agent from anywhere without exposing it to the public internet.
On the laptop: install from tailscale.com/download/windows, sign in with your infrastructure Google account, note the laptop's Tailscale IP (100.x.y.z). On your phone and main computer: install Tailscale, sign in with the same account.
From your main computer, open http://<laptop-tailscale-ip>:18789 and bookmark it. For HTTPS support, run openclaw gateway --tailscale serve on the laptop.
10Verify Everything
Run the checks, then run them again after a reboot:
Health check: openclaw doctor -- fix anything flagged critical. openclaw models status -- confirm your Anthropic key is valid.
Test from Telegram:
Any question -- "What is the weather in Boston today?"
Web search -- "Search for recent news about AI in education"
File operation -- "Create a file called test.md in the workspace"
Memory recall -- "What do you remember about me?"
Reboot test: restart the laptop. After it boots, wait a minute, then check http://localhost:18789. The gateway should start automatically through its Windows scheduled task. If it does not, re-verify the Task Scheduler entry: it should have a startup trigger and restart-on-failure configured.
Power settings re-check: Settings > System > Power & battery. Confirm sleep when plugged in is still Never. Windows Update can revert this on major updates.