Skip to content

feat(gateway): optional quota failover for existing conversations - #12

Merged
Alumos merged 1 commit into
mainfrom
feat/quota-failover
Nov 12, 2026
Merged

Alumos merged 1 commit into
mainfrom
feat/quota-failover

Conversation

@Alumos

@Alumos Alumos commented Nov 12, 2026

Copy link
Copy Markdown
Owner

Adds a per-group opt-in "Switch accounts when quota runs out". When a bound conversation's account is quota-exhausted, a Responses request without server-held state moves to another admitted account of the same provider. Encrypted reasoning/compaction items from previous accounts are fingerprinted (migration 035) and stripped from later turns; the visible transcript is kept. Default off keeps the strict binding rule.

Verification: make check passes; new tests cover failover on, off, and item_reference refusal.

🤖 Generated with Claude Code

Resource groups can let a Responses conversation leave a quota-exhausted
account for another account of the same provider. Encrypted reasoning and
compaction items present at the move are fingerprinted on the binding and
withheld from the new account on every later turn. Requests referencing
provider-held state never move. Disabled by default.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Alumos
Alumos merged commit 21931e7 into main Nov 12, 2026
14 checks passed
@Alumos
Alumos deleted the feat/quota-failover branch November 12, 2026 06:32
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