Align examples with project-scoped Runtime API - #7
Merged
Conversation
added 2 commits
April 9, 2026 02:13
- Use /api/v1/projects/{projectId}/sessions/... for bash e2e and React sample
- Require PLANVAULT_PROJECT_ID / VITE_PLANVAULT_PROJECT_ID; add UI field
- POST messages: drop autoExecute; body is { message } only (202 Accepted)
- Refresh README copy (tools paths, plannerMode, removed legacy routes)
- Fix formatSseText unwrapJsonStringBlob return type for tsc --noEmit
Made-with: Cursor
Resolve conflicts by taking main for overlapping docs and samples: project- scoped Runtime URLs, X-Request-Id / error instance handling, no per-message status polling, and updated tools/Admin API wording. Brings in webhook and MCP README correlation notes from main. Made-with: Cursor
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.
Summary
Updates
planvault-examplesto match the current PlanVault Runtime API: all session routes live under/api/v1/projects/{projectId}/sessions/...,POST .../messagesreturns HTTP 202 withmessageId, andPromptRequestis{ "message": "..." }only (noautoExecute).Changes
scripts/bash-e2e/script.sh: requirePLANVAULT_PROJECT_ID; use project-prefixed URLs; dropautoExecutefrom the sample message body.frontend/react-chat:VITE_PLANVAULT_PROJECT_ID+ UI field;runtimeSessionsBase()for fetch URLs; SSE and actions use the same base; send only{ message }.README.md,frontend/react-chat/README.md,.env.example— env vars and API behaviour notes (tools under/projects/{projectId}/tools, etc.).formatSseText.ts: narrowunwrapJsonStringBlobcatch return sotsc --noEmitpasses (small typing fix).Verification
npm testandnpm run buildinfrontend/react-chatnpx tsc --noEmitinfrontend/react-chat