feat(account selection) Add relative availability routing strategy by egusev · Pull Request #507 · Soju06/codex-lb

egusev · 2026-04-27T15:03:00Z

Description

add a new relative_availability routing strategy that prioritizes accounts by remaining weekly capacity relative to time left before reset
improve account usage when weekly windows differ, especially for mixed free, plus, and pro pools
prefer accounts whose remaining weekly limit would otherwise expire sooner, instead of looking only at current usage or absolute remaining capacity
add dashboard settings to tune strategy aggressiveness and candidate cutoff behavior
add selection diagnostics to make candidate scoring, shortlisted accounts, and final choice visible in logs
expose app logs through the root logger so routing diagnostics are visible in Docker logs

Compared with current strategies:

usage_weighted mainly follows lowest current usage percentage and does not account for how soon that weekly limit resets
capacity_weighted prefers larger remaining weekly capacity, but can under-prioritize accounts whose limit is about to expire
relative_availability balances both factors, helping reduce wasted weekly capacity near reset boundaries

half144 · 2026-04-27T15:05:52Z

amazing

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 31aeb0f578

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-04-27T15:09:34Z

+
+
+def _relative_availability_label(state: AccountState) -> str:
+    return state.email or state.account_id


Stop emitting account emails in routing logs

Using state.email as the primary routing label causes INFO diagnostics to log raw email addresses for candidate scoring, top-k selection, and winner selection. In deployments that ship logs off-host, this introduces unnecessary PII exposure compared with using stable internal account IDs (or a redacted/hash form), and the change affects every relative-availability routing decision.

Useful? React with 👍 / 👎.

Komzpa · 2026-05-16T17:52:24Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a0cbd1905e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-05-16T17:57:42Z

-            "Selected account_id=%s strategy=%s sticky=%s model=%s",
-            selected_snapshot.id,
+            "Selected account=%s strategy=%s sticky=%s model=%s",
+            selected_snapshot.email or selected_snapshot.id,


Avoid logging raw account emails in selection logs

This changed the selection log payload from an internal identifier to selected_snapshot.email when present, so routine INFO logs now emit user email addresses on every account pick. In environments that forward app logs to centralized storage, this creates avoidable PII exposure and also breaks existing account_id-based log correlation. Keep the stable non-PII account ID in this hot-path log (or mask email and gate it behind debug diagnostics).

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-05-16T17:57:42Z

+  const relativeAvailabilityPowerChanged =
+    relativeAvailabilityPowerValid && parsedRelativeAvailabilityPower !== settings.relativeAvailabilityPower;
+
+  const parsedRelativeAvailabilityTopK = Number.parseInt(relativeAvailabilityTopK, 10);


Reject non-integer top-k values instead of truncating

Using Number.parseInt here silently truncates decimal input (for example, 1.5 becomes 1), and the subsequent Number.isInteger check then passes, so the UI saves a different value than the user entered. That can unintentionally reduce the candidate pool and change routing behavior without clear feedback. Validate that the raw input is an integer-form value (or use strict numeric parsing) before enabling save.

Useful? React with 👍 / 👎.

# Conflicts: # app/core/balancer/logic.py

# Conflicts: # frontend/src/components/layout/status-bar.tsx

Soju06 · 2026-05-21T06:10:16Z

Maintainer cleanup: closing this as stale / no longer merge-ready against the current main.

This PR has been open across substantial main-branch churn and is currently carrying at least one stale signal (conflicts/blocked or failing checks, outstanding codex: needs work, draft/old branch state, or overlap with newer/current implementation). Keeping it open is making the PR queue harder to reason about.

If the change is still needed, please open a fresh, focused PR rebased on current main with green CI and a clean Codex review.

Komzpa · 2026-05-21T14:15:00Z

Revived on a maintainer-owned branch as #765 because this PR head has maintainerCanModify=false and cannot be updated here. Keeping credit to the original implementation in the replacement PR.

Add the relative availability account-routing strategy, which scores eligible accounts by remaining secondary-window credits over time to reset. Also persists and exposes dashboard tuning for the strategy, wires the configured power/top-K through sticky fallback selection, keeps routing diagnostics on non-PII account IDs, and adds OpenSpec, migration, backend, and frontend coverage. Revives #507.

egusev added 3 commits April 26, 2026 22:47

Add relative availability routing strategy

faac125

Add relative availability selection logs

7028d5e

Expose app logs through root logger

31aeb0f

chatgpt-codex-connector Bot reviewed Apr 27, 2026

View reviewed changes

egusev changed the title ~~Add relative availability routing strategy~~ (feat) Add relative availability routing strategy Apr 27, 2026

egusev changed the title ~~(feat) Add relative availability routing strategy~~ feat(account selection) Add relative availability routing strategy Apr 27, 2026

egusev added 2 commits April 27, 2026 12:53

Honor relative availability tuning in sticky fallback

15de6e9

Reduce relative availability candidate log level

a0cbd19

egusev mentioned this pull request Apr 28, 2026

[follow-up] Narrow _state_above_budget_threshold primary-only gating #446

Closed

Komzpa mentioned this pull request May 6, 2026

Tested live aggregate stack and suggested merge order #554

Closed

chatgpt-codex-connector Bot reviewed May 16, 2026

View reviewed changes

Komzpa added 🤖 codex: needs work [@codex review] raised an issue 🤖 codex: ok [@codex review] says no issues found. and removed 🤖 codex: needs work [@codex review] raised an issue 🤖 codex: ok [@codex review] says no issues found. labels May 16, 2026

Merge remote-tracking branch 'origin/main' into rel_strategy

a114c72

# Conflicts: # app/core/balancer/logic.py

Komzpa removed the 🤖 codex: needs work [@codex review] raised an issue label May 19, 2026

Merge remote-tracking branch 'origin/main' into rel_strategy

23516c6

# Conflicts: # frontend/src/components/layout/status-bar.tsx

Soju06 added the 🤖 codex: needs work [@codex review] raised an issue label May 21, 2026

Soju06 closed this May 21, 2026

Komzpa added needs rebase Needs rebase or conflict repair against current main stale No response from reporter; scheduled for close labels May 21, 2026

Komzpa mentioned this pull request May 21, 2026

feat(routing): add relative availability strategy #765

Merged

Komzpa removed 🤖 codex: needs work [@codex review] raised an issue needs rebase Needs rebase or conflict repair against current main labels May 21, 2026

Komzpa added the superseded Replaced by another PR, issue track, or merged implementation label May 21, 2026

Soju06 added the 🤖 codex: needs work [@codex review] raised an issue label May 21, 2026

Komzpa removed the 🤖 codex: needs work [@codex review] raised an issue label May 21, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(account selection) Add relative availability routing strategy#507

feat(account selection) Add relative availability routing strategy#507
egusev wants to merge 7 commits into
Soju06:mainfrom
egusev:rel_strategy

egusev commented Apr 27, 2026

Uh oh!

half144 commented Apr 27, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

chatgpt-codex-connector Bot Apr 27, 2026

Uh oh!

Komzpa commented May 16, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot May 16, 2026

Uh oh!

chatgpt-codex-connector Bot May 16, 2026

Uh oh!

Soju06 commented May 21, 2026

Uh oh!

Komzpa commented May 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants



		def _relative_availability_label(state: AccountState) -> str:
		return state.email or state.account_id

Conversation

egusev commented Apr 27, 2026

Uh oh!

half144 commented Apr 27, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

Komzpa commented May 16, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot May 16, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot May 16, 2026

Choose a reason for hiding this comment

Uh oh!

Soju06 commented May 21, 2026

Uh oh!

Komzpa commented May 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants