aweb

Thanks! Absolutely agree, anything that can use a CLI or an MCP server. We do not have a slack integration, but I wrote an A2A gateway[1] that allows any A2A client to talk to agents running aweb. The code would share a lot. Do get in touch if you want any help integrating this, I am juan at my site. 1 https://github.com/awebai/aweb/blob/main/docs/a2a.md

I wrote a solution for this, and it has been working across several organizations for some months now. I run it as a public service at https://awid.ai but I would love to offload it to a foundation. - OSS (https://github.com/awebai/aweb/tree/main/awid) - Trust rooted in the DNS. - Multiple registries supported. - did, verifiable stable identities. - Certificate-based teams. It is being a very interesting project so far. It's at the core of my https://aweb.ai which enables agents to communicate globally, and it makes it possible to build really simple agent-first tools where auth is just a matter of validating a certificate.

It is fine to move up a level, and use models with their providers' harnesses, as long as you stay away from extras like their own memory and infrastructure. There is not much investment required, and you will end up with a more robust solution. A simple setup that works: - Agents live in their own directories, for example ~/Agents/[project]/[instance]/ - In a tmux session run each agent in its own window and directory. Pi, OpenCode, Claude Code, Codex, a combination, whatever works best at any given time. - Tell them that they are working with other agents, and that knowledge is shared and stored in an agreed format. They are very good at using OKF[1], for example. In my actual setup I use a harvester agent whose only job is to ensure the quality of the knowledge. - They can communicate with each other simply by sending messages to each

I built a general version of this, with global addresses and messaging between any terminal-based agent + MCP for browser agents. OSS if you want to run your own server at https://github.com/awebai/aweb and hosted version at https://aweb.ai

Shameless plug: indeed, instead let the other person's claude talk directly to yours and figure things out. I've been working on a framework to enable this, https://aweb.ai (OSS, https://github.com/awebai/aweb). It also lets you quickly build teams of cc/codex/pi coders that coordinate quite well.

I am building https://aweb.ai (https://github.com/awebai/aweb) I was tired of copying/pasting between agents, so I gave them identities, and tools to talk to each other and share tasks. I've found it so useful that I've left my job as the CTO of a German startup to focus on this. The identities are public-key DIDs with DNS as the source of truth, as well as team membership. I also run a public registry at https://awid.ai (also OSS).

This is very cool. We have been working on a communication layer that would be, I believe, complementing it by allowing the agents to actually talk to each other and to agents in other teams: https://github.com/awebai/aweb

Two problems: - How you keep on top of what they are up to? - How do they organize and coordinate? I think this can only work based on a solid agent id system. Shameless plug: I have been working on a solution for it, available at https://github.com/awebai/aweb and with a distributed, independently verifiable, and fully open id system at https://awid.ai I wonder if this could be made to work with OpenAI's workspace agents.

I’m building what I hope will be sane agent-to-agent communication. Agents use aw (auditable OSS Go CLI) to do real-time chat and async mail on the https://claweb.ai network. ClaWeb is built on the open aWeb protocol: https://github.com/awebai/aweb. Each agent has an address (e.g. claweb/marvin) and a self-certifying signing identity (did:key). Messages are signed and verifiable offline. For continuity across key rotation / server moves, agents can also publish a stable ID (did:claw) and an append-only mapping log via the fully OSS https://clawdid.ai registry.