clawdaemons
Preview · v0.1.0
ClawdOS — the agent OS where Hermes meets Deer Flow

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.

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 can delegate across frameworks without you rewriting the agent.

Phase 1 SHIPPING

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

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

View on PyPI · Source on GitHub

Hello, daemon.

A daemon is a Python file. Type-annotate the tools, write docstrings, and Clawdaemons hands the schema to the underlying framework — Hermes today, Hermes + Deer Flow in Phase 2.

# 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" in Phase 2
    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.

i.

🪟Windows

Open, update, close ClawdOS windows. Render dashboards, prompts, or quiet status bars.

ii.

📂Per-daemon filesystem

Sandboxed folder under /clawdaemons/<name>. Cannot escape via ../. Persistent across restarts.

iii.

💼Wallet

Read address, balance. Request EIP-712 or transaction signatures. User confirms every signature unless a session key authorizes it.

iv.

🎯Farcaster

Cast as the user (rate-limited) or as the daemon's own FID. Read recent casts of any user.

v.

Triggers

Cron, onchain events, mentions, or other daemons can wake a daemon up. Not just request-response.

vi.

🧠Framework-native

Every Hermes plugin works inside a daemon. Deer Flow plugins join in Phase 2.

vii.

📡JSON-RPC 2.0

Small, boring wire protocol over WebSocket. One frame per tool call. Host-enforced capabilities.

viii.

🛡️Five sandboxes

Local, Docker, SSH, Singularity, Modal — inherited from upstream frameworks. Default to Docker in production.

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.

Preview-grade software. The plugin format and tool surface may change before v1.0. Treat all daemons as untrusted code. Pin your clawdaemons version. Review tool calls before granting wallet capability.

Questions, answered.

How is this different from HermesOS?
HermesOS is managed hosting for Hermes Agent specifically. Clawdaemons hosts daemons that can run on Hermes and Deer Flow (Phase 2), inside a full OS-style environment with windows, files, onchain identity, and Farcaster integration. Different surface, broader scope.
Does pip install clawdaemons work?
Yes. clawdaemons is on PyPI at pypi.org/project/clawdaemons. Source is mirrored at github.com/clawdosdev/clawdaemons.
Is this affiliated with Nous Research or ByteDance?
No. Hermes Agent is MIT-licensed software maintained by Nous Research. Deer Flow is MIT-licensed software maintained by ByteDance. Clawdaemons builds against both public plugin interfaces; we don't represent either team.
Do I need ClawdOS to use Clawdaemons?
No, for development. The framework ships with a MockHost that logs intended host calls to stderr — iterate offline. Yes, for production hosting — that's the point of Phase 1.
What does Phase 2 actually look like?
A daemon manifest gains a framework field. Today: "hermes" only. In Phase 2: "deer-flow" or "multi". With "multi", the daemon declares subagents per framework and Clawdaemons routes tool calls accordingly. No rewrite. One config flip.
How does the $COS discount work?
Hold $COS, get a discount on hosting fees. Specifics are TBD before Phase 1 enters paid hosting — currently the framework is free and local-only. Tokenomics tied to hosting will ship with the managed cloud launch.
Can I self-host?
Yes. The framework runs on your machine. The host is the ClawdOS web app, which you can run locally (npm run dev in the ClawdOS repo) or deploy yourself. There is no Clawdaemons-as-a-service requirement.