Inspect automatic retries for failed Codex and Claude Code turns in bb after provider overloads or subscription usage windows. Check pending retry times and recorded decisions, send a scheduled retry immediately, or cancel it.
中文简介正在准备中。当前显示英语简介。
Diagnose automatic retries of BB turns after provider overloads, server or connection errors, and subscription-window limits.
安装前可以查看交给 AI 代理的指令内容。
The plugin is enabled on fresh installations. It reacts only to failed Codex and Claude Code turns and never blocks a send; prior output or tool activity does not prevent a retry. It queues a retry of the failed turn, which core runs by continuing accepted input or re-sending input the provider never accepted, for one of three failures:
For Account Pooler routes, retry timing comes from the pool's earliest usable account for the failed request's model, including parent pools, so a generic provider 429 without quota windows can still schedule a retry. Unknown resets, authentication failures, and unavailable pool sources do not schedule retries.
A turn gets at most four automatic retries. The maximumWait setting
(6 hours by default, or 24 hours or No limit) skips a subscription-limit
retry whose reset is farther away:
bb plugin config provider-retry set maximumWait "24 hours".
A pending retry is an ordinary durable queued row, shown on the thread's queue card with its reason and time, and survives restart.
bb provider-retry status [thread-id] [--json]
bb provider-retry explain [thread-id] [--json]
bb provider-retry retry <thread-id> [--json]
bb provider-retry cancel <thread-id> [--json]
status defaults to the current thread and lists every thread outside one.
explain reports the last recorded scheduling or skip decision; it is
historical and survives restart, so use status for what is still pending.
Decisions from before the plugin version that records them are not
backfilled. The plugin RPC decision.get accepts { threadId } and returns
the same nullable diagnostic.
retry sends the pending row now; cancel deletes it. Inspect the failed turn
before retrying manually, and avoid duplicating an existing queued retry. Use
the core bb thread retry command for an intentional manual retry of a turn
with no pending row; follow its live help for selection and scheduling flags.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Configure and diagnose Account Pooler in BB, including accounts, authentication, quota-based routing, and failover, which switches to another account. Inspect account and routing state, plus Provider Retry decisions after pooled rate-limit failures.
中文简介正在准备中。当前显示英语简介。
Configure and troubleshoot agents connected to BB through ACP, an agent connection protocol. Manage agent discovery, registry additions, model choices, custom agent settings, skill locations, and supported conversation compaction, which condenses session context.
中文简介正在准备中。当前显示英语简介。
Approve a GitHub account to open pull requests in get-bb/bb by updating its allowlist. The workflow verifies the account, checks the change, and creates and merges an approval PR while skipping SlopCop review and CI.
中文简介正在准备中。当前显示英语简介。
Add comments to specific elements in desktop Browser tabs and include those references in prompts. Edit or delete annotation pins, or update saved comments through the plugin RPC, a command interface for plugins.
中文简介正在准备中。当前显示英语简介。
Schedule recurring or one-time BB tasks using an agent for work that needs reasoning or a server-side script for fixed checks. Manage schedules, pause and resume tasks, run them manually, and inspect execution history.
中文简介正在准备中。当前显示英语简介。
Manage the getbb.app account linked to a bb server. Check which account remote access and hosted services use, sign in through a browser or pairing code, and sign out to revoke the server's credential.
中文简介正在准备中。当前显示英语简介。