Skip to content

[CRITICAL] Provide Full Rate Limit Transparency #2897

@laz-001

Description

@laz-001

Describe the feature or problem you'd like to solve

Problem: the latest rate-limit chaos

Proposed solution

Besides the discussion here:

#2827

Some more things:

  • => extended to per model family rate limit display (e.g. gpt/claude)
  • => the agents should be able to access the actual rate limits (and see the notifications), so they can adapt.
  • => a prompt or subagent call can contain a rate limit (we can set a limit ourselves, for each call)

Those are must-have constructs in order to be able to control workflow behavior decently.

Example prompts or workflows

Do this and that.

/token-limit: n

Additional context

META: (this form) this really needs to be a multiline input:

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:modelsModel selection, availability, switching, rate limits, and model-specific behavior
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions