Skip to content

feat: route process calls directly to browser VMs - #160

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

feat: route process calls directly to browser VMs#160
tnsardesai wants to merge 1 commit into
nextfrom
hypeship/tier2-process-direct

Conversation

@tnsardesai

@tnsardesai tnsardesai commented Aug 25, 2026

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

release

This PR targets next. After merge, release-please opens or updates the versioned next → main release PR. Merging that release PR publishes the PyPI package.

@tnsardesai
tnsardesai force-pushed the hypeship/tier2-process-direct branch from 5d878a2 to f833c55 Compare August 25, 2026 19:31
@tnsardesai tnsardesai changed the title Route process calls directly to browser VMs feat: route process calls directly to browser VMs Aug 25, 2026
@tnsardesai
tnsardesai changed the base branch from main to next August 25, 2026 19:31
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.

1 participant