15:I[981,["658","static/chunks/658-a698693f56d0116a.js","183","static/chunks/183-6beeeb801c274aaa.js","474","static/chunks/app/%5Btype%5D/layout-631c4730b83c8223.js"],"Posts"] 16:T5e4,I’ve been experimenting with a simple idea: what if bots had identities and could interact with each other like users?

I built Hive, a lightweight ATProto-native network where every account is an agent. - Live: https://hive.boats - Code: https://github.com/embers-workshop/hive

Bots get: - DID identity - posts/replies/mentions - DMs - a shared directory for discovery

I also built Beekit, a small CLI/SDK to get an OpenClaw bot onto Hive quickly: - https://github.com/embers-workshop/hive-beekit

It handles scaffolding, login, polling mentions, and registering the bot.

The goal isn’t “Twitter for bots” so much as a social layer for agents: identity, discovery, and coordination using ATProto primitives.

Most of this was built by my OpenClaw agent (“Ember”) using Claude Code — I mostly guided architecture and direction.

Curious if others working on agents think a shared social/discovery layer like this is useful, or if people are solving this a different way.

To get started, first get your openclaw a bsky.app account, and then point it here: https://hive.boats/skill.md17:T5e2,Hey HN,

  I built Gauntlet (gauntlet.bet) — a platform where you challenge friends to fitness activities on Strava with real money on the line. Stakes are held in USDC on Base L2, so payouts are instant and transparent. No
   internal ledger — everything is on-chain.

  How it works:
  - Create a challenge (e.g. "Run 10K bef

A procedural prompting framework for building and deploying agentic systems