Skip to content

[Feature]: Retry one-shot AI text helpers on another saved account after a subscription quota refusal #38528

Description

@dzkchen

Problem or use case

Orca's one-shot AI text helpers each run a single CLI process against one prepared account. The helpers are automatic branch and workspace names, commit messages, PR/MR title and body, Jira titles and independently configured chat-name recipes. When that account's subscription limit is reached, the provider refuses and the request fails. This happens even when the same host has another saved Claude, Codex or OpenCode Go account with capacity left.

  • Automatic branch/workspace naming records a failure and backs off. The workspace keeps its placeholder name until a later work event happens after the limit resets, or until the user switches accounts globally.
  • Commit-message / PR-field / Jira-title generation shows an error and the user has to switch accounts globally and click again.

Proposed solution

Add an opt-in host setting, off by default, under Settings → AI Provider Accounts. When a helper request is refused for subscription quota, the host that owns the request does the following:

  • Waits for the refused process to fully exit, then retries the same request on at most two other eligible saved accounts for the same provider and host. An account is eligible only if it has fresh usage data showing capacity in the relevant bucket.
  • Keeps the provider, model, effort, permissions and prompt unchanged, and never touches the global account selection.
  • Delivers the result only to the original workspace, draft or session. Stop, a newer request, a manual rename, an owner change or a deleted workspace discards a late result.
  • Keeps today's error and backoff when no account is eligible. Account pins, custom commands and credentials, WSL and unsupported routes behave exactly as today.

Alternatives or additional context

Activity

  1. added theissue type on Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions