Skip to content

Route process calls directly to browser VMs - #160

Draft
tnsardesai wants to merge 1 commit into
mainfrom
hypeship/tier2-process-direct
Draft

Route process calls directly to browser VMs#160
tnsardesai wants to merge 1 commit into
mainfrom
hypeship/tier2-process-direct

Conversation

@tnsardesai

Copy link
Copy Markdown
Contributor

summary

  • add process to the default direct-to-VM browser routing allowlist
  • cover process exec, spawn, kill, resize, status, stdin, and stdout streaming through the existing prefix matcher
  • keep fs/* and telemetry/events on the control plane and preserve the environment override/kill switch

testing

  • pytest (678 passed, 2952 skipped)
  • ruff check and ruff format --check on touched files
  • live browser validation: exec, spawn, and stdout streaming routed through /browser/kernel/process/... and returned the expected output

Sign up for freeto 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.

1 participant

@tnsardesai