fix: clarify sandboxed local server failures#167
Merged
Conversation
5b4d845 to
03cd91c
Compare
03cd91c to
f100e05
Compare
jcarver989
approved these changes
May 19, 2026
blimmer
pushed a commit
that referenced
this pull request
May 19, 2026
🤖 I have created a release *beep* *boop* --- ## [0.7.1](v0.7.0...v0.7.1) (2026-05-19) ### Bug Fixes * clarify sandboxed local server failures ([#167](#167)) ([c3de712](c3de712)) * **website:** typo in website agent instructions copy ([#149](#149)) ([6c85ebd](6c85ebd)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: contextbridge-pr-automation[bot] <259134118+contextbridge-pr-automation[bot]@users.noreply.github.com>
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.
Summary
ContextBridge now recognizes likely localhost bind failures caused by coding harness network sandboxes and reports them as user-recoverable environment errors. This gives users actionable guidance instead of the confusing Bun message
Failed to start server. Is port 0 in use?, and it avoids sending these sandbox failures to Sentry as runtime errors. Closes #168; fixes PLANBRIDGE-BACKEND-E.Review focus
Please check the boundary choice: the server API stays throw-based, while CLI annotation handlers classify only known local network sandbox signals before converting them to warn-level command errors. Explicit port conflicts, including
CONTEXTBRIDGE_PORT, should remain normal runtime errors.Commits
f100e05— clarify sandboxed local server failures