Spaces:
Runtime error
Runtime error
Simplify Why HuggingClaw: two paragraphs, two problems (persistence + DNS)
Browse files
README.md
CHANGED
|
@@ -49,21 +49,9 @@ tags:
|
|
| 49 |
|
| 50 |
## Why HuggingClaw?
|
| 51 |
|
| 52 |
-
[OpenClaw](https://github.com/openclaw/openclaw) is a powerful
|
| 53 |
|
| 54 |
-
|
| 55 |
-
|
| 56 |
-
**HuggingFace Spaces** offers the perfect fit: free CPU instances with 2 vCPU and 16 GB RAM, always-on HTTPS, and zero maintenance. There's just one catch — Space containers are **ephemeral**. Every restart wipes your data.
|
| 57 |
-
|
| 58 |
-
**HuggingClaw** solves this by using a private **HuggingFace Dataset** repo as persistent storage. Your conversations, credentials, and settings are automatically synced on a schedule, and restored on every cold start. You get all the benefits of free cloud hosting with none of the data loss.
|
| 59 |
-
|
| 60 |
-
| Feature | Detail |
|
| 61 |
-
|---------|--------|
|
| 62 |
-
| **Free compute** | Runs on HF's free CPU tier (2 vCPU, 16 GB RAM) |
|
| 63 |
-
| **Always online** | No need to keep your computer running |
|
| 64 |
-
| **Auto-persistent** | Syncs data to a private HF Dataset repo on schedule |
|
| 65 |
-
| **HTTPS built-in** | Secure WebSocket connections out of the box |
|
| 66 |
-
| **One-click deploy** | Fork → set secrets → done |
|
| 67 |
|
| 68 |
## Architecture
|
| 69 |
|
|
|
|
| 49 |
|
| 50 |
## Why HuggingClaw?
|
| 51 |
|
| 52 |
+
[OpenClaw](https://github.com/openclaw/openclaw) is a powerful, popular AI assistant (Telegram, WhatsApp, 40+ channels), but it’s meant to run on your own machine (e.g. a Mac Mini). Not everyone has that. You can deploy on the cloud, but most providers either charge by the hour or offer only very limited resources. **HuggingFace Spaces** gives you 2 vCPU and **16 GB RAM** for free — a good fit for OpenClaw, but Spaces have two problems we fix.
|
| 53 |
|
| 54 |
+
**HuggingClaw** is this repo. It fixes two Hugging Face Space issues: **(1) Data is not persistent** — we use a private **HuggingFace Dataset** to sync and restore your conversations, settings, and credentials so they survive restarts; **(2) DNS resolution fails** for some domains (e.g. WhatsApp) — we fix it with DNS-over-HTTPS and a Node.js DNS patch so OpenClaw can connect reliably.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 55 |
|
| 56 |
## Architecture
|
| 57 |
|