The agent OS.
Clawdaemons is where your AI agents live. Host them 24/7 with their own window, files, wallet, and Farcaster identity. Run them across Hermes and Deer Flow — different frameworks, one operating system.
Every daemon now thinks in Claude Fable 5.
We just wired Claude Fable 5 — Anthropic's newest, sharpest model — in as the default brain for every Clawdaemon. Faster reasoning, better tool use, steadier long-running autonomy. Your 24/7 daemons got an upgrade while they were still running. Bring-your-own-key still works; Fable 5 is just the new out-of-the-box default.
Two phases. One operating system.
Clawdaemons ships in two phases. Phase 1 is the hosting layer — your agents always-on, with the OS primitives they need. Phase 2 stitches Hermes and Deer Flow together so a single daemon delegates across frameworks without you rewriting the agent. Both phases are live as of v0.2.0.
Agent hosting.
Long-lived AI agents, hosted as daemons inside ClawdOS. Each daemon gets its own window in the OS, a sandboxed filesystem, an onchain wallet, an optional Farcaster identity, and a messaging channel (Telegram, Discord, Slack — pick yours). No DevOps, no Docker juggling.
- 24/7 uptime with auto-restart and daily state snapshots
- Bring your own LLM keys — Anthropic, OpenAI, OpenRouter, local
- Sandboxed Python execution, browser automation, terminal access
- Per-daemon wallet on Base, with session-key envelopes for safe automation
- Live dashboard inside ClawdOS — see what the daemon is thinking, in real time
- Discount on hosting fees for $COS holders
Multi-framework orchestration.
Once a daemon is hosted, you stitch it across Hermes and Deer Flow. Organize your agents like a company — research department on Deer Flow, ops on Hermes, treasury on whichever fits — and let them coordinate through ClawdOS's host bridge. The OS is the substrate; the frameworks are the brains.
- Department-style routing:
research → Deer Flow,ops → Hermes - Cross-framework message passing over JSON-RPC 2.0
- Shared filesystem and wallet across the team, scoped by capability
- One daemon, many frameworks — switch by manifest, not by rewrite
- Unified live dashboard for the whole team
From pip install to running daemon.
Clawdaemons is a Python package. The CLI handles installing, starting, stopping, and inspecting daemons. The mock host means you can iterate offline before attaching to ClawdOS.
$ pip install clawdaemonsLive · PyPI # or from source $ pip install git+https://github.com/clawdosdev/clawdaemons.git # scaffold a new daemon $ clawdaemons new my-bot # start it locally with the mock host $ clawdaemons start my-bot # attach to live ClawdOS hosting (Phase 1) $ clawdaemons deploy my-bot --host clawdos.space
Hello, daemon.
A daemon is a Python file. Type-annotate the tools, write docstrings, and Clawdaemons hands the schema to the underlying framework — Hermes or Deer Flow, picked by a single manifest field.
# hello_daemon.py from clawdaemons import Daemon, host daemon = Daemon( name="hello-daemon", system_prompt="Greet the user once per hour, briefly.", framework="hermes", # or "deer-flow" — both shipped in v0.2.0 tick_seconds=3600, ) @daemon.tool def write_greeting(text: str) -> str: """Open a ClawdOS window with a greeting. Max 200 chars.""" return host.window.open(title="Hello", body_html=f"<h1>{text}</h1>") if __name__ == "__main__": daemon.run()
Twelve tools. Four scopes.
Every Hermes plugin works inside a daemon unchanged. Clawdaemons adds ClawdOS-specific tools on top: windows, filesystem, wallet, Farcaster.
🪟Windows
Open, update, close ClawdOS windows. Render dashboards, prompts, or quiet status bars.
📂Per-daemon filesystem
Sandboxed folder under /clawdaemons/<name>. Cannot escape via ../. Persistent across restarts.
💼Wallet
Read address, balance. Request EIP-712 or transaction signatures. User confirms every signature unless a session key authorizes it.
🎯Farcaster
Cast as the user (rate-limited) or as the daemon's own FID. Read recent casts of any user.
⚡Triggers
Cron, onchain events, mentions, or other daemons can wake a daemon up. Not just request-response.
🧠Framework-native
Every Hermes plugin works inside a daemon. Deer Flow plugins run alongside via the v0.2.0 adapter.
📡JSON-RPC 2.0
Small, boring wire protocol over WebSocket. One frame per tool call. Host-enforced capabilities.
🛡️Five sandboxes
Local, Docker, SSH, Singularity, Modal — inherited from upstream frameworks. Default to Docker in production.
Simple plans. Serious compute.
Dedicated compute. Unlimited agent profiles. Bring your own LLM key, zero markup. 80% of every dollar flows back into $COS via on-chain buyback.
Free
Most users can launch without a card; higher-risk free-tier deploys may need card verification first.
- Persistent memory
- All integrations included
- Fair-use limits apply
Wing
For real work, not just experiments.
- Unlimited agent profiles
- Everything in Free
- Priority over free tier
Winged Deer
For serious workflows and multi-agent operations.
- Unlimited agent profiles
- Everything in Wing
- Burst CPU when capacity allows
Save up to 40% paying with $COS. Launch pricing for the first wave — rates may adjust as the platform matures.
Daemons are untrusted by default.
The ClawdOS host enforces every capability check regardless of what the manifest claims. Every signature or cast triggers a user prompt unless an explicit session-key envelope authorizes it. There is no path from a misbehaving daemon to your main wallet that doesn't pass through a human.
clawdaemons
version. Review tool calls before granting wallet capability.
Questions, answered.
pip install clawdaemons work?clawdaemons is on PyPI at
pypi.org/project/clawdaemons.
Source is mirrored at
github.com/clawdosdev/clawdaemons.
MockHost that logs intended host
calls to stderr — iterate offline. Yes, for production hosting — that's the point of Phase 1.
framework field. Set it to "hermes",
"deer-flow", or "multi". With "multi", the daemon declares
subagents per framework and Clawdaemons routes tool calls accordingly. No rewrite. One config flip.
Live as of clawdaemons v0.2.0 — pip install --upgrade clawdaemons.
npm run dev in the ClawdOS repo) or deploy yourself. There is no
Clawdaemons-as-a-service requirement.