Repository navigation
feat(bash): add env parameter for setting environment variables #11065
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Issue Description
Problem
Plugins cannot inject environment variables into bash commands. There are a number of current feature requests which could be done with plugins if that was allowed, and it's a cheap / low risk fix.
Use Case
I want to build a plugin that sets AGENT_MODE=primary|secondary and AGENT_ID=<session_id> on all bash commands. This allows tracking whether commands run in the main agent or subagent sessions, as well as letting me keep track of some state in an external tool.
Currently, the only workaround is prepending VAR=value to commands, which is hacky and unreliable.
Proposed Solution
Add an optional env parameter to the bash tool that accepts a record of environment variables to set for the spawned process.
Example Usage
"tool.execute.before": async (input, output) => {
if (input.tool !== "bash") return
const session = await ctx.client.getSession(input.sessionID)
const isSubagent = session?.parentID != null
output.args.env = {
AGENT_MODE: isSubagent ? "secondary" : "primary",
AGENT_ID: input.sessionID,
}
}Implementation
- Add
env: z.record(z.string(), z.string()).optional()to bash tool schema - Merge env vars with
process.envin spawn call - Add tests for single and multiple environment variables
This would also allow issues like #10247 to be done in a plugin, thus reducing the need for specialized niche things in opencode.
Activity
github-actions commentedon Jan 29, 2026
This issue might be a duplicate of existing issues. Please check:
While these issues have different specific use cases, they all request the ability to set/inject environment variables for bash commands. Your proposal for an
envparameter in the bash tool schema would be a general solution that could address all of these needs.Feel free to ignore if your specific implementation is sufficiently different from these existing requests.
github-actions commentedon Mar 30, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
taxilian commentedon Apr 9, 2026
I love it how this closes it but when you open a new one you have to promise it hasn't been suggested before... but it has been, it was just automatically closed
Mart-Bogdan commentedon Sep 13, 2026
DAMN! This is really needed feature!