Add a "Use CI" setting, off by default #248

Closed
opened 2026-10-27 15:30:58 -04:00 by cmoriarty · 1 comment
Owner

Why
For prototypes and proofs of concept, local tests are enough, and waiting on CI is slow. In the pinball test, runs waited 31.9 min on CI for tests that took 3.7 min locally. For big, established projects, CI matters.

What we want
A "Use CI" setting in Settings, off by default.

When it's off:

  • Agents are told to rely on the local tests, and not to add a CI workflow.
  • Runs skip the CI lane (#163) and never wait on CI.

When it's on, today's behaviour, plus:

  • Wait on one job when push and pull_request run the same jobs on one commit.
  • Print "waiting on CI" when the wait starts. Today it only appears after.

Done when
With it off, no run waits on CI and no agent adds a CI workflow.

From the Braid vs Claude Code pinball test, 2026-10-27 (runs 110–120).

**Why** For prototypes and proofs of concept, local tests are enough, and waiting on CI is slow. In the pinball test, runs waited 31.9 min on CI for tests that took 3.7 min locally. For big, established projects, CI matters. **What we want** A "Use CI" setting in Settings, off by default. When it's off: - Agents are told to rely on the local tests, and not to add a CI workflow. - Runs skip the CI lane (#163) and never wait on CI. When it's on, today's behaviour, plus: - Wait on one job when push and pull_request run the same jobs on one commit. - Print "waiting on CI" when the wait starts. Today it only appears after. **Done when** With it off, no run waits on CI and no agent adds a CI workflow. _From the Braid vs Claude Code pinball test, 2026-10-27 (runs 110–120)._
Author
Owner

What shipped

  • "Use CI" in Settings → Agents, off by default and kept per run. Off, the fix loop never waits on CI, and the agents are told not to add a CI workflow.
  • On, a job's push and pull_request runs are waited on once: the first to finish settles it.
  • "Waiting on CI" now shows when the wait starts. Script output is no longer held until the next bytes arrive.

Tests
tests/api/test_settings.py, tests/pipeline/test_ci_lane.py, tests/engine/test_script_output.py.

Shipped in 5598ddf (OpenSpec change checks-that-match-the-brief, archived).

**What shipped** - "Use CI" in Settings → Agents, off by default and kept per run. Off, the fix loop never waits on CI, and the agents are told not to add a CI workflow. - On, a job's push and pull_request runs are waited on once: the first to finish settles it. - "Waiting on CI" now shows when the wait starts. Script output is no longer held until the next bytes arrive. **Tests** `tests/api/test_settings.py`, `tests/pipeline/test_ci_lane.py`, `tests/engine/test_script_output.py`. _Shipped in 5598ddf (OpenSpec change `checks-that-match-the-brief`, archived)._
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#248
No description provided.