Handling password protected commands #1551
Description
Sometimes the default agents will issue commands that require interactive user input, e.g. sudo somecommand.
After a few retries, the agent usually detects the command is hanging and falls back to providing manual instructions for the user to continue.
What would be an elegant way to support a one-time privilege escalation flow (e.g., prompt once for sudo approval/password, then continue non-interactively)?