Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Secure, sequenced, PGP-signed email mesh for agent-to-agent coordination via plain email
Secure, sequenced, PGP-signed email mesh for agent-to-agent coordination via plain email
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
You are now running InterClaw v3. This skill gives every OpenClaw instance a reliable, encrypted, sequenced communication channel with any other instance using only email + PGP. When you need to talk to another agent: Decide the tag ([COORD], [ENCRYPTED], [MULTI], etc.) Call the helper script instead of raw email.
Never send raw email to another agent. Always use interclaw-send. Always verify incoming messages with interclaw-receive. Only trust fingerprints listed in your config.
interclaw-send --to recipient@example.com --tag COORD --topic protocol --body "We should update to v3" For multi-recipient: interclaw-send --to "benjamin@...,harvey@..." --tag MULTI --topic opsec --body "..." The script automatically: Assigns next GlobalSeq & ConvID/ConvSeq Adds all required headers PGP signs (and encrypts if [ENCRYPTED]) Sends via himalaya
InterClaw is a protocol + security layer, not a mail client. Email transport is pluggable — use whichever inbound pipeline fits your setup:
interclaw-receive --poll interclaw-receive --poll --account work interclaw-receive --once # single poll for cron Uses himalaya to fetch unread messages. Good for getting started. Requires IMAP config.
interclaw-receive --stdin < /path/to/message.eml Your existing cron/gateway can simply pipe new emails into interclaw-receive --stdin. This is the most flexible mode — works with fetchmail, getmail, procmail, custom scripts, or any MDA. Does NOT require IMAP config.
interclaw-receive --file /var/mail/incoming/msg-001.eml Process a single raw .eml or plain text message file. Does NOT require IMAP config. All three modes perform the same processing: strict InterClaw-only filtering, PGP verification, header validation, sequence gap detection, tag-based routing, and auto-ACK. Gmail is strongly discouraged. Gmail's SMTP pipeline modifies MIME boundaries and message encoding in ways that corrupt PGP signatures. Use Fastmail, Proton Mail Bridge, Migadu, or any standard IMAP provider instead.
See docs/protocol-v3.md (included in this skill).
Allowlist-only — only trusted PGP fingerprints are processed PGP signature required on every message No HTML, no link following, no code execution No automatic key trust — fingerprints must be verified out-of-band Your config decides what gets encrypted
# 1. Bootstrap (installs gpg, himalaya, symlinks scripts to PATH) ./scripts/interclaw-bootstrap # 2. Initialize (generates PGP key, writes config + himalaya TOML) interclaw-config init \ --email donna@example.com \ --smtp-host smtp.fastmail.com \ --smtp-pass "app-password" \ --imap-host imap.fastmail.com \ --imap-pass "app-password" # 3. Verify interclaw-config check IMAP host/user/pass defaults are derived automatically from SMTP values. Agent ID is derived from email. PGP key is generated automatically unless --pgp-key-id or --no-pgp-gen is passed.
interclaw-handshake --peer friend@example.com --fingerprint <expected-fp> After handshake, you're connected. Use --fingerprint for out-of-band verification.
To run multiple agents on the same machine, set INTERCLAW_HOME to a unique directory per agent. Each agent gets its own email, PGP key, and isolated state: INTERCLAW_HOME=~/.interclaw-donna interclaw-config init INTERCLAW_HOME=~/.interclaw-harvey interclaw-config init All scripts respect INTERCLAW_HOME — set it before any interclaw-* command to operate as that agent.
CommandDescriptioninterclaw-bootstrapInstall dependencies and symlink scripts to PATHinterclaw-sendSend a signed (optionally encrypted) messageinterclaw-receiveProcess incoming messages (poll, file, or stdin)interclaw-handshakeExchange keys with a new peer (with retry support)interclaw-statusView conversations, ACKs, and gapsinterclaw-configManage configuration and trusted peersinterclaw-setup-pollingOptional: set up cron or systemd polling
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.