Auto settings

Tune autonomous mode.

Defaults are sensible but your project is not the default. Tune autonomous mode in .story/config.json: cap how much it tackles per session, choose which reviewers run, decide what a red review means, and set escalation thresholds for when to stop and ask you.

Coming soon

Follow along

  1. 1.

    Open .story/config.json

    This is where autonomous mode reads its settings. The recipeOverrides object holds the knobs that matter. The Mac app has a settings UI for the common ones, but editing the JSON directly is always an option.

  2. 2.

    Set maxTicketsPerSession

    How many tickets the state machine will work through before handing back to you. 1 is safe while you're building trust. 3-5 is typical once you've seen it work. Higher is fine for well-scoped phases.

  3. 3.

    Choose review backends

    Under reviewBackends, enable or disable Codex and the lens set. You can also pick which individual lenses run (security, performance, test quality, architecture, UX, accessibility, observability, style). Fewer lenses = faster, more = more coverage.

  4. 4.

    Decide what stops the machine

    Set failureEscalation: on a red review, should it retry with the feedback, stop and ask you, or mark the ticket blocked? On test failure, how many attempts before handing back? Tune these to match your appetite for autonomy.

  5. 5.

    Save and try a run

    Save the file. Your next /story auto picks up the new settings. Start with one ticket on the tight settings, loosen as you build trust.