Retro

A collaborative sprint retrospective, run from the terminal but joined from any browser.

How it works

Retro mode is built around a live board rather than a solo report. The host opens the Retro page in the yeaboi TUI, which starts a small local web server for the session and a secure tunnel in front of it. Teammates then open the link from any browser, wherever they are — no install or account required — and add sticky cards to four grids: What went well, What didn't go well, Action items, and Demos.

Because the board is served over the network rather than shared as a static file, everyone sees the same state as it grows: cards added by any participant update live on every other participant's screen, kept in sync by polling the server every 2 seconds.

Access to a session is protected rather than open to anyone who happens to be on the network. Each retro gets a random access token together with a short, human-friendly join code, so the board can't be discovered or written to by an uninvited device. Card text itself is also treated as untrusted input — it's length-capped and escaped everywhere it gets rendered, so a pasted card can't be used to break the page.

Beyond the four grids, the live board supports emoji reactions on cards, drag-to-reorder, a shared countdown timer, a theme switcher, and ambient background music — all built with zero extra dependencies, since the server itself is just Python's standard-library HTTP server.

Joining

Teammates get into a running retro via the join code and URL the host shares, rather than needing any setup of their own. The short code is designed to be easy to read aloud or type in on the spot, and it resolves to the same token-gated board as the full URL, so there's no separate account step for anyone joining the session.

AI action items

Once the retrospective discussion winds down, yeaboi can turn the "didn't go well" cards into a set of suggested action items with a single LLM call. These AI-suggested items are clearly marked as AI-added on the board, so the team can tell at a glance which action items came from the discussion itself and which were synthesized afterward.

Remote sharing

The board's web server binds loopback only — nothing on your local network can reach it. It is shared through a free Cloudflare quick tunnel that starts automatically with the board, giving one HTTPS link that works for the person in the next chair and the person three time zones away, both protected by the same access code and token gate. The link takes a few seconds to appear while the tunnel comes up; the access code is live immediately.

Exports

Every retro auto-exports once it wraps up, saving both a Markdown file and a self-contained HTML report to ~/.yeaboi/exports/retro/<project>/, so the outcome of the session is captured as a shareable document rather than something that only lived on the board.