Skip to content

Release 2.4.0: move an automatic session off an exhausted account - #21

Merged
maxrossignol merged 5 commits into
mainfrom
feat/session-failover
Oct 20, 2026
Merged

maxrossignol merged 5 commits into
mainfrom
feat/session-failover

Conversation

@maxrossignol

@maxrossignol maxrossignol commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

When an automatic session's account runs out (5-hour, weekly or spend cap), the pool now replays the request on the next account and keeps the session there, for Claude Code, Codex and Claude Desktop alike. The tool gets the answer instead of the 429.

  • Trigger: an exhaustion 429, or a binding already unable to serve (held, errored, disabled, outside the model's route). Throttle 429s keep their same-account wait, and the switch threshold still never moves a bound session.
  • Pins stay strict: the picker's account rows, --account, JAYNSHARE_ACCOUNT and the Desktop monitor's switch still mean that account or nothing.
  • Nobody left: the last account's own 429 is relayed unchanged, so each tool shows its usual limit message and reset time.
  • Sticky after the move: the session stays on the new account after the old one resets, so the prompt cache is lost once per switch.
  • Setting: [selection] failover, on by default; false restores the old sticky binding. A session_moved log line names both accounts.

Codex continuing a thread on another ChatGPT account was checked by hand with codex resume; the Desktop mid-chat switch already proved it for Claude.

Tests

  • New acceptance tests: a Claude Code session moves, stays, ignores a throttle and gets the real 429 when nothing is left; a Codex thread moves to the second login and stays; an automatic Desktop conversation moves mid-chat.
  • The tests of the old sticky path run with failover = false; the errored-binding check now expects the move.
  • Local: 390 unit and 514 acceptance tests, clippy and cargo fmt --check.

Also in this PR

  • Dependency advisories: CI's deny check failed on new advisories, the same on main. rustls 0.23.46 fixes RUSTSEC-2026-0346 to 0349; ruzstd 0.9.1 fixes RUSTSEC-2026-0344, a decompression bomb in the decoder that reads Codex's bodies; zip 9 fixes RUSTSEC-2026-0367 to 0369, which read_zip never reached because it doesn't extract. NOTICE.md is regenerated.
  • Desktop startup time limit: about half of the local full acceptance runs, with or without this PR's other changes, failed with "Desktop compatibility command timed out". The first run of a freshly copied binary waits for macOS's security scan, and under load that passed the 2 to 3 second limit. A newly downloaded Desktop runtime faces the same scan, so the limit is now 15 seconds. 4 of 4 full runs passed afterwards.

v2.4.0-rc.1 was published from fb75fd4 and checked live. The last commit sets 2.4.0; the tag goes on the merge commit.

🤖 Generated with Claude Code

maxrossignol and others added 4 commits October 18, 2026 18:13
An exhaustion 429 on an unpinned exchange is replayed on the next
account, and the session binds there; a binding that cannot serve
(held, errored, disabled, outside the route) gives way the same way.
Pins stay strict, throttles keep their same-account wait, and with
nobody left the last account's own 429 is relayed. The behaviour
applies to Claude Code, Codex and Claude Desktop alike and is on by
default; `[selection] failover = false` restores the sticky binding.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The version checks and the running-app check allowed 2-3 seconds. The
first run of a freshly installed binary waits for macOS's security scan,
which under load passed that limit: `jaynshare desktop` stopped with
"Desktop compatibility command timed out", and about half of the full
acceptance runs failed on fresh fake-tool copies. 15 seconds still
bounds a stuck command.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rustls 0.23.46 (RUSTSEC-2026-0346 to 0349), ruzstd 0.9.1
(RUSTSEC-2026-0344, the decoder that reads Codex's bodies) and zip 9
(RUSTSEC-2026-0367 to 0369; read_zip never extracts). zip 9 makes a
member's name fallible. NOTICE.md regenerated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@maxrossignol maxrossignol changed the title Move an automatic session off an exhausted account (2.4.0-rc.1) Release 2.4.0: move an automatic session off an exhausted account Oct 20, 2026
@maxrossignol
maxrossignol merged commit 1697a48 into main Oct 20, 2026
11 checks passed
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