not available equivalent
reversible
No per-operator spend or rate cap exists in this repo
applies to
N/A — documented gap, not a control
mechanism
N/A
notes
restrict-access.md is explicit that claude-tag itself has no "per-user spend caps on channel work" either ("Spend limits apply at the organization and channel level. There's no way to cap what one member can spend in channels"). This repo has the same real gap: nothing meters or caps how much any individual operator session spends against a shared Cloudflare account or D1 database. Seeded here as an honest "controls that aren't available" entry, mirroring that section of the same doc, rather than silently omitted.
grounded in
admins/restrict-access.md, "Controls that aren't available", "Per-user spend caps on channel work"
created 2026-07-02 14:20:40