hi OH, i found this and verified it Issue: Automation master API key exposed to agent sandbox Our automation backend's master API key (

OPENHANDS_AUTOMATION_API_KEY

) is currently injected as a plain environment variable into the AI agent's sandbox, the same environment where it executes arbitrary shell commands. This violates least-privilege: the sandbox is a lower-trust context (commands can be influenced by untrusted input via prompt injection, or dumped accidentally via

env

, debug output, or crash logs), so any leak there exposes a full-privilege credential capable of controlling the entire automation backend. We should either stop seeding this key into the agent's environment (check injection point in

dev-with-automation.mjs

) or replace it with a short-lived, narrowly-scoped token so a leak has limited blast radius.

Hey, thank you for the report! Please feel free to check out this issue: https://github.com/OpenHands/software-agent-sdk/issues/4288 where we are investigating the redesign of all secrets

thanks that explains the direction this will be handled. seems good