[Bug]: npm package publish with interactive secret request #35226

Before submitting#

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area#

apps/desktop

Steps to reproduce#

1. Start macOS app (my current version: Version 0.1.10-nightly.20261112.4580 (40526f96f6ae)
2. let the agent start an npm publish via prompt => this will be interactive
3. when the npm cli asks for confirmation, it opens a browser window where i have to enter my 2fa
4. when i do this, the process can go on, but the t3code "secret input" tool still shows the secret input ui

Technically the process goes on and i can type anything i like there, but it is confusing.

Solution Idea: implementing a detection in this secret tool if a value is necessary for the cli at hand or not or if a remote confirmation is enough.

Expected behavior#

the secret tool simply showing me that remote confirmation is enough and that it closes when it detects remote confirmation (this might not be simple, because it might be dependent on the cli-tool that's run)

Actual behavior#

the secret input ui stays open and has an input

Impact#

Cosmetic issue

Version or commit#

Version 0.1.10-nightly.20261112.4580 (40526f96f6ae)

Environment#

macos Tahoe 26.7.2 (25G332)

Logs or stack traces#

Screenshots, recordings, or supporting files#

Workaround#

Simply add anything to the input and confirm with enter