Batches: several issues in one run, an agent that picks them, and a rethought New Run wizard #361

Open
opened 2026-11-03 01:58:28 -05:00 by cmoriarty · 1 comment
Owner

What happens
A run takes one issue or one brief, so each issue costs its own branch, pull request and CI wait. New Run starts from an empty repository field and offers nothing about what to do next.

What we want

Batches: several issues in one run

  • Fewer CI waits and faster development overall.
  • A branching and merging process Braid can facilitate, to avoid unnecessary conflicts. To design.
  • Script what is easy to script. Where a rule would be hard to script or too restrictive, give the agent a brief instead of restricting it.

An agent step that chooses the batch

  • It reviews all the open issues and groups them by the user's guidance: timeframe, topic or anything else.
  • With no guidance, it uses a prepared default brief for sensible groups: UI fixes, same page, small issues, overlap.

Rethink every option in the New Run wizard

  • Recent repositories as one of the options, done elegantly, with a small Braid icon on repositories started with Braid.
  • Suggested next issues or batches, probably behind a button that starts the agent.
  • A setting for that agent in Settings, like Planning and Repair, with a "same as run" option.

To decide

  • "Same as run" when the run's backend hasn't been chosen yet: ask for it first, or fall back to the active profile?
  • One failing issue in a batch: does it hold back the others?
  • How this fits planned projects and #306, which runs items side by side on separate branches.

Done when

  • One run ships a batch of issues in one pull request with one CI wait, and each issue closes on its own evidence.
  • A sim covers the batch, including an issue that fails.
  • The same issues are timed as a batch and one at a time, with the result in a comment here.

Where to look: ui/src/components/NewRun.tsx, ui/src/components/Settings.tsx, openspec/specs/new-run/spec.md.

**What happens** A run takes one issue or one brief, so each issue costs its own branch, pull request and CI wait. New Run starts from an empty repository field and offers nothing about what to do next. **What we want** *Batches: several issues in one run* - Fewer CI waits and faster development overall. - A branching and merging process Braid can facilitate, to avoid unnecessary conflicts. To design. - Script what is easy to script. Where a rule would be hard to script or too restrictive, give the agent a brief instead of restricting it. *An agent step that chooses the batch* - It reviews all the open issues and groups them by the user's guidance: timeframe, topic or anything else. - With no guidance, it uses a prepared default brief for sensible groups: UI fixes, same page, small issues, overlap. *Rethink every option in the New Run wizard* - Recent repositories as one of the options, done elegantly, with a small Braid icon on repositories started with Braid. - Suggested next issues or batches, probably behind a button that starts the agent. - A setting for that agent in Settings, like Planning and Repair, with a "same as run" option. **To decide** - "Same as run" when the run's backend hasn't been chosen yet: ask for it first, or fall back to the active profile? - One failing issue in a batch: does it hold back the others? - How this fits planned projects and #306, which runs items side by side on separate branches. **Done when** - One run ships a batch of issues in one pull request with one CI wait, and each issue closes on its own evidence. - A sim covers the batch, including an issue that fails. - The same issues are timed as a batch and one at a time, with the result in a comment here. Where to look: `ui/src/components/NewRun.tsx`, `ui/src/components/Settings.tsx`, `openspec/specs/new-run/spec.md`.
Author
Owner

The recent-repositories part of this issue shipped with #541 (#544). New run lists the repositories of the newest runs, archived ones included, each with that run's name, status and date.

Batches, the agent that picks them, suggested issues and the Braid mark on repositories Braid started stay here.

The recent-repositories part of this issue shipped with #541 (#544). New run lists the repositories of the newest runs, archived ones included, each with that run's name, status and date. Batches, the agent that picks them, suggested issues and the Braid mark on repositories Braid started stay here.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#361
No description provided.