byline
Wednesday, May 20, 2026·Vol. I, No. 24
The Archives

Changelog

What we’ve added, changed, and fixed — by issue.

  1. Vol. I, No. 24

    Sensible limits

    • addedPer-user caps on manual runs and beat creation, so a stuck loop can’t run away with the bill.
  2. Vol. I, No. 23

    Pick your hour, pick your zone

    • addedA schedule picker and timezone dropdown for new beats — no more hand-rolled cron strings.
    • changedTighter mobile layout across the dashboard and dialogs, with a few accessibility nits cleaned up along the way.
  3. Vol. I, No. 22

    Sonar, on the wires

    • addedPerplexity Sonar joins the agent’s research toolset for fresher web context.
  4. Vol. I, No. 21

    Quotes on the desk

    • addedA Yahoo Finance tool the agent can reach for when a beat mentions tickers.
  5. Vol. I, No. 20

    An editorial overhaul

    • changedDashboard, beats, and the landing page all redrawn with a stricter editorial hand.
  6. Vol. I, No. 19

    Sign in without Google

    • addedEmail and password sign in, alongside the existing Google option.
    • addedSign up and password reset flows, with email-based confirmation.
  7. Vol. I, No. 18

    A broadsheet for every issue

    • changedNewsletter PDFs are now typeset as a WSJ-style broadsheet — masthead, columns, drop caps, and footnoted citations.
  8. Vol. I, No. 17

    Small mercies

    • addedA favicon. Finally.
    • fixedCramped spacing around page titles across the app.
  9. Vol. I, No. 16

    Run now

    • addedA "Run now" button on each beat, so you can trigger a dispatch on demand instead of waiting for the next tick.
  10. Vol. I, No. 15

    Past issues, not run timelines

    • changedThe runs view now lists past issues directly, instead of step-by-step agent traces.
    • removedThe custom run-event tracing table — telemetry now flows to Cloud Trace, where it belongs.
  11. Vol. I, No. 14

    Introducing the changelog

    • addedA changelog page. Issue numbers in the masthead now link here.
    • changedThe masthead volume label is driven by the latest changelog entry instead of being hardcoded.