Show the running test's browser as view-only

[Jonksar]

While a setup test runs, the Test step now shows the run's Browserbase browser as view-only; the user cannot click, type, scroll or focus it.

Chain: FIRE publishes the Browserbase fullscreen live-view URL when a run's browser opens → GET /agent/{id}/run/{run}/live-view (null once the run has a result) → ICE proxy → CFE setup controller returns liveViewUrl from getTestRun only while running → workflow-use renders it inert behind a pointer shield.

Host: . New e2e asserts the frame is inert, tabindex=-1, and covered by a shield (red confirmed without the UI change); 17/17 e2e pass.

---

Summary by cubic

Adds a demonstration-based setup flow for computer-use agents: describe a task, demonstrate it in an ephemeral browser, review the captured steps, test, and schedule. The previous workflow canvas is replaced by the new setup UI, and a separate recording service captures bounded semantic events from a Browserbase session. While a test runs, the Test step shows the run's browser as a watch-only live view behind an inert pointer shield.

New Features

• Setup UI with host message bridge: drafts, credential placeholders, compiled computer-use configs, and step review.
• Recording service: public-HTTP URL validation, 15-minute TTL, 200-step cap, and credential-field classification that never retains typed values.

Infrastructure

• CI runs UI unit and e2e tests plus recording service tests; production images for ui and recording are built on main.
• Docker images, Playwright setup, and a Playwright e2e suite covering the full journey were added.

^{Written for commit b8de132. Summary will update on new commits.}

[Jonksar]

Opened against the wrong repository by mistake; sorry for the noise.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic Password	e04e326	recording/tests/test_api.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}