AI game recaps

Once a game’s score is final, League Sage can write a short recap of the game — final score, standout plays, and standings context — and post it right on the game page for the whole team to read. It’s off by default; you turn it on per team.

Who can do this

Coaches and captains turn recaps on, set the tone, and choose the delay. Anyone on the team — including players — can read a finished recap once it’s written.

Steps

Open Config and scroll to the AI Game Recap card.
Check Enable AI game recaps. Two more controls appear.
Recap available after is a slider from On demand up through 12h, 24h, 36h, 48h, and 72h. This is deliberately not instant — see Why the delay below. 24h is the default and works well for most teams.
Tone & humor is a free-text box (up to 2000 characters) that steers how the recap reads. Leave it blank for a warm, lightly playful rec-league tone, or write your own, for example:

Big sports-radio energy, gentle ribbing for strikeouts, always end with a shoutout to whoever brought snacks.

Every field on this card autosaves — there’s no Save button.

Why the delay

The recap is written from whatever’s in the box score and at-bat data at the moment it runs — so if stats are still being corrected (a late scorebook upload, a coach fixing a play after the fact), a recap written too early just tells the story of the wrong game. The delay is your buffer: it counts from the game’s scheduled start time, not from when the score was entered, so pick something that comfortably covers how long it usually takes your team to get stats finalized after a game.

What players see

Once a recap exists, it shows up as a Game Recap card on the game page — 2 to 4 short paragraphs covering the final score, any standout batting or scoring performances, where the team stands in its league, and (once voting has closed) who won Player of the Game if your league uses that. Every recap carries a small “AI-generated — recaps can get details wrong” note, since it’s written from the data on file, not watched live.

When the app has history for the two teams, the recap opens with pre-game context — recent form and the head-to-head record. Scrimmages get recaps too, minus the standings angle, since they never count toward the league.

Players only ever see a finished recap. They never see a Generate button, a failure message, or a “not written yet” placeholder — if there’s nothing to show, the card simply isn’t there. While a recap is actively being written, the card shows a brief “Writing the recap…” line to anyone looking at the page at that moment.

On-Demand mode

Set the delay slider all the way to On demand and nothing happens automatically — no recap gets written on its own, ever. Instead, a coach or captain gets a Generate recap button on the game page once the score is submitted, and taps it whenever they’re ready (right after the game, the next morning, whenever the stats look right). This is the mode to use if your team’s timing varies a lot game to game, or if you’d rather just ask for a recap when you want one.

Regenerate

Not happy with a recap, or fixed a stat after it was written? Coaches and captains see a Regenerate button on any finished recap — tap it and a fresh one is written from the current data, replacing the old text. If a recap attempt fails outright (rare), the same spot shows Try again instead.

Good to know

Only coaches and captains (or an admin managing your team) can turn recaps on, change the tone, or generate/regenerate one. Players and observers can only read a finished recap.
A recap needs a submitted score to exist — it won’t generate for a game that hasn’t been reported yet.
Cornhole recaps only get per-player scoring detail on the side that entered the score that game; the other team’s recap still covers the final result and standings, just without that detail.
Only public post-game notes ever feed the recap — anything a coach marked private stays private.

Upload your scorebook — getting accurate stats in before your recap’s delay runs out
Keep score on game day