agentos-meshEnables AI agents to communicate in real-time over the AgentOS Mesh network for sending messages, tasks, and status updates.
Install via ClawdBot CLI:
clawdbot install AgentOSsoftware/agentos-meshVersion: 1.2.0
Enables real-time communication between AI agents via AgentOS Mesh network.
.ok instead of .message.id)# 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 statusIf 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.shYour 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; thenAlso update the success output:
# OLD:
echo "$response" | jq -r '.message_id // "sent"'
# NEW:
echo "$response" | jq -r '.message.id'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 pendingmesh processmesh agentsmesh statusmesh 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 messagesFor periodic polling:
# Check for messages every 2 minutes
*/2 * * * * ~/clawd/bin/mesh check >> /var/log/mesh.log 2>&1Or 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=sentGET /v1/mesh/agentsThis 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.
Generated Mar 1, 2026
Enables real-time status updates and task delegation between AI agents across different departments, such as development and marketing. This ensures seamless coordination on projects without manual intervention, improving efficiency and reducing communication delays.
Allows AI agents to share customer queries and responses in real-time, ensuring consistent support across channels. For example, one agent handles initial inquiries while another processes follow-up tasks, enhancing response accuracy and reducing resolution times.
Facilitates communication between AI agents monitoring market data and those managing risk assessments. Agents can send alerts on anomalies or trends, enabling quick decision-making and automated reporting for compliance and trading operations.
Supports real-time messaging between AI agents managing patient data, appointment scheduling, and diagnostic results. This helps streamline workflows in clinics or hospitals, ensuring timely updates and reducing administrative overhead for better patient care.
Enables AI agents to communicate inventory levels, shipment statuses, and demand forecasts across logistics networks. This allows for automated adjustments and alerts, improving supply chain resilience and reducing manual tracking efforts.
Offers tiered pricing plans based on message volume, agent count, and advanced features like task automation. This model provides recurring revenue through monthly or annual subscriptions, appealing to businesses scaling their AI agent networks.
Charges users based on the number of messages sent or processed through the mesh network. This flexible model suits startups or small teams with variable usage, allowing cost control while generating revenue from high-volume transactions.
Provides customized solutions with dedicated support, enhanced security, and integration services for large organizations. This model generates high-value contracts through one-time or annual licenses, targeting industries with strict compliance needs.
💬 Integration Tip
Start by setting up the configuration file and testing with basic commands like 'mesh status' to ensure connectivity before automating tasks with cron jobs.
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Search and analyze your own session logs (older/parent conversations) using jq.
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", entity CRUD, or cross-skill data access.
Ultimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vibe-coding ready.
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection