Hydrogen Desktop

Reporter: kaleymer ([email protected]), running Hydrogen Desktop v0.1.95 on Windows/WSL2.

What happens

When the AI issues a desktop shell command, the "Shell command needs approval" toast (bottom-right) only shows the bare program name — e.g.:

Shell command needs approval Approve in Adom Desktop: powershell [ Approve 1 hr ] [ Approve 24 hr ] [ Bypass Permissions ]

But the actual call was something like:

adom-desktop shell_execute '{"command":"powershell","args":["-NoProfile","-Command", ...]}'

The args / -Command payload — the part that actually determines what runs — is never surfaced in the prompt.

Why this is a problem

I'm being asked to grant 1 hr or 24 hr blanket approval to "powershell" with zero visibility into what it will execute. "powershell" tells me nothing: it could list a folder or wipe one. I can't responsibly approve a shell request without seeing the actual command, and a time-boxed approval to a bare interpreter name effectively hands over an unbounded shell for that window. As it stands I have to deny everything, which blocks legitimate work.

What I need before I'll approve

1. Show the full command and args in the toast (and/or an expandable "details" view) — the exact program + arguments, including the -Command / script body, not just command.
2. For long payloads, show a truncated preview with a way to expand the full text.
3. Ideally, scope the time-boxed approvals (1 hr / 24 hr) to the specific command, or at least make clear the approval applies to any powershell invocation for that window — the current wording is ambiguous about what "Approve 24 hr" actually authorizes.

Repro

Have the AI run any desktop shell command via shell_execute with a non-trivial -Command arg (e.g. the EDA-tool folder scan that triggered this). Observe the toast shows only "powershell".

please close once done.