Tasks

You see work when it starts, not when the pull request lands.

A task is a piece of work with a name, an owner, and a conversation. You start one by saying what you want. That is all a task is, and it replaces a surprising number of meetings.

You see it start

A teammate's new task appears at the top of your sidebar with their face on it. Open it and you are reading along, live. If you have something to add, type; your message goes in under your name.

Kirill's sidebar and an open conversation. Steve's new task, Offline Badge, appears first under Tasks with Steve's face on it. Kirill opens it and reads along: Steve's request, the agent's first line and a tool step, still working.

Nobody has to write a status update for this to work. We build Happy in Happy, and there are two of us, Kirill and Steve. In November 2026 one of Kirill's tasks, on slow reconnects, published the page that framed its main decision, and Steve had joined the task within the hour. Two days earlier Kirill had joined Steve's task building Happy Cloud. Neither was asked to.

The agents notice each other too. A reviewer agent in Steve's task saw a commit Kirill had pushed straight to main, reviewed it without being asked, and caught a deployment step that would have broken a new model. Another was about to start a release, found one already running from the other person's account, and stood down.

Leave what isn't yours

You don't have to follow everything. If a task is not your business, leave it and it drops out of your list; it carries on for the people who care. Your sidebar is yours: you order it, and moving a task there moves it for nobody else.

One task, several repositories

Real work rarely fits in one repository. A task opens subtasks, each in its own copy of a repository on its own branch, each with its own list of changes, nested under the task that asked for it.

Team Servers open with its three subtasks under it in the sidebar, iOS server codes, Desktop sign-in and Docs: sign-in page, each with its repository's icon, an unread dot and its line counts. In the task, each subtask has replied with its final answer and the task says all three are ready for review.

One reply from Kirill in that reconnect task became a benchmark and eleven fixes, four in a networking library and seven in the phone app. Each ran in its own checkout, they took turns on the one Mac that builds iOS, and a twelfth agent merged the branches.

Each subtask can run on a different model. Plan on one, build on another, review on a third. → Models on your subscriptions

It finds you when it's your call

Tell Happy what you look after ("billing, invoices, Stripe webhooks") and agents know who to bring in. When a task touches your area, its agent loops you in with a one-line reason. When a decision is yours, it asks you by name and waits.

The Voice waveform task: the agent asks @Steve whether the muted waveform should be gray or red, with a question card offering both. Steve answers under his own name, Gray, red reads like an error, and the agent says gray it is and goes back to work.

Set yourself to away and agents stop waiting: they make the call, keep going, and leave you a note.

Tasks don't die

Close the app, restart the machine, come back next week. The task is where you left it and still knows what it was doing.

It can also keep going without you. Kirill signed off one night asking for proof by morning. The task woke itself every 45 minutes, and the report was there at breakfast: returning to a busy chat took 0.31 seconds, down from 6.7. → Agents That Never Die