Changelog

  1. v0.2.0

    May 15, 2026

    Breaking

    Config schema v2

    We are migrating from the v1 YAML config format to v2. v1 will be supported until 2026-07-01, after which Maestrio will refuse to start with a v1 config.

    What changed

    The top-level shape moved from a flat keyed object to a sectioned format:

    # v1 (deprecated)
    default_confidence: suggest
    bug_confidence: draft
    docs_confidence: ship
    

    # v2
    confidence:
      default: suggest
      bug: draft
      docs: ship

    We also renamed the following fields:

    • human_reviewers is now reviewers.required
    • auto_merge is now merge.strategy, taking values manual, auto, or auto_after_review
    • slack_intake_channels is now intake.slack.channels

    Migrating

    Run maestrio config migrate from the CLI. It rewrites your config in place and prints a diff. Commit the result and you are done.

    Why

    The flat format started to break down once we added per-category confidence levels. Sections make growth easier without forcing more renames later.

  2. v0.1.0

    May 14, 2026

    Feature

    First public release

    The first public release of Maestrio is out. Highlights:

    • Slack and email intake
    • Automatic triage with category, severity, and dedupe
    • Linked GitHub PRs for well-scoped fixes
    • Per-team confidence levels (suggest, draft, ship)

    Sign up at maestrio.ai if you would like early access.

  3. v0.0.8

    May 1, 2026

    Fix

    Race condition in dedupe, plus a handful of small fixes

    A few weeks of accumulated fixes from beta feedback.

    Fixed

    • Race condition where two near-identical feedback messages arriving within 50ms could both be created as separate parent tickets. Dedupe now serializes per-channel.
    • Slack reactions on the original message are now preserved when Maestrio threads a reply.
    • Author avatars on the dashboard no longer 404 when an avatar URL contains query parameters.
    • Webhook payloads for pr.opened were missing the confidence field. Restored.

    Known still-broken

    • Linear sync still drops the priority field for non-bug tickets. Tracked, fix coming next week.

  4. v0.0.5

    April 18, 2026

    Improvement

    Faster Locate, smaller token bills

    Locate step now uses a reranker before handing files to the Patch agent. This cuts the average context size we send to the LLM by 4x and improves Patch quality on bugs that touch shared modules.

    Behind-the-scenes numbers from a week of production runs:

    • Median Locate time: 8.2s, down from 14.7s
    • Tokens per Patch call: 6,400, down from 24,100
    • Cost per resolved bug: $0.21, down from $0.74

    No config change required. Existing runs use the new pipeline automatically.

    One regression to flag: very small repos under 200 files sometimes return fewer candidate files than ideal. We are tuning the floor.

  5. v0.0.1

    April 2, 2026

    Feature

    Private beta opens

    Maestrio enters private beta with a small group of design partners.

    What is available:

    • Slack intake and triage
    • GitHub PR creation at Draft confidence
    • Per-team config via YAML
    • A very rough dashboard

    Known sharp edges:

    • Reproduce step is currently English-only.
    • No retry queue. Failed runs need to be re-triggered manually.
    • The CLI does not exist yet.

    If you are reading this and want access, send us a note. We are bringing in a handful of teams per week.