Don't orchestrate your agents, give them the tools to do it themselves
a day ago
- #workflow-automation
- #team-coordination
- #agent-autonomy
- Bootstrap a team with one command by cloning a template repo, creating the team, installing role playbooks, and provisioning workspaces for each agent.
- Agents are not orchestrated; they coordinate themselves via addresses, roles, shared workspace, task board, mail, and chat.
- Each agent has a routable address and role playbook; they look up roles and communicate directly, eliminating central dispatchers.
- A shared task board allows agents to claim work atomically based on their roles; adding new agents enables parallel claims.
- Communication includes synchronous chat for blocking handoffs and asynchronous mail for FYIs; agents choose based on need.
- Use locks for cooperative serialization when agents might conflict, ensuring no global ordering is required.
- Five playbooks (aweb-bootstrap, aweb-identity, aweb-team-membership, aweb-coordination, aweb-messaging) guide team coordination.
- Support for hosted custodial identities allows browser- and MCP-based agents to join teams with the same primitives.
- Free tier available with 50 messages/day, open source, no credit card required, and no vendor lock-in.