Orbs

A self-hosted multi-bot chat from nikuscs: rooms hold people and bots, a direct room is one bot, and teams can build an AI group chat like Grok Bot, Muse and Dots without giving up the machine that runs it. Each bot can use any model your Pi installation can reach.

Mentioning a handle wakes that bot, and @everyone, @all or @here wake every member. With no mention, Jev (TypeSafe) scores who should reply, which requires a TYPESAFE_API_KEY in the web app's .env file; without a key that routing path is what you lose.

You need Bun 1.4.2 and Pi 0.99.0+ on your PATH. Clone the repo, run bun install, copy apps/web/.env.example to apps/web/.env, start the web app with bun run dev:cloudflare, sign up at http://localhost:47101, then fill the daemon .env with a daemon key and start the daemon.

A daemon on your machine connects out and drives your own Pi process (pi --mode rpc); Pi is not bundled. Bot instructions are edited in the bot form, with extra instructions and skills under ~/.orbs/bots/<botId>/ and shared skills defaulting to ~/.orbs/shared.

Bots run Pi's tools (read, bash, edit, write) as your user in ORBS_WORKDIR, and the README states plainly that this is not a sandbox: a bot asked to change a repository will change that repository. Treat daemon keys and working directories as you would an agent with shell access.

Yes, the same app targets Cloudflare Workers with D1, R2 and one Durable Object per organization, or a single local Bun process with SQLite and disk. A production deploy requires creating the database, bucket and Worker yourself and setting APP_URL to an https origin, since the committed config is for local dev only.

MIT, with the bundled avatar blob engine also MIT by Jeremy Perret. The digest shows TypeScript, 40 stars, 6 forks, created and pushed 2026-10-06, so it is brand new; the local Bun mode listens on every interface unless you set HOST=127.0.0.1.