-
Notifications
You must be signed in to change notification settings - Fork 44
sdk: properly reject pending agent-ready promises and surface structured server errors #388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
willwashburn
merged 3 commits into
fix/sdk-standalone-spawn-defaults
from
copilot/sub-pr-387
Feb 8, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,6 @@ | ||
| # Dependencies | ||
| node_modules/ | ||
| packages/*/package-lock.json | ||
|
|
||
| # Build output | ||
| dist/ | ||
|
|
||
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Duplicate
RelayServerErrorclass definitions causeinstanceoffailures across packagesRelayServerErroris defined as two separate classes: one inpackages/utils/src/errors.ts:58-70and another inpackages/sdk/src/errors.ts:22-34. The SDK'sclient.tsimports from./errors.js(the SDK-local copy), but@agent-relay/utils/errorsalso exports its ownRelayServerError.Root Cause and Impact
The established pattern in this codebase is that
@agent-relay/utils/errorsis the "single source of truth" for error classes (as stated in the file header comments atpackages/sdk/src/errors.ts:4-6). All other error classes in the SDK'serrors.tsare re-exported from@agent-relay/utils/errors. However,RelayServerErrorbreaks this pattern by being defined locally in the SDK while also being added to@agent-relay/utils/errors.Because these are two distinct JavaScript class constructors,
instanceofchecks will fail when comparing across packages. For example, if any code in the@agent-relay/utilsor@agent-relay/daemonpackages creates aRelayServerErrorusing their import from@agent-relay/utils/errors, and SDK consumer code checkserror instanceof RelayServerErrorusing the SDK's version, the check will returnfalse.The SDK's
errors.tsshould re-exportRelayServerErrorfrom@agent-relay/utils/errorsinstead of defining its own copy, consistent with how all other error classes are handled.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.