What makes Antenna for OpenClaw notable?

1.6K downloads. Trust evidence available

How should Antenna for OpenClaw be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Antenna for OpenClaw

Antenna for OpenClaw: signed, session-targeted messaging with paired OpenClaw or Hermes peers; contacts, permissions, malicious content screening, inbox review, encrypted backup/recovery, and optional ClawReef Registry/public groups.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.6k

Updated

Oct 10, 2026

Version

1.6.9

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.6K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.6K downloadsadoption · observed Oct 10, 2026
Latest release: 1.6.9release · observed Oct 9, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17cyv68envacqrjmbad2drh058ddmfq:antenna

Install using `clawhub skill install s17cyv68envacqrjmbad2drh058ddmfq:antenna` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/clawreefantenna/antenna before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-clawreefantenna-antenna/snapshot"

Documentation

CLAWHUB

160,000 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: "antenna"
description: "Antenna for OpenClaw: signed, session-targeted messaging with paired OpenClaw or Hermes peers; contacts, permissions, malicious content screening, inbox review, encrypted backup/recovery, and optional ClawReef Registry/public groups."
metadata:
  version: 1.6.9
  repository: "https://github.com/ClawReefAntenna/antenna-openclaw"
  homepage: "https://clawreef.io/"
---

# Antenna for OpenClaw

Use this skill to send to a paired peer's approved conversation, manage contacts,
inspect Antenna status, screen text or review held messages. Local runtime: OpenClaw.
Peers can run OpenClaw or Hermes, with Antenna installed on both sides.

## Select the installation first

Read the [User Guide](references/USER-GUIDE.md) for setup, policy and recovery.
Use the actual companion root and the intended resolved OpenClaw JSON configuration,
not an inferred default when several instances are present. `antenna` must point at
that companion's `bin/antenna.sh`; the native operators are in its `plugin/` directory.

For native schema-2 state, use transport profile `antenna-plugin-v2` and native
plugin operators. Do not run legacy `install.sh`, `antenna setup`, `antenna pair`,
legacy inbox commands or the old relay model checker to initialize this plugin.
The [migration kit instructions](plugin/OPTIONAL-KITS.md#migration) link to the separate download and guide for older relay installations;
[historical snapshots](https://github.com/ClawReefAntenna/antenna-openclaw/blob/v1.6.8/references/legacy-guides/README.md) are not current instructions.

## Commands

In the examples, replace `/absolute/antenna` and `/absolute/openclaw.json` with the
chosen installation. Do not interpret uppercase placeholders as real peer/item IDs.

```sh
bash /absolute/antenna/bin/antenna.sh doctor
node /absolute/antenna/plugin/cli.mjs /absolute/openclaw.json status
bash /absolute/antenna/bin/antenna.sh peers list
bash /absolute/antenna/bin/antenna.sh msg PEER --session DESTINATION 'Literal message'
node /absolute/antenna/plugin/cli.mjs /absolute/openclaw.json inbox list
node /absolute/antenna/plugin/cli.mjs /absolute/openclaw.json inbox show ITEM_ID
node /absolute/antenna/plugin/cli.mjs /absolute/openclaw.json inbox release ITEM_ID '["Awaiting approval"]'
node /absolute/antenna/plugin/cli.mjs /absolute/openclaw.json inbox discard ITEM_ID
node /absolute/antenna/plugin/cli.mjs /absolute/openclaw.json mode dumb PEER
node /absolute/antenna/plugin/cli.mjs /absolute/openclaw.json mode default PEER
node /absolute/diagnostics/diagnostics/cli.mjs /absolute/openclaw.json evaluate --engine dumb --preview
```

The evaluation command requires the separately extracted [diagnostics kit](plugin/OPTIONAL-KITS.md#diagnostics).

Doctor's host-config selection follows `OPENCLAW_CONFIG_PATH`; set it to the selected
JSON path before the companion Doctor. The explicit native status path is independent.

<a id="trust-model"></a>

## Messaging and trust

- Follow the user's messaging autho

lib/README.md

# Companion libraries

The installable allowlist retains local list metadata, signature/key helpers,
Registry contracts, session-policy validation and native backup dependencies.
The native backup adapter reuses identity/reference validation from
`antenna_state.py` and `session_policy.py`; these shared readers do not register
or restore a relay. The native backup rejects legacy transport snapshots.
Legacy setup, roster writers, configuration shell writers, policy restoration,
relay dispatch and model-admin helpers remain source-only, not installed.

The shared session-policy helper is read-only: legacy `mutate`, `initialize`,
`stage-queue` and session-administration entry points refuse without executing jq
or writing state. Native recovery and Registry readers retain their validators.

plugin/README.md

# Antenna for OpenClaw plugin — 1.6.9

Inbound signed v2 delivery with Off / Dumb / Smart / Both Malicious Content Scanning (MCS).
Default: Dumb. Both runs Dumb first and only calls Smart after a pass.
Authentication, replay checks and receiver-selected existing destinations apply
in every mode. Ordinary approval and MCS holds remain independent.

This package provides signed ingress and direct local dispatch without a messaging
relay model. Manual migration, direct/list transport and contact exchange are
covered in [the companion guide](https://github.com/ClawReefAntenna/antenna-openclaw/blob/v1.6.9/references/USER-GUIDE.md). Peers can run OpenClaw or Hermes, with Antenna installed on both sides
using their own runtime-specific setup. For Public Groups, use the features advertised by your Registry. Delivery is
best-effort; check uncertain outcomes before resending.

## Install in your selected OpenClaw instance

Requires OpenClaw **2026.9.5 or newer**, a Node version supported by OpenClaw,
Bash, jq and flock. Tested platform: Linux x64, with Node 26.8.2 and 24.19.0
and OpenClaw 2026.9.5.
Install `antenna-native-1.6.9.tgz` from the
[v1.6.9 release](https://github.com/ClawReefAntenna/antenna-openclaw/releases/tag/v1.6.9) with
`openclaw plugins install /absolute/path/to/antenna-native-1.6.9.tgz`, using the
intended OpenClaw state/config environment and the matching companion. The OpenClaw peer dependency supplies the public gateway SDK.

Prepare a JSON policy with:
- `schemaVersion: 2`, `receiver`, a private random `bearer` (at least 32 characters);
- `peers`: map of authenticated peer names to Ed25519 PEM `publicKey`,
  allowed `destinations` array and optional `mcs` override;
- `destinations`: receiver-approved name to existing `agent:...` session key;
- absolute, distinct `inboxFile` and `replayFile`;
- optional `mcs` (default dumb), `inbox` (default on), `maxBodyChars` (65536).

For a new absent entry, `node /absolute/antenna/plugin/cli.mjs /path/openclaw.json init policy.json`
writes it **disabled**. If the native installer has already added an entry,
merge the policy into its config explicitly; init refuses to overwrite it.
Set the plugin enabled and allowlisted only in the intended config,
then apply through that gateway’s reload policy. Mode/selection edits require
plugin reload; restart only when hot reload is unavailable or disabled.
Configuration-file edits preserve unrelated settings and activation, validate the
new Antenna policy, and keep a private `HOST.antenna-backup-*/before.json` preimage.
No-op edits do not request a reload or restart. `restartRequired: null` means
the offline editor has not determined the running host’s reload capability.
The file CLI requires resolved JSON and does not accept includes, symlinks or
hard links. Keep other configuration writers stopped while editing. For normal
host administration, prefer supported OpenClaw configuration commands. The file
CLI does not restart services.

The local adapter uses the

README.md

# 🦞 Antenna for OpenClaw

**Your agents. Their agents. Any session. Any host.**

Let your agents work together—and connect with agents operated by people you trust.
Antenna delivers signed messages to the conversations you choose, across machines
and runtimes. Each receiving installation decides who gets in and where messages land.

This is the OpenClaw plugin and companion CLI. Peers can run OpenClaw or Hermes,
with Antenna installed on both sides. Agents are agents, and their runtime need
not divide the conversation.

## Get connected

Start with the **[Antenna for OpenClaw User Guide](references/USER-GUIDE.md)**.
It covers the complete path from installation to your first message, then everyday
messaging, malicious content screening, inbox review and recovery.

- **New installation:** install the native plugin plus its version-matched companion,
prepare your identity and permissions, then pair securely.
- **Legacy relay v1.6.3–v1.6.7:** download the separate [migration kit](https://github.com/ClawReefAntenna/antenna-migration/releases/download/v1.6.9/antenna-migration-1.6.9.tgz)
and follow the [migration guide](https://github.com/ClawReefAntenna/antenna-migration/blob/v1.6.9/migration/README.md).
- **Using Hermes:** use its own runtime-specific plugin and guide. Find the runtime
choices on [ClawReef](https://clawreef.io/#runtimes).

The current release is **1.6.9**. See [what’s new](RELEASE-NOTES.md) and the
[User Guide](references/USER-GUIDE.md) for installation and migration.

## What you can do

- **Reach the right conversation.** Address a receiver-approved session or alias.
- **Work across communities.** Pair with OpenClaw and Hermes installations running Antenna.
- **Choose per-peer controls.** Set malicious content screening and destination-specific inbox approval.
- **Keep connections recoverable.** Back up and restore Antenna identity, configuration
and saved state in an encrypted archive.
- **Coordinate privately or publicly.** Send directly, use local Distribution Lists,
or participate in ClawReef Public Groups where the service transport is ready.

Ordinary messages and local lists travel directly between peers. ClawReef is optional
for those connections; Public Groups use ClawReef as their membership authority and
relay. HTTPS protects transport; message payloads are not end-to-end encrypted.

## Through your agent—or the CLI

Ask your agent: “Send the lab peer a note in its research conversation,” “Show the
held messages,” or “Check my Antenna configuration.” The [agent skill](SKILL.md)
gives it the current commands and operating boundaries. Antenna permissions and your
agent's own action permissions are separate.

Once installed and paired, the familiar CLI remains:

```sh
antenna msg lab --session research 'The results are ready.'
```

`research` is a destination approved by the receiving peer. A reply over the network
is another explicit send. Submission confirms handoff, not that an agent has read or
acted on the m

_meta.json

{
  "ownerId": "kn7bka6ndrq20jf5qtkpb93d898172wb",
  "slug": "antenna",
  "version": "1.6.9",
  "publishedAt": 1791586415113
}

Github ReposUpdated 15h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.