Skip to content

Preserve the Browser control secret boundary - #63

Merged
laotoutou merged 1 commit into
mainfrom
agent/browser-control-secret-boundary
Aug 2, 2026
Merged

Preserve the Browser control secret boundary#63
laotoutou merged 1 commit into
mainfrom
agent/browser-control-secret-boundary

Conversation

@laotoutou

Copy link
Copy Markdown
Contributor

Summary

  • project Browser control responses from an explicit public-field allowlist
  • keep runtime dashboard coordinates and proxy headers server-side
  • assert the exact public response shape in the Browser service regression test

Context

The capability-aware Browser control path introduced in #62 accepted a runtime upstream object through structural typing. Spreading that object into the response could expose server-only upstream fields on the authenticated control endpoint. This patch returns only owner, transport, revision, and takeoverAvailable.

Validation

  • npm test (749 tests)
  • npm run build
  • npm run openapi:check
  • npm run typecheck
  • npm run lint
  • git diff --check

@laotoutou
laotoutou marked this pull request as ready for review August 2, 2026 06:07
@laotoutou
laotoutou merged commit 8abe714 into main Aug 2, 2026
2 checks passed
@laotoutou
laotoutou deleted the agent/browser-control-secret-boundary branch August 2, 2026 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants