Add API for externally launching agent sessions - #77
Draft
Mbeaulne wants to merge 1 commit into
Draft
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.
Closes Shopify/oasis-frontend#688
Description
Adds a dedicated API for trusted external systems to create a bundle-backed Tangent session and immediately send its first prompt to Prime.
POST /api/session-launcheswith requiredbundleIdandpromptfields.sessionIdwithout exposing internal workspace details.Screenshots
N/A — server API only.
How to test
pnpm --filter @tangent/server test pnpm validateWith the server running and the deployment ingress configured, call:
Verify the response is
201 Createdwith asessionId, then open/sessions/<sessionId>and confirm the prompt is present and Prime begins processing it.Notes
The application does not store shared machine credentials. Basic Auth and any additional deployment-specific authentication headers must be configured outside this repository at the ingress or service-proxy layer.