Web UI: allowlist trusted domains to skip link-open confirmation

[lbronwas]

Problem

When clicking a link in terminal output in the web UI, agent-deck shows a browser confirm() dialog:

This link could potentially be dangerous — Cancel / OK

For anyone working against internal tooling (self-hosted GitLab, Gerrit, code review, CI, etc.), essentially every merge-request / change / build link fires this prompt. The links are known-safe and frequent, so the confirmation is pure friction — several extra clicks per minute during review work.

Request

A way to suppress the confirmation for trusted hosts. Either:

1. A domain allowlist, e.g.:

   [web]
   trusted_domains = ["gitlab.mycorp.example", "gerrit.mycorp.example"]

   Links matching an allowed host open without the prompt; everything else still confirms.

2. And/or a global toggle to disable the confirmation entirely for users who accept the risk:

   [web]
   confirm_link_open = false   # default true

Option 1 (allowlist) is preferred — keeps the safety net for arbitrary links while removing friction for the handful of internal hosts a user actually clicks all day.

Environment

• agent-deck v1.10.10
• Web UI (agent-deck web), Chrome on macOS

[asheshgoplani]

Accepted — this is real friction and the proposal is exactly the right shape. The [web] trusted_domains allowlist (host-match opens directly, everything else still confirms) plus an explicit opt-out toggle both fit the existing config patterns, and the allowlist form is the one we'd prefer as the default recommendation.

Implementation notes for whoever picks this up (contributions welcome, this is a good first issue): the confirm lives at the single link-open call site in the web UI; config plumbing follows the existing [web] section pattern; a Playwright test for allowlisted-vs-not is required for web UI changes here. If you'd like to take it, lbronwas, say so — otherwise it's open for any contributor.

[amh1k]

Would like to take this up. New to open source and will try my best to contribute effectively @asheshgoplani

[lbronwas]

Thanks for picking this up @amh1k. Sorry I accidentally closed the and I don't have perms to Reopen. Please reopen

[asheshgoplani]

Reopened — apologies, this was closed in error during today's high-volume cleanup sweep (the fix for this is designed and accepted but not yet merged). It stays open until the [web] trusted_domains allowlist actually lands. Thanks for the quick catch.

[asheshgoplani]

@amh1k — an apology and a thank-you: you volunteered for this right as a large automated fix-batch (running for the release push) already had this issue in its queue, and it produced PR #1758 before we saw your comment. That overlap is on us, not you. Two honest options, your pick: (1) review #1758 critically — if you spot gaps, your findings shape it and you are credited in the merge; (2) grab another issue — #1744 (reaper smoke test) or #1732-family test issues are open and yours if you want one, and we will hold them for you. Sorry again for the race, and welcome — we would love to have you contributing.