Skip to content

Follow-up handler is missing the per-message and total conversation character caps #45

Description

@jeremyandrews

scolta-php enforces follow-up caps (100000 characters per message, 400000 total). This port does not enforce those caps. (Node's Next adapter has a 1 MB body cap; Nuxt, Astro, and Django have no cap at all.)

Without the caps, an oversized or runaway conversation is forwarded to the provider instead of being rejected early, which is both a cost and an abuse concern.

Fix: port the two follow-up caps (per-message and total) from the scolta-php handler into this port's follow-up path, returning the same "Message too long" / "Conversation too long" validation errors.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions