Start remote container bridges with sensible defaults - #85
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.
Start a real container bridge with one call
This introduces a host-side remote container bridge API with sensible defaults:
The default path selects a local host adapter, generates a bridge token, validates local origins, exposes browser-ready WebSocket configuration, and resolves Apple
containerwhen the CLI is available.Developers can still choose every layer
The sandbox package now exposes explicit host-only subpaths for manual composition:
@inbrowser/sandbox/remote/hostownsstartRemoteContainerBridge, provider/host contracts, shared host behavior, and resolver types.@inbrowser/sandbox/remote/nodeadds a Node HTTP/WebSocket host and Node command runner.@inbrowser/sandbox/remote/bunkeeps Bun host support and adds a Bun command runner.@inbrowser/sandbox/remote/apple-containerpromotes the Applecontainerprovider into the package.The Apple provider is no longer Bun-bound. It uses an injectable
HostCommandRunner, with a Node default and a Bun runner available for Bun-hosted flows.The demo now runs through the public bridge API
The remote container demo now calls
startRemoteContainerBridgedirectly while preserving the fake provider for automated UI and protocol tests. The real Apple container integration test also exercises the high-level bridge path, so the demo validates the same API users will copy.The bridge behavior is covered across host runtimes
Coverage now includes Bun and Node host parity for authentication, streaming
run.outputevents, authenticated port proxy URLs, session cleanup, provider auto-resolution, resolver diagnostics, command-runner injection, Apple stale cleanup, and the one-callcreateWebSocketProvider()path.Verified locally: