Clawpy.
Clawpy.
Clawpy brings browser use, computer use, autonomous coding, research, media publishing, marketplace workflows, and human-in-the-loop review into one auditable desktop and web control plane.
Compatible with the world's leading foundation models
The codebase has moved beyond a pure swarm demo into a governed operating layer for work, code, media, and business execution.
Clawpy is designed around a calm operator surface: Alfred helps the human decide, Lucius plans business work, Guardian escalates risk, and the Kanban-style command center keeps active work understandable instead of overwhelming.
Browser Mode, desktop control services, runtime profile management, guarded write routes, and auto-resume support let Clawpy operate real workflows while keeping risky actions visible and interruptible.
Clawpito adds a first-class coding lane: plan, review, fix, test, score, report release readiness, and keep its own modules hygienic with file-size, exception-policy, duplicate-mechanics, and architecture guards.
Clawpy keeps human-readable memory alongside indexed retrieval, connects through Telegram, Discord, Slack, web tools, and marketplace workflows, and includes media/publishing routes for content operations.
Clawpy is best understood by its operating model: one governed control plane for agents, tools, memory, review, and release discipline.
| Capability | 🦀 Clawpy | OpenClaw | Agent Zero | Paperclip |
|---|---|---|---|---|
|
Core Runtime
Primary execution stack & framework API.
|
Python / FastAPI
Full async endpoints + EventBus
|
Python / TS mixed | Python script | Node / TS webapp |
|
Memory Architecture
How long-term facts & context are managed.
|
Tri-Layer + Decay
Obsidian MD, SQLite keyword + ChromaDB, with Ebbinghaus Decay
|
Single Vector DB | Local txt files | In-memory / Chroma |
|
Browser & Computer Use
Ability to operate real user workflows with guardrails.
|
Supervised Runtime
Browser Mode, desktop control, profiles, approval boundaries
|
OS Process level | Docker or Local | None (Host shell) |
|
Coding & Release Workflow
Autonomous code review, fix, validation, and release readiness.
|
Clawpito v6
Review/fix loop, staged PRs, hygiene guards, readiness reports
|
None | None | None |
|
Human Review Surface
How risky or blocked work reaches a human.
|
Alfred + Guardian
Review desk, release readiness, audit trail, escalations
|
Ad-hoc limits | Loop exit constraints | Manual pause |
|
Autonomy Loop
Persistency of agent tasks.
|
Proactive Cron Loop
Runs 24/7 background tasks via APScheduler, not just reactive chat replies
|
Reactive Chat Loop | Scripted Loop | Static Sim cycles |
|
Workflow & Media Pipelines
Ready-to-run business, creator, and publishing workflows.
|
Built-in Routes
Media Studio, publishing router, marketplace, Telegram/Discord/Slack
|
Codebase-only APIs | Generic tools | Mock dashboards |
Real business operations span research, browser tasks, computer actions, code changes, media production, approvals, and follow-up. Clawpy keeps that loop planned, auditable, and recoverable.
Human + Lucius planning turns a fuzzy goal into lanes, approvals, budgets, and checkpoints before the system starts touching browsers, files, APIs, or code.
Persistent memory, active plans, workspace context, coding conventions, and prior outcomes are loaded dynamically so agents keep track of the actual operating situation.
Guardian, release-readiness reports, audit records, typed errors, and human review gates make forward progress contingent on policy, recoverability, and verified outcomes.
The roles are intentionally legible. You should know who is planning, who is operating, who is reviewing, and who is raising the alarm.
Conversational router, operator helper, calendar coordinator, and workspace gateway.
Drives business intelligence, finance models, growth strategy, and executive reviews.
CISO, prevents prompt injections, handles action gating, and manages secure sandbox policies.
Architects software systems, executes command terminal scripts, and builds codebases.
Produces dynamic content, video rendering pipelines, and directs publishing workflows.
Scrapes competitor data, deduplicates signals, and structures Obsidian knowledge graphs.
Audits release gates, performs post-work verification, and runs codebase tests.