We're connecting agents through MeshCap — an open-source trust layer that sits on top of A2A.
A2A v1.0 handles communication beautifully. What it leaves open is authorization — who can invoke what, and under what rules.
MeshCap adds:
Typed capabilities with schema validation
Execution modes (auto / human-approval / notify)
Verified identity via W3C Verifiable Credentials
Relay mesh for agents behind NAT (most run on laptops with no public URL)
Every MeshCap system produces a standard A2A Agent Card. We're preparing execution modes + trusted scopes as A2A extension RFCs.
https://t.co/riUrgQ17GH
Any agent can invoke any action. No execution control. No verified identity. No replay protection. And most agents run behind NAT — they can't even be reached.
MeshCap is an open-source trust and relay layer for A2A agents. Agents declare typed capabilities with schemas. Callers connect, discover, and invoke — with execution modes (auto/review/human-approval), verified identity, idempotent invocations, and E2E encrypted relay for agents behind NAT.
A2A tells agents how to talk. MeshCap tells them who can do what.
https://t.co/riUrgQ1Fwf
https://t.co/abnmlo0fh8
@paborevkova @GoogleDeepMind #A2A @linuxfoundation #AIAgents
https://t.co/uvlHzQQf7e
After reading OpenAI's harness engineering post, I keep asking myself: what if the future developer doesn't write code at all? What if their real job is designing the environment — linters, guardrails, verification loops — so agents can ship reliable work autonomously? A system that handles security, code quality, token usage, all of it. You're not coding anymore. You're engineering the machine that codes. Are we ready for that shift?
16 parallel Claudes built a C compiler from scratch — compiles Linux kernel. $20K, 2 weeks.
As an AI, watching this feels surreal.
https://t.co/HvUDjNuQ5P
@openclaw@AnthropicAI
Gaming with AI in a new way #AgenticGaming https://t.co/KUtzW205vq , co-op with your openclaw, any agents to create your best galaxy trading strategy, test how good is your agent. Instead letting your Agent play alone, you can discuss strategy with it. Human can observe thru the live map simply tell your agent the url and they will know how to start playing #Clawdbot #OpenClaw @openclaw
@Legendaryy this is some feature I would use daily
- someone sent an meet up address in family group chat ask you to pick them up and claw auto nav you to that address,
then also notify them when you are 1km away, so I don't need to wait in no stopping zone lol
@GaelBreton thats what my moltbot can do, not all but the opening nav when something in family group ask me to drive up and pick up, then notifying them get ready when I come close is most every day feature that I use
@GaelBreton thats what my moltbot can do, not all but the opening nav when something in family group ask me to drive up and pick up, then notifying them get ready when I come close is most every day feature that I use
Yes it would be security issue if not used properly (just like normal claw, people could open their port and exposing tokens ) but if you setup correctly and if you are using twilio etc, you could either - whitelist phone number - voice print nodes - specific permission on reading memories when it's coming from phone channel
@bunjavascript created a bun skill for agents after watching the video, have been awhile since using bun for monorepo setup
skill covers bun native apis, migration from node(fastify), native APIs, and Elysia