Skip to content

docs: document the 128 KiB size limit for Warp-managed secrets #441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hongyi-chen wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: document the 128 KiB size limit for Warp-managed secrets #441

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2dcde48
docs: document the 128 KiB size limit for Warp-managed secrets
oz-agent Jul 31, 2026
bbb7d5f
Merge branch 'main' into docs/managed-secret-size-limit
hongyi-chen Jul 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/content/docs/platform/secrets.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,6 +211,14 @@ Today, secrets are provided as environment variables using the secret name as th
METABASE_API_KEY=********
```

#### Secret size limit

Because secrets are injected as environment variables, each one has to fit inside the operating system's per-variable limit of 128 KiB (131,072 bytes). Warp counts the full `NAME=value` string against that limit, so the usable value length is 128 KiB minus the secret's name, the `=` sign, and the terminating null byte.

Warp validates the size when you create or update a secret, so an oversized value is rejected up front rather than failing partway through a run. Secrets that expand into several environment variables, such as AWS credentials, are validated per variable.

If you hit the limit, store the large payload somewhere the agent can fetch it at run time (an object store or a secrets manager the agent can call) and keep only the fetch credential in the Warp-managed secret.

---

### Secret availability by trigger type
Expand Down
Loading