Skip to content

reports: reprocess has no rate limit and is a gateway-spend amplifier #692

Description

@Aristocles

One reprocess of a 20-page scan is ~21 vision calls plus comprehension; the endpoint accepts unlimited requests from the session holder, so a loop can drain a monthly gateway allowance in hours with nothing refusing or slowing it (the allowance classification then degrades reports to raw, which is the designed backstop). Single-user app, so this is self-harm or a stolen cookie, but a modest per-hour cap on reprocess would match the restraint elsewhere. Related: a 20-page vision document occupies the single ingest slot for many minutes with no queue-position feedback.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:serverHTTP surface + routing in server.jsenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions