Overview
Clawdi positions itself as the layer above the agent framework, not another framework competing with OpenClaw, Hermes, or Claude Code. Each user gets a hardware-encrypted cloud workspace (running on Intel TDX) where memory, API keys, skills, cron jobs, and app connections persist independently of whichever agent engine is currently driving the work.
Built by Phala Network and shipped with a Chrome extension and an MIT-licensed CLI, Clawdi targets developers and operators who keep rebuilding the same scaffolding every time they switch between Claude Code, OpenClaw, Hermes, or a homegrown agent. The pitch: build locally with one engine, sync to the cloud, then continue from any other engine without losing your setup.
Key Features
- Framework-agnostic agent runtime — Run AI agents like OpenClaw, Hermes, Claude Code, Codex, or your own (BYOA) inside the same workspace, so a switch in engines doesn't require rebuilding memory or reconnecting integrations.
- Hardware-encrypted workspaces — Every workspace lives inside an Intel TDX TEE-protected VM, which is meaningful for users handling production credentials or regulated data.
- 500+ app integrations via Composio — Email triage, calendar, CRM, analytics, web research, and similar workflows plug in without bespoke connector work.
- 13+ messaging channels — Telegram, WhatsApp, Slack, and others can serve as agent front-ends, useful for non-CLI users or team-facing assistants.
- ClawHub skill marketplace — Shared skills can be installed and synced across supported agents; verify current ClawHub behavior in the official docs before relying on specific install or self-evolving flows.
- Deep memory and session continuity — Conversations and learned context carry across sessions and across engines, addressing the most common pain when switching frameworks.
- Browser automation via Chrome extension — The Clawdi Browser extension (v0.1.2 at launch) bridges Chrome to the cloud agent over a debugger-permission relay, so the agent can actually click, read, and act on pages.
- Voice mode and TTS — Lower-friction interaction surface for non-developer team members or hands-free workflows.
How to Get Started
- Install the CLI:
npm install -g clawdi(the CLI itself is MIT-licensed and runs locally). - Sign in and create a workspace: A free Freemium tier provisions a 2 vCPU / 4 GB / 20 GB workspace with 5,000 monthly credits.
- Pick or import an agent: Claude Code, OpenClaw, Hermes, Codex, or your own (verify current GitHub star counts at the time of reading — these change quickly).
- Install the Chrome extension (optional): Adds browser automation to the workspace via a one-click connect flow.
- Build locally, sync, continue anywhere: Skills, keys, and memory persist server-side; switch frameworks without rewiring.
Pricing & Plans
Clawdi uses a credit-metered freemium model. The public pricing page lists monthly prices, plus quarterly billing at 10% off and annual billing at 20% off. Credits cover compute and integration calls; resources scale with the tier.
| Plan | Price | Monthly credits | Workspace resources |
|---|---|---|---|
| Freemium | $0 / month | 5,000 | 2 vCPU · 4 GB RAM · 20 GB storage |
| Pro | $29 / month | 30,000 | 2 vCPU · 4 GB RAM · 20 GB storage |
| Max | $99 / month | 120,000 | 4 vCPU · 8 GB RAM · 40 GB storage |
| Enterprise | Custom | Custom | SSO, audit logs, custom regions |
The GitHub repo ships the MIT-licensed CLI alongside a FastAPI backend, Next.js dashboard, database schema, migrations, and docs; hosted Clawdi Cloud — workspaces, credits, and managed Composio integrations — remains the paid, credit-metered offering. So this is freemium, not fully open.
Community & Ecosystem
Clawdi did not appear in a vacuum. Its developer, Phala Network, ships OpenClaw (a personal AI assistant project) and operates in the broader agent ecosystem alongside the Hermes Agent project. Live GitHub star counts are not pinned here because they change quickly — check the repos directly for current numbers. ClawHub serves as the community skill marketplace, with skills authored by users and updated as agents run more tasks. Launch-day numbers from the official site cite 5,052 users and 1,672 deployments, which puts Clawdi well past a pre-launch shell but still squarely in early-adopter territory.
Best For
- Developers who currently maintain memory, prompts, and integrations separately for Claude Code, OpenClaw, or Hermes and want a single source of truth.
- Solo operators running agents that touch credentials (Gmail, Slack, GitHub) who care about hardware-level isolation.
- Teams piloting multi-agent setups that need to swap engines mid-flight without re-onboarding the agent.
- Builders who want to ship browser-automation agents but don't want to maintain a Playwright stack themselves.
- Researchers comparing agent engines or AI agent protocols who need a fair, side-by-side baseline (same workspace, same memory, different engine).
FAQ
Is Clawdi a new agent framework, or something different?
Clawdi is explicitly not a framework. It is the runtime/environment layer that sits above frameworks. The agent engine (OpenClaw, Hermes, Claude Code, Codex, or BYOA) is swappable; Clawdi keeps memory, skills, integrations, and credentials stable underneath.
Is Clawdi open source?
Partly. The CLI is MIT-licensed and runs locally. The cloud workspaces, credit-metered runtime, ClawHub marketplace, and managed Composio integrations are part of the freemium/paid platform. For purely OSS memory components, adjacent projects like MemOS explore that space separately.
What does the Freemium tier cover?
A free workspace with 2 vCPU, 4 GB RAM, 20 GB storage, and 5,000 monthly credits. Sufficient for evaluation; heavier browser automation or multi-tool workflows may require Pro or Max depending on actual credit burn.
Why does Clawdi run on Intel TDX?
Intel TDX is a Trusted Execution Environment that provides hardware-level memory encryption and integrity. For agents that hold OAuth tokens, API keys, and live access to email, calendars, and source repos, this raises the bar on credential isolation versus shared cloud VMs.
Which agent frameworks are supported today?
Officially listed: OpenClaw, Hermes Agent, Claude Code, Codex, plus a Bring Your Own Agent (BYOA) path. The roster will likely grow as the adapter layer matures.
Do I need the Chrome extension to use Clawdi?
No. The extension only adds browser automation — clicking, reading pages, and acting on tabs from the cloud agent. Workflows that don't need a real browser can run without it.
How does the credit system work?
Credits cover compute and integration calls. The free tier ships 5,000/month; Pro ships 30,000; Max ships 120,000. The exact per-call cost is set by the platform and may change as workloads stabilize — verify in the dashboard before committing to a plan.
Where is Clawdi developed?
By Phala Network — the same team behind OpenClaw — and the developer contact on the Chrome extension is paco@phala.network. Phala has a long track record in confidential computing, which explains the TDX choice.
