Workflow-style top bar on the agent edit page

[Jonksar]

Brings the edit page's top bar in line with the editor's workflow top bar (TopNavBar): one 64px row, 18px/500 title.

• Agent name is an inline-editable title (borderless until hover/focus) instead of a labelled input box; "Agent name" and "Name saves automatically" stay as visually-hidden label/description, so a11y and e2e selectors are unchanged.
• Version is a rounded chip, schedule sits after a thin divider and ellipsises instead of wrapping.
• Rename status (Saving…/Saved) and rename errors unchanged.

Before/after at 1440 and 900 px checked; full e2e suite 119/119.

---

Summary by cubic

Adds a demonstration-based setup flow for computer-use agents and replaces the default app: users describe a task, demonstrate it in a remote browser, review the captured steps, test, and schedule. Previously the ui/ app rendered the ReactFlow workflow editor; now it renders an embedded setup wizard, with a new recording/ capture service and production images beside it.

New Features

• Setup wizard covers describe, demonstrate, review, test, and schedule; the host owns auth, storage, execution, and scheduling through an origin-checked message bridge.
• recording/ captures demonstrations in ephemeral Browserbase sessions, groups steps into stages and rewording via an LLM, reports downloads, and stores credential fields as kind-only placeholders so values never reach the UI or model.
• Recording accepts only public HTTP(S) URLs with no query parameters or fragments and no embedded credentials.
• The edit page's top bar matches the editor's workflow bar: inline-editable agent title, version chip, and ellipsizing schedule after a divider; rename status and errors are unchanged, and visually-hidden labels keep a11y selectors stable.

Dependencies

• CI now runs UI unit tests, builds, and Playwright e2e plus pytest for the recorder; pushes to main build and push ui and recording images to ECR.
• The host contract for embedding the wizard is documented in docs/agent-setup-host.md; the app requires a parentOrigin query parameter.

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

[Jonksar]

Opened against the wrong repository by mistake, sorry.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets 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 secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic Password	e04e326	recording/tests/test_api.py	View secret
-	-	Username Password	64cbfd0	ui/src/setup/AgentSetup.tsx	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}