Requests & approvals
A request is an ask, not a change: "I need STRIPE_SECRET_KEY in production, here is why." It lands in a reviewer's queue, and if the reviewer approves, the reviewer supplies the value. The requester never proposes secret material.
Who can file, who can review#
| Actor | Files requests | Reviews requests |
|---|---|---|
| Owner, Project Manager, Team Lead | — (creates directly) | ✓ |
| Developer | ✓ | — |
| Editor, Viewer | — | — |
Reviewing needs the project.requests.review capability. Developers see only their own requests; reviewers see every request in their projects.
The human loop#
File it#
From the dashboard (Request Variable), the CLI (envpilot request), or VS Code (Envpilot: Request Variable). You supply the key, the environments, and why you need it. A developer's environment choices are limited to their assigned scope.
Review it#
The reviewer sees the request in the project's Requests inbox, in envpilot requests, or via email. They approve, reject with a reason, or leave it pending.
Supply the value#
Approval is where the value is entered. In the CLI that is a masked prompt; in CI, --value-stdin keeps it out of argv and out of shell history.
Use it#
Once approved, the variable exists and appears in the requester's next pull.
Rejection carries the reviewer's reason back to the requester, so nobody has to guess whether they were denied or ignored. Cancelling is available to the requester while a request is still pending.
Agents#
Agents no longer file variable requests; that path needed an API key and was removed with API-key access to the MCP server. An agent signed in to the MCP server works under your role instead: it can create variables you could create, and a write into a protected environment becomes a change request that a second person approves.
Limits#
Other boundaries worth knowing:
- Requests create variables. They are not a channel for editing an existing value — that is a direct write by someone who holds the capability.
- The GitHub Action can never file a request. CI reads; it does not negotiate.
- On approval, a human always types the value.
See also#
- CLI: requests —
request,requests list/approve/reject/cancel - MCP: agent requests (legacy)
- Roles & permissions