What it is
A group chat where several bots share one room and Jev picks who speaks next.
What it does: You create bots with a name, instructions and a model, then talk to one bot alone or to several in a room. A mention is a hard rule in code: @handle wakes that bot and @everyone wakes all of them. When nobody is named, Jev scores which bot should reply. The turn itself runs on your own machine, where a daemon drives the Pi agent CLI with whatever model Pi can reach.
Why it belongs in the showcase: Picking the next speaker is a small, frequent routing decision. Orbs keeps explicit mentions in code and asks Jev only for the open case.
Caveats: Bots run real tools in your work folder (not a sandbox); no published routing metrics.
Evidence
Public MIT README; rooms hold people and bots, `@handle` wakes one bot and `@everyone` / `@all` / `@here` wake every member, otherwise Jev (TypeSafe) decides who answers; runs on Cloudflare (Workers, D1, R2, one Durable Object per organization) or as one local Bun process with SQLite; Jev routing needs `TYPESAFE_API_KEY`; the daemon connects out with an organization API key and drives your own Pi (`pi --mode rpc`), which is not bundled.
Caveats
- Bots run Pi's tools (read, bash, edit, write) as your user in the work folder; the README warns this is not a sandbox
- No routing-accuracy or cost figures published for the Jev speaker choice
- New repository at intake (34 stars, created 2026-10-06)
Unofficial case page. Stars / list position observed for heat; do not treat heat as a quality SLA. Review the upstream README before you depend on it.