omniwire（omniwire 控制）

OmniWire v3.5.0 — Mesh Control for AI Agent Swarms

88 MCP tools. 12 categories. Every machine, one agent, zero friction.

OmniWire is the infrastructure layer for AI agent swarms. It connects your entire mesh (VPS, laptops, Raspberry Pis, Docker hosts) into a single controllable surface with 88 tools spanning execution, A2A protocol, OmniMesh VPN, CyberSync, web scraping, firewall management, CDP browser automation, and more.

You: check disk and container status on all servers

Agent: [omniwire_broadcast + omniwire_docker — parallel across all nodes]

  contabo  | 10.0.0.1 | ONLINE | 78ms  | disk=16% | containers: 12 running
  kali     | 10.0.0.2 | ONLINE | 91ms  | disk=34% | containers: 4 running
  rpi      | 10.0.0.3 | ONLINE | 112ms | disk=20% | containers: 2 running

What It Does

Setup — 3 Steps

Step 1: Install OmniWire

AGENT: Run this via exec. User just clicks Approve.

npm install -g omniwire@latest

Works on: Linux (x64, ARM64, ARMv7), macOS (Intel + Apple Silicon), Windows (x64).

Step 2: Configure Your Mesh

Create the mesh config. Ask the user for their server details:

AGENT: Ask the user: "What servers do you want to control? For each one I need: - A name (e.g., contabo, kali, rpi) - IP address or hostname - SSH user (usually root) - SSH key filename in ~/.ssh/ (e.g., id_ed25519) - Role: storage, compute, gpu+browser, or leave blank"

Then create the config:

mkdir -p ~/.omniwire
cat > ~/.omniwire/mesh.json << 'EOF'
{
  "nodes": [
    {
      "id": "contabo",
      "host": "10.0.0.1",
      "user": "root",
      "identityFile": "id_ed25519",
      "role": "storage",
      "tags": ["vps", "docker"]
    },
    {
      "id": "kali",
      "host": "10.0.0.2",
      "user": "root",
      "identityFile": "id_ed25519",
      "role": "compute",
      "tags": ["kali", "pentest"]
    }
  ],
  "cyberbase": {
    "host": "10.10.0.1",
    "port": 5432,
    "database": "cyberbase",
    "user": "cyberbase"
  }
}
EOF

Step 3: Verify

echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1"}}}' \
  | omniwire --stdio --no-sync 2>/dev/null | head -1

Should respond with omniwire v3.5.0. Done.

Transport options:

Usage Examples

Execute commands anywhere

You: restart nginx on contabo

Agent: [omniwire_exec node=contabo command="systemctl restart nginx"]
  OK — nginx restarted (0ms)

You: run uptime on every server

Agent: [omniwire_broadcast command="uptime"]
  contabo  | up 42 days, 3:21
  kali     | up 7 days, 11:04
  rpi      | up 2 days, 0:15

Transfer files between nodes

You: copy the pentest report from kali to contabo

Agent: [omniwire_transfer_file src_node=kali dest_node=contabo src=/root/report.pdf dest=/var/reports/]
  Transferred 2.4MB — LZ4 compressed — 83ms

Transfer modes (auto-selected):

• SFTP for files under 10MB
• netcat + LZ4 for 10MB–1GB
• aria2c for files over 1GB (16 parallel connections)

Docker management

You: what containers are running on contabo?

Agent: [omniwire_docker node=contabo action=ps]
  12 running — neo4j, postgres, omnibus-hub, kali-htb, omniwire-events...

You: pull and start the latest omniwire-events image

Agent: [omniwire_container node=contabo action=pull image=omniwire-events:latest]
  Pulled. Starting...
  ✓ omniwire-events running (healthy)

Monitor mesh health

You: how are all my servers doing?

Agent: [omniwire_mesh_status]

  contabo  | 10.0.0.1 | ONLINE | 78ms  | load=1.2 | mem=31% | disk=16%
  kali     | 10.0.0.2 | ONLINE | 91ms  | load=0.4 | mem=19% | disk=34%
  rpi      | 10.0.0.3 | ONLINE | 112ms | load=0.7 | mem=22% | disk=20%

VPN switching

You: switch to Mullvad on the kali node

Agent: [omniwire_vpn node=kali action=connect provider=mullvad country=nl]
  Connected — Netherlands exit — mesh routes preserved
  New IP: 185.65.134.x

Supported providers: Mullvad, OpenVPN, WireGuard, Tailscale. OmniMesh routes are protected during VPN switches.

Web scraping with Cloudflare bypass

You: scrape the pricing table from example.com

Agent: [omniwire_scrape node=contabo url=https://example.com/pricing selector=".pricing-table"]
  Scraped 4.2KB — Scrapling engine — Cloudflare bypassed
  [returns structured data]

A2A agent messaging

You: send a task to the pentest agent on kali

Agent: [omniwire_agent_task node=kali agent_id=pentest-agent task={type:"scan", target:"192.168.1.0/24"}]
  Task queued — ID: task_abc123

Agent: [omniwire_blackboard action=watch key=task_abc123/result]
  Result ready: {hosts: 12, open_ports: [...]}

COC — Unified CyberBase + Obsidian + Canvas sync

You: COC save — OmniWire v3.5.0 deployed with 88 tools

Agent: [omniwire_coc action=save note="OmniWire v3.5.0 deployed with 88 tools"]
  Saved to CyberBase (knowledge table)
  Mirrored to Obsidian vault: CyberBase/omniwire-v350.md
  Canvas node updated: CyberBase MindMap.canvas
  ✓ All 3 sync targets confirmed

Full Tool Reference

<details> <summary><strong>Execution (6 tools)</strong></summary>

</details>

<details> <summary><strong>Agentic / A2A Protocol (13 tools)</strong></summary>

</details>

<details> <summary><strong>Files (6 tools)</strong></summary>

</details>

<details> <summary><strong>Monitoring (4 tools)</strong></summary>

</details>

<details> <summary><strong>System / DevOps (14 tools)</strong></summary>

</details>

<details> <summary><strong>Network / VPN (7 tools)</strong></summary>

</details>

<details> <summary><strong>Security (6 tools)</strong></summary>

</details>

<details> <summary><strong>CyberSync (9 tools)</strong></summary>

CyberSync provides bi-directional config sync for 6 AI tools: Claude Code, OpenCode, OpenClaw, Codex, Gemini, PaperClip. All sensitive files encrypted with XChaCha20-Poly1305 at rest.

</details>

<details> <summary><strong>Knowledge (2 tools)</strong></summary>

</details>

<details> <summary><strong>OmniMesh (3 tools)</strong></summary>

OmniMesh is OmniWire's built-in WireGuard mesh manager. It provisions, rotates keys, and manages peer routing automatically.

</details>

<details> <summary><strong>Events (1 tool)</strong></summary>

</details>

<details> <summary><strong>CDP Browser (1 tool)</strong></summary>

omniwire_cdp provides 18 browser actions via a persistent Docker Chrome instance on any node. Sessions persist between calls. Cookies auto-exported in JSON + Header String + Netscape format.

</details>

<details> <summary><strong>Utilities (10+ tools)</strong></summary>

</details>

Performance

Encryption: AES-128-GCM for transport, XChaCha20-Poly1305 for at-rest sync items. Compression: LZ4 for transfers.

Architecture & Platform Support

No native compilation. Pure JavaScript + SSH2. npm install -g omniwire works everywhere Node.js 18+ runs.

Transports: stdio (MCP standard), SSE port 3200, REST port 3201, Events/WebSocket port 3202.

Security

Agent Instructions

When to use OmniWire tools

Use OmniWire when the user:

• Mentions servers, VPS, nodes, mesh, or "my machines"
• Wants commands run remotely or on all servers
• Needs files read, written, or transferred between nodes
• Asks about Docker, services, processes, or system health on remote nodes
• Wants to switch VPN, manage firewall rules, or handle certs
• Mentions "scrape", "browser", "CDP", or web automation on a remote node
• Wants to sync configs, save memory, or COC/save something
• Uses agent-to-agent workflows (A2A, blackboard, task queues)
• Needs TOTP codes, cookies, or security audit
• Mentions "COC", "Save to CyberBase", "Obsidian", or canvas sync

How to pick the right tool

Node selection defaults

If the user doesn't specify a node:

• File storage, databases, Docker → node with role: "storage"
• Security/pentest tools → node with tag "kali" or "pentest"
• GPU / display / browser → node with role: "gpu+browser"
• Heavy compute → node with role: "compute"
• Background task dispatch → omniwire_bg with any available node
• If ambiguous, ask: "Which server should I run this on?"

Background mode

All 88 tools support background: true. Use it for:

• Any operation expected to take > 5 seconds
• Builds, installs, deploys, large transfers
• Scraping and CDP sessions
• Long-running pipelines

omniwire_exec(node="contabo", command="apt upgrade -y", background=true)
→ returns task_id immediately
→ poll with omniwire_bg(action="poll", task_id="...")
→ get result with omniwire_bg(action="result", task_id="...")

Error handling

• If a node is offline, report it and offer alternatives
• If exec fails, show stderr and suggest fixes
• If transfer fails, retry with a different mode (SFTP → LZ4 → aria2c)
• If VPN connects but mesh breaks, restore mesh routes automatically (built-in)
• For persistent shell failures, use omniwire_shell with a new session_id

OpenClaw + PaperClip Integration

OmniWire is the primary infrastructure backend for OpenClaw agents and PaperClip workflows.

OpenClaw

OpenClaw agents use OmniWire for all remote operations. The skill is auto-loaded when OpenClaw detects omniwire in the installed MCP servers. Agents can:

• Execute tasks across the mesh without user intervention
• Use the A2A protocol to coordinate multi-agent workflows
• Persist state via the blackboard and knowledge base
• Dispatch background jobs and collect results asynchronously

PaperClip

PaperClip workflows integrate with OmniWire via CyberSync. Any workflow that produces knowledge, memory, or config changes can route through omniwire_coc for unified persistence across CyberBase, Obsidian vault, and Canvas.

COC workflow from PaperClip:

1. Workflow completes → calls omniwire_coc(action="save", ...)
2. Saved to CyberBase knowledge table with pgvector embedding
3. Mirrored to Obsidian vault as .md file
4. Canvas node created/updated in CyberBase MindMap.canvas
5. All nodes confirmed in one response

Sync coverage — CyberSync 6 AI tools

Links

• GitHub: https://github.com/VoidChecksum/omniwire
• NPM: https://www.npmjs.com/package/omniwire
• Issues: https://github.com/VoidChecksum/omniwire/issues
• License: GPL-3.0-only

*OmniWire v3.5.0 — 88 tools. Every machine. One agent.*