fix: code workspace path escape errors - #2283
Conversation
🦋 Changeset detectedLatest commit: bd03d61 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…e-path-escape # Conflicts: # packages/agent-core-v2/src/session/workspaceContext/workspaceContextService.ts
|
Resolved conflicts with latest main and pushed head 4c4459f. The resolution keeps current main's shared FS_PATH_ESCAPES error domain and maps terminal cwd escapes to FS_PATH_ESCAPES_SESSION. Local validation under Node 24.18.0: pnpm install --frozen-lockfile; pnpm --dir packages/agent-core-v2 test test/session/workspaceContext/workspaceContextService.test.ts (3 passed); pnpm --dir packages/kap-server test test/terminals.test.ts (4 passed). |
…ace-path-escape # Conflicts: # packages/agent-core-v2/src/session/workspaceContext/workspaceContextService.ts # packages/kap-server/src/routes/terminals.ts
|
Rebased/resolved conflicts against upstream main. Validation:
Current head: bd03d61 |
Related Issue
No linked issue.
Problem
Path escapes from the workspace root currently bubble as generic errors instead of a stable workspace-specific code, which makes terminal reporting inconsistent.
What changed
Added a coded workspace-path-escape error, throw it from the workspace context service, map it to
FS_PATH_ESCAPES_SESSIONin kap-server, and cover the path with tests. Added a changeset for the release note.Checklist