MCP header-minting commands now run with credentials stripped from their environment.
What's wrong with this entry?
A headersHelper command declared by an MCP server no longer shells out directly with your full environment. It runs through the same runner used for other repo-declared commands, which picks the working directory from where the config lives and strips credential environment variables for project, plugin and additional-directory configs.
- The working directory is the plugin root, the declaring directory, or the current directory, depending on where the config came from.
- If the workspace has no saved trust decision, the helper is refused with a printed explanation rather than an exception, with a distinct message for sessions rooted at your home directory.
- Failure messages are now written per reason, including a new "did not return valid JSON" case.
did not return valid JSON
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Separate failure code when a credential helper's token is rejected
Both mention header helper
-
v2.1.248
Credential-helper tokens suppress the MCP OAuth flow
Both mention header helper
-
v2.1.227
Bad HTTP header values are rejected before the request instead of crashing
Both mention header helper