Skip to content

feat: per-account client fingerprints, wider failover and faster CI - #14

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

Alumos merged 1 commit into
mainfrom
feat/fingerprint-failover

Conversation

@Alumos

@Alumos Alumos commented Nov 12, 2026

Copy link
Copy Markdown
Owner
  • Per-account fingerprint convergence (CLIProxyAPI style): Claude device profile stabilization; Codex platform learned once per account and reused (migration 037).
  • Failover extended to long cooldowns, disabled/reauth/deleted/pool-removed accounts and exhausted allowances; original error returned when nowhere to move.
  • Connect-phase retry (DNS/dial/proxy CONNECT) only.
  • CI: separate Go build/race caches, BuildKit cache mounts persisted, main-branch cache warmer, shard split.

Tests run in CI only (per maintainer request).

🤖 Generated with Claude Code

- Pin one client fingerprint per upstream account: Claude device profiles
  are stabilized per account and Codex accounts reuse the platform of their
  first native client (migration 037).
- Account failover also leaves long cooldowns, disabled, reauthorization,
  deleted and pool-removed accounts, and exhausted allowances; it reports the
  original cause when no account can take the conversation.
- Retry provider connections that fail before any byte is sent.
- CI keeps separate build and race caches, persists BuildKit cache mounts,
  warms caches on main and splits the slowest test shard.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Alumos
Alumos merged commit 40c1478 into main Nov 12, 2026
16 checks passed
@Alumos
Alumos deleted the feat/fingerprint-failover branch November 12, 2026 13:13
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