[maxy-shpfy]

Description

Teaches the browser remote-env host to describe itself so Prime can tell it apart from an editor host (e.g. the VS Code extension) via list_environments and target the right one.

• Adds describeBrowserEnv(context) in remoteEnvHost.ts, returning { editor: "browser", description, capabilities } and distinguishing the editor canvas ("Tangent browser canvas", edits the spec live) from the run inspector ("Tangent browser run inspector", read-only).
• Threads an optional metadata field through createRemoteEnvHost into the connect options.
• Wires it up in TangentProjectAgentProvider (editor mode) and TangentRemoteEnvProvider (context-aware).

Related Issue and Pull requests

Top of the stack:

• feat: vs code extension for local agents support #2911 → feat: integrate vs code into tangent project page #2912 → chore: describe browser remote env properly for tangent #2913 (this PR)

Type of Change

• Improvement

Line Breakdown

Category	Added	Removed
Production code	32	3
Comments	2	0
Tests	48	1
Total	82	4

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Test Instructions

1. Open a Tangent project (editor) and a run view in the browser.
2. From Prime, call list_environments and confirm the browser host reports editor: "browser" with distinct descriptions/capabilities for the canvas vs the read-only run inspector.
3. pnpm test covering remoteEnvHost.test.ts passes (describeBrowserEnv + metadata forwarding).

Additional Comments

Depends on #2912.

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[github-actions]

🎩 Preview

A preview build has been created at: maxy/chore--describe-browser-remote-env-for-tangent/9d93cfa