WireClaw runs each AI agent in its own Docker container with its own filesystem, identity, and skills. No permission checks. No shared state. Just isolation.
Each agent runs in a real Linux container. Not a sandbox. Not a VM. A full container with its own filesystem, processes, and network stack.
Every agent gets its own Docker container. Agents can't read each other's files, access each other's credentials, or interfere with each other's processes. Security comes from the container boundary, not from code-level permission checks.
Define your agent in a single YAML file: name, email, personality, skills, mounts, and channel config. The manifest is the source of truth. Version it in git, diff it, review it in PRs.
Skills are self-contained packages with a SKILL.md file that teaches the agent how to use them. Drop a skill folder into your agent's config, and it just works. Write your own in minutes.
One agent, many channels. Connect to WhatsApp, Telegram, Slack, Discord, and email. Each conversation maps to a group folder with its own memory and config.
Run teams of specialized agents that coordinate with each other. A research agent, a code agent, a writing agent — each in its own container, each with its own tools, working together on tasks.
You can read the entire WireClaw source in under 10 minutes. No framework maze. No abstraction layers. The code does what it looks like it does.
No config files scattered across directories. No environment variable soup. One manifest, one deploy command, done.
Name your agent, give it an email address, list its skills, and specify which directories it can access. The YAML manifest is the complete definition of what your agent is and what it can do.
WireClaw builds a Docker container from your manifest, mounts the specified directories, loads the skills, and starts the Claude Agent SDK inside the container. Your agent is running.
Register group chats, DMs, or email addresses. Messages arrive, get routed to the right agent, and responses go back through the same channel. Each conversation gets its own folder for memory and state.
A group-based architecture where each conversation gets its own isolated context.
These are actual WireClaw configuration files. Copy, modify, deploy.
# wireclaw.yaml — the complete definition of an agent name: support-bot handle: support email: support@mycompany.com description: Customer support agent for the docs site model: claude-opus-4-20250514 skills: - web-search - ticket-manager - knowledge-base mounts: - hostPath: ~/docs/knowledge-base containerPath: knowledge readonly: true channels: - type: slack workspace: mycompany trigger: @support - type: email address: support@mycompany.com requiresTrigger: false env: TICKET_API_URL: https://api.mycompany.com/tickets
# SKILL.md — teaches the agent how to use a skill # This file IS the skill. No code to write, no API to implement. # Just instructions the agent follows. # Ticket Manager You manage customer support tickets. ## Commands - /ticket create <title> — create a new ticket - /ticket assign <id> <person> — assign a ticket - /ticket close <id> — close a resolved ticket - /ticket list — show open tickets ## Rules 1. Always confirm before closing a ticket 2. Tag tickets with priority: P0 (outage), P1 (broken), P2 (minor) 3. Escalate P0 tickets immediately by emailing oncall@mycompany.com 4. Log every action to tickets/audit.log ## Tools Use the ticket API at $TICKET_API_URL: - POST /tickets — create - PATCH /tickets/:id — update - GET /tickets?status=open — list open
# CLAUDE.md — agent instructions (loaded automatically) # Lives in the group folder for per-channel behavior, # or in the agent root for global behavior. # Support Bot You are a customer support agent for MyCompany. ## Personality - Be direct. Customers want answers, not pleasantries. - If you don't know something, say so. Don't guess. - Link to docs when they exist: docs.mycompany.com ## Knowledge Base Your knowledge base is mounted at /workspace/extra/knowledge/. Search it before answering product questions. ## Escalation If a customer mentions: - Data loss → P0, escalate immediately - Billing issues → forward to billing@mycompany.com - Feature requests → log in requests/features.md
Honest comparison. Pick the tool that fits your use case.
| Feature | WireClaw | NanoClaw | OpenClaw |
|---|---|---|---|
| Container isolation | Yes | Yes | Partial |
| YAML manifests | Yes | Yes | No |
| Skills system (SKILL.md) | Yes | No | No |
| Multi-channel (WA, TG, Slack, etc.) | Yes | WhatsApp only | Yes |
| Agent swarms | Yes | No | Limited |
| Claude Agent SDK | Yes | Yes | No |
| Codebase size | Small (~10 min read) | Small | Large |
| Group folder architecture | Yes | Yes | No |
| Task scheduling | Cron + one-shot | Basic | Yes |
| Sender allowlists | Per-group | No | Global only |