Skip to content

feat: Add clearer documentation for “Routing Strategy” and account-safety implications #1059

@bjspi

Description

@bjspi

Pre-flight checklist

  • I searched existing issues and discussions for similar proposals.
  • This is a concrete proposal, not an open-ended question.

Problem / motivation

Hi,

first of all thanks for building and maintaining codex-lb.

I would like to request some additional documentation or inline help text for the Routing Strategy (Choose how requests are distributed across accounts.) setting in the dashboard. Right now it is not fully clear to me what each routing option does internally and what the practical trade-offs are.

Proposed change

It would be very helpful if the docs could explain:

  • What each available Routing Strategy option means
  • How each strategy distributes requests across multiple ChatGPT/OpenAI accounts
  • Whether some strategies are better suited for low-volume, normal, policy-compliant personal usage
  • Whether any strategy is more likely to create unusual traffic patterns, rate-limit issues, or account-safety concerns
  • Which strategy you would recommend for users who want to minimize the risk of account flags, restrictions, or bans while staying within OpenAI’s terms and intended usage limits

Alternatives considered

No response

Area

No response

Additional context

I am not asking for ways to bypass limits or evade detection. I am mainly looking for guidance on which setting is safest and most conservative for compliant usage, and how to avoid accidentally configuring the load balancer in a way that looks abnormal from the upstream provider’s perspective.

A small table in the README or dashboard tooltip would already be very useful, for example:

Routing Strategy Behavior Pros Cons / Risks Recommended use case

Thanks again!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttriageAwaiting triage

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions