You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 066a786
Browse filesBrowse the repository at this point in the historyBrowse files
[agent] feat: per-project caps on variable count and plaintext size
Two new settings, enforced by `envx set` before upload:
settings.max_variables_per_project (default 256)
settings.max_project_bytes (default 100 * 1024 * 1024)
Pre-flight check uses the variable list already fetched for the
overwrite-detection step (no extra network call). Computes the final
state after the upload would land — `existing - overwrites + new` for
both count and plaintext bytes — and bails with a clear message if either
cap would be breached, naming the exact `envx config set` command to
raise the limit.
Bytes are plaintext (key + value), not ciphertext. The user-facing
mental model is "how much did I type", which matches what they can
control. Ciphertext tracks plaintext closely (PGP adds ~constant
per-recipient overhead) so the cap still bounds server-side storage.
**Caveat for abuse prevention:** these are client-side caps. A modified
CLI can bypass them. For real abuse defense, the server needs to enforce
the same limits.
New FieldKind::Number variant in the field registry handles u32/u64
parsing for the two new settings.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments