Your PC just became a personal AI assistant, no cloud required

Most AI assistants are rented, not owned. You pay monthly, your data passes through someone else’s servers, and the moment you stop paying, your setup vanishes. What if your own machine handled all of that instead?

That’s the exact frustration that sparked HyperClaw. The creator, u/Traditional_Cup_1151, posted this open-source project to r/ChatGPTPromptGenius, and the premise is straightforward: turn your Windows, macOS, or Linux PC into a self-hosted AI assistant that talks back to you through the messaging apps you already use.

What HyperClaw actually does

At its core, HyperClaw is a local AI hub. You install it on your machine, point it at your preferred AI model, and it responds to you through whatever chat channel you prefer. No cloud middleman. No recurring subscription for the infrastructure.

Here’s what the author packed in:

• 28+ messaging integrations: Telegram, Discord, WhatsApp, Signal, iMessage, Slack, Matrix, and two dozen more. Pick one or several; they all route through the same local assistant.
• Multi-model support: GPT-4, Claude, Grok, Gemini, and local Ollama models all work. You can swap between them through config without rebuilding anything.
• Voice in both directions: TTS and STT are built in, so you can speak to your assistant and have it speak back.
• Docker sandbox for tools: Any tools your assistant runs are isolated inside Docker, which keeps your main system clean and your execution environment reproducible.
• MCP protocol support: This is actually the twist worth paying attention to. MCP (Model Context Protocol) means HyperClaw can connect to external tool servers, letting your assistant reach beyond its local context. It’s the same protocol that Claude Desktop and a growing number of AI clients use, so the ecosystem of compatible tools is already substantial.
• Config hot-reload: Change settings and they apply immediately. No restart. No downtime.
• Built-in security audit: The tool includes a self-audit feature so you can check your own setup for obvious vulnerabilities before exposing it.

Getting started

The author made the onboarding deliberately minimal. Here’s the full setup path:

1. Make sure you have Node.js installed on your machine
2. Run npm install -g hyperclaw && hyperclaw onboard in your terminal
3. Follow the onboarding prompts; it walks you through connecting your first messaging channel and choosing your AI model
4. Point HyperClaw at your API key (OpenAI, Anthropic, xAI, Google, or a local Ollama endpoint)
5. Send a message from Telegram, Discord, or whichever channel you configured; your PC responds

The “no WSL” note is worth highlighting for Windows users specifically. A lot of self-hosted tools technically support Windows but make you install the Linux subsystem to get there. HyperClaw runs natively, which removes a meaningful barrier.

How it compares

A community member asked how this differs from OpenClaw: a fair question since the naming is similar. The author didn’t respond in the thread, so it’s an open point worth investigating if you’re choosing between them. From what’s described in the post, HyperClaw’s differentiators appear to be the breadth of messaging integrations (28+ channels is genuinely wide coverage), the MCP protocol support, and the focus on a clean one-command setup.

If you’ve used something like n8n or a self-hosted Home Assistant setup for AI routing, HyperClaw takes a more opinionated, packaged approach. It’s less “build your own workflow” and more “get a working assistant fast, then customize.”

For users who’ve tried running local models through Ollama or LM Studio and wanted to tie them to a chat interface, this adds that last-mile connection without requiring you to wire it all together manually.

A few things to keep in mind

The project is open-source and early-stage. With 16 upvotes and a small comment thread, it’s not yet battle-tested by a large community. That’s not a knock; it’s a realistic framing. You’re adopting something built by an individual developer who’s clearly thought about UX (one-command setup, hot-reload, built-in audit), but edge cases and platform-specific quirks are likely to surface.

Also worth noting: while the local infrastructure is free, you’ll still need API keys for cloud models like GPT-4 or Claude. The “no subscription” pitch applies to the assistant layer, not necessarily to the underlying model costs. Local Ollama models avoid this entirely if that’s a priority for you.

Pro tip

Start with a single messaging channel rather than connecting all 28 at once. Get one working cleanly; Telegram is usually the smoothest for this kind of setup. Then expand. Debugging multi-channel routing issues is much harder than debugging one clean integration.

You can find HyperClaw linked in the original Reddit post in r/ChatGPTPromptGenius. The author is active in the comments and offered to answer questions directly.

HyperClaw – personal AI assistant (GPT/Claude/Grok) on your own PC, replies via Telegram, Discord, Signal & 25+ more channels
by u/Traditional_Cup_1151 in ChatGPTPromptGenius