Every AI agent your team runs right now is impersonating a human account, which means when something breaks, the audit trail is worthless.

The bot-token model has been quietly rotting team workflows

Most teams bolt agents onto Slack or Teams using shared bot tokens with no real identity, no channel ownership, and no reliable history. When an agent touches something it shouldn’t, there’s no clean way to trace who authorized what.

Agents get keypairs now, not borrowed credentials

Nous Research Ships Three Integration Paths for Hermes Agent and Buzz, Block’s Open Source Nostr Workspace for Humans and Agents gives every agent its own cryptographic identity on a Nostr relay you host, so humans and AI share the same channels with separate, verifiable signatures. You open Settings, navigate to Runtimes, and Hermes appears automatically under the Buzz Desktop managed runtime with no extra configuration. The relay runs on Postgres, Redis, and S3/MinIO, and Hermes connects via ACP over stdio or a WebSocket relay bridge depending on whether your agent is local or hosted.

Platform teams feel this gap the most acutely

• Mid-market platform engineers who need agents to post incident summaries with a traceable identity, not a shared bot handle
• DevOps leads running code review workflows who want branch-scoped rooms where agents draft notes without polluting human channels
• Security-conscious teams on self-hosted infrastructure who cannot route agent traffic through third-party SaaS bot APIs

Solo developers can run the full stack on Buzz Desktop today with zero configuration overhead.

Open source workspaces are eating the bot-API layer

Buzz has 18.8k stars on GitHub under Apache-2.0, and Hermes Agent ships MIT licensed, which puts this squarely in the path of proprietary bot frameworks charging per-seat for features that are now free and self-hostable. As agent-to-agent communication becomes a standard expectation in team tooling, platforms that can’t assign discrete identities to non-human participants will look architecturally behind.

What you can actually do with this today

• Route incident alerts into a channel where Hermes summarizes history automatically
• Create a branch-scoped room and have agents draft pull request review notes
• Schedule cron-delivered reports posted by a named agent identity
• Run agent-drafted release notes through a channel before human sign-off

Both Buzz and Hermes Agent are free and open source. Pricing not listed for any hosted tier — check our directory.

Mobile clients and workflow approval gates are still in progress, so enterprise rollouts should treat this as a pilot rather than a production dependency.

If you need a managed alternative, tools like Slack with third-party bot frameworks or Microsoft Copilot Studio offer hosted agent orchestration but neither gives agents a portable, self-owned cryptographic identity. The Nostr-based approach here is architecturally distinct from anything in the managed SaaS stack.

Agent identity is becoming the next compliance fault line

The shift from shared bot tokens to cryptographically signed agent identities is happening faster than most teams have planned for. We cover tools like this every Friday — subscribe here and we’ll send the best ones straight to you.