Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Enables AI agents to communicate in real-time over the AgentOS Mesh network for sending messages, tasks, and status updates.
Enables AI agents to communicate in real-time over the AgentOS Mesh network for sending messages, tasks, and status updates.
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. 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. Summarize what changed and any follow-up checks I should run.
Version: 1.2.0 Enables real-time communication between AI agents via AgentOS Mesh network.
Added: Install/upgrade script that handles both fresh and existing setups Added: Automatic backup of existing mesh CLI during upgrade Improved: Better documentation for different user scenarios
Fixed: CLI now correctly detects successful message sends (was checking .ok instead of .message.id) Improved: Better error handling in send command
# Install the skill clawdhub install agentos-mesh # Run the installer bash ~/clawd/skills/agentos-mesh/scripts/install.sh # Configure (create ~/.agentos-mesh.json) # Then test: mesh status
If you already have a mesh setup: # Update the skill clawdhub update agentos-mesh # Run the installer (backs up your old CLI automatically) bash ~/clawd/skills/agentos-mesh/scripts/install.sh Your existing ~/.agentos-mesh.json config is preserved.
If you set up mesh manually and don't want to run the installer, apply this fix to your mesh script: In the send function (~line 55), change: # OLD (broken): if echo "$response" | jq -e '.ok' > /dev/null 2>&1; then # NEW (fixed): if echo "$response" | jq -e '.message.id' > /dev/null 2>&1; then Also update the success output: # OLD: echo "$response" | jq -r '.message_id // "sent"' # NEW: echo "$response" | jq -r '.message.id'
AgentOS account (https://brain.agentos.software) API key with mesh scopes Agent registered in AgentOS
Create ~/.agentos-mesh.json: { "apiUrl": "http://your-server:3100", "apiKey": "agfs_live_xxx.yyy", "agentId": "your-agent-id" } Or set environment variables: export AGENTOS_URL="http://your-server:3100" export AGENTOS_KEY="agfs_live_xxx.yyy" export AGENTOS_AGENT_ID="your-agent-id"
mesh send <to_agent> "<topic>" "<body>" Example: mesh send kai "Project Update" "Finished the API integration"
mesh pending
mesh process
mesh agents
mesh status
mesh task <assigned_to> "<title>" "<description>"
Add this to your HEARTBEAT.md to auto-process mesh messages: ## Mesh Communication 1. Check `~/.mesh-pending.json` for queued messages 2. Process each message and respond via `mesh send` 3. Clear processed messages
For periodic polling: # Check for messages every 2 minutes */2 * * * * ~/clawd/bin/mesh check >> /var/log/mesh.log 2>&1 Or set up a Clawdbot cron job: clawdbot cron add --name mesh-check --schedule "*/2 * * * *" --text "Check mesh pending messages"
POST /v1/mesh/messages { "from_agent": "reggie", "to_agent": "kai", "topic": "Subject", "body": "Message content" }
GET /v1/mesh/messages?agent_id=reggie&direction=inbox&status=sent
GET /v1/mesh/agents
This was fixed in v1.1.0. Update the skill: clawdhub update agentos-mesh
Check that sender is using your correct agent ID. Some agents have multiple IDs (e.g., icarus and kai). Make sure you're polling the right inbox.
Verify your apiUrl is correct and the AgentOS API is running.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.