Repository navigation
feat(platformclaw): proxy browser gateway access - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
PlatformClaw browser users need access to their provisioned OpenClaw agent without receiving unrestricted Gateway credentials or being able to reach another user's agent, sessions, credentials, or administrative methods.
Why This Change Was Made
Adds a control-plane-owned browser Gateway proxy policy that binds every request to the authenticated PlatformClaw browser session and its personal agent. The proxy uses explicit method allowlists, rewrites agent and session scope server-side, projects responses to browser-safe shapes, and records denied access in the existing control-plane audit store. Enterprise policy remains isolated in
packages/platformclaw-control-planeinstead of modifying OpenClaw Gateway core.User Impact
Authenticated browser users can use the allowed agent, chat, session, model, and health operations for their own managed agent. They cannot select arbitrary agents, raw model profiles, archived sessions, administrative cron behavior, or diagnostic model catalogs. Knox room routing is unchanged.
Evidence
origin/mainafter PR feat(platformclaw): provision personal agents #8 merged.git diff --check origin/main...HEADpassed.packages/net-policy/src/ip.ts; this is outside the PlatformClaw diff. The changed files were linted directly with the repository oxlint configuration.AI-assisted: yes. The author reviewed the implementation and validation results.