fix(app): route mounted workspace promptAsync/command through the OpenWork wrapper path#2452
Merged
Merged
Conversation
…nWork wrapper path The read-side session overrides (list/get/messages/todo) already go through the OpenWork wrapper when the client is openwork-mounted; promptAsync and command still used the generated SDK call unless the caller passed reasoning_effort (a field the generated client drops). Make the write path consistent with the read path: openwork-mounted clients always use postSessionRequest, which preserves unknown body fields and passes the directory via header. Split out of #2439 so this shared-path change ships and bisects independently of the org MCP connections feature.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Split out of #2439/#2451 so this shared-path change ships and bisects independently of the org MCP connections feature.
The read-side session overrides (list/get/messages/todo) already go through the OpenWork wrapper when the client is openwork-mounted; promptAsync and command still used the generated SDK call unless the caller passed
reasoning_effort. This makes the write path consistent with the read path: openwork-mounted clients always usepostSessionRequest, which preserves unknown body fields and passes the directory via header.Originally validated as part of #2439's full desktop fraimz (real chat turn executing an org MCP tool end-to-end): #2439 (comment)
Tests:
pnpm --filter @openwork/app typecheckclean;bun test apps/app/tests/passing on the source branch.