Bots

A bot is one job, one key, and one rulebook.

Some work never finishes. Releases go out every week. Something has to watch the servers. Somebody should know how sign-ups did yesterday. On most teams those jobs belong to whoever remembered last, and the keys for them live on that person's laptop.

In Happy they belong to bots. A bot has a name, a picture, a folder of its own, and one continuous conversation. Every member sees the same bot and writes into the same conversation, so when you ask Desktop Releases how the preview build is going, you are reading the same thread your teammate asked in this morning.

The Happy window with the Desktop Releases bot selected in the sidebar's Bots list, a clock beside it because it is waiting for its next check. Its conversation is open: Linux passed, Windows still building, and a build receipt listing macOS, Windows and Linux with their build and signing state.

The bots we run

We build Happy with Happy: two people, Kirill and Steve, and these bots.

  • Desktop Releases writes the release notes and hands the grunt work to a cheaper model. It will not ship to production until a person says so, and a request passed along by another bot does not count.
  • Mobile Releases is the only thing on the team that holds the keys that sign our iPhone and Android apps.
  • Product Health keeps one dashboard current. It once traced most of the "rage clicks" on our website to a single scraper and shipped the fix.
  • GitHub Communications answers on issues and pull requests, and only when asked.
  • Chief of Staff is where the team's rules are written down. After our shared machine fell over under load one night, the rule "no heavy builds on the shared machine" went there, and every agent has followed it since.

The pattern is the same each time: a narrow job, the one credential that job needs, and a written rulebook the bot quotes back when you ask for something outside it. Any member can start one from New bot in the sidebar.

What makes a bot different from a chat

  • It remembers. One conversation, kept. It does not start from zero on Monday.
  • It has its own place. A folder for its notes and files, and its own subtasks when a job needs real work in a repository.
  • It works on a schedule. A bot can message itself tomorrow at nine, wait for a build, and pick up where it stopped after a restart.
  • It reports. What it makes goes into the feed like anyone else's work.
  • Its blast radius is scoped. Limit a bot to the secrets its job needs, keep it to its own agents, or run its commands in a container. → Exactly enough access

The Desktop Releases bot's conversation with two people in it. Steve asks under his own name whether Windows is done and the bot answers; Kirill says Windows passed QA and asks it to check the item off, and the bot updates the list and confirms.

The first bot: Chief of Staff

Every installation starts with one bot already there. The Chief of Staff sets Happy up when you ask: adds model accounts, imports a project, pairs your phone, creates the team, invites people. → Chief of Staff

Bots outside the app

A bot can answer in Telegram, or through a small bridge in Slack, Discord, or any other chat service. Each outside person is a guest with their own thread, and nobody gets in until you say yes. Recipes: Telegram, any chat service, restrict a bot.