Skip to content

Handle provider subscription rate-limit retries - #1027

Open
ymichael wants to merge 14 commits into
mainfrom
bb/handle-provider-rate-limit-retries-thr_nhfaj9pyvu
Open

Handle provider subscription rate-limit retries#1027
ymichael wants to merge 14 commits into
mainfrom
bb/handle-provider-rate-limit-retries-thr_nhfaj9pyvu

Conversation

@ymichael

@ymichael ymichael commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • normalize Codex and Claude subscription rate-limit telemetry into a shared provider state
  • add guarded, at-most-once continuation on the same provider conversation using agent-only Please continue.
  • add the opt-in builtin provider-retry plugin with in-memory scheduling, account coordination, UI, SDK, and CLI controls
  • enable it explicitly through Extensions → Plugins or bb plugin enable provider-retry
  • allow plugins to be enabled or disabled directly from their settings detail page
  • intentionally exclude retry persistence across server or daemon restarts

Safety

  • continuation is allowed only for the latest terminal failed turn with no emitted output or possible side effect
  • provider-owned retries remain authoritative while active
  • reset changes, host disconnects, cancellation races, and realtime reconnection are handled explicitly
  • credits and spend controls remain manual-retry cases

Validation

  • 13 affected Turbo typecheck tasks pass
  • app: 2,354 tests pass
  • server: 1,330 tests pass
  • agent runtime: 802 tests pass
  • provider-retry plugin: 10 tests pass
  • host-daemon contract: 49 tests pass
  • CLI, SDK, plugin SDK, server contract, templates, and domain suites pass
  • standalone provider-retry plugin build passes

@ymichael
ymichael force-pushed the bb/handle-provider-rate-limit-retries-thr_nhfaj9pyvu branch from a02a7c2 to 2af8587 Compare August 5, 2026 19:28
@ymichael
ymichael force-pushed the bb/handle-provider-rate-limit-retries-thr_nhfaj9pyvu branch from 8842902 to 0436b99 Compare August 5, 2026 22:46
ymichael added a commit that referenced this pull request Aug 5, 2026
## Summary

- give the structured workflow harness test a test-local 30-second
timeout
- keep the 15-second default timeout for the rest of the workflows suite

## Why

The packages check on #1027 timed this test out after 15.815 seconds.
The same test took 8.065 seconds and 10.852 seconds in the two preceding
successful runs, while it takes about 0.9 seconds locally. The test runs
several complete workflow lifecycles and validates multi-megabyte
payloads, so its runtime is unusually sensitive to shared-runner
contention.

## Testing

- pnpm exec turbo run test --filter=bb-plugin-workflows --force (5
consecutive runs)
- pnpm exec turbo run typecheck --filter=bb-plugin-workflows
@ymichael
ymichael marked this pull request as ready for review August 5, 2026 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant