Skip to content

Pin the Cursor work capture mode explicitly - #20

Merged
hopeatina merged 1 commit into
mainfrom
fix/plan-v3-stage0
Sep 23, 2026
Merged

hopeatina merged 1 commit into
mainfrom
fix/plan-v3-stage0

Conversation

@hopeatina

Copy link
Copy Markdown
Contributor

Plan v3 §5.10. The bridge now always passes --work_episode_capture: metadata-only unless ORGX_CURSOR_WORK_CAPTURE=bounded. It also strips the ambient ORGX_SESSION_WORK_EPISODE_CAPTURE, so another client's setting cannot widen Cursor capture.

Behavior change: bounded capture on Cursor now needs the Cursor-specific variable. The one active external Cursor workspace connects via hosted MCP only, so it is unaffected.

Checks: npm test 54 pass / 0 fail.

🤖 Generated with Claude Code

Plan v3 §5.10: the bridge loaded the Wizard hook without
--work_episode_capture, so an ambient ORGX_SESSION_WORK_EPISODE_CAPTURE
could widen capture. It now always passes the mode (metadata-only unless
ORGX_CURSOR_WORK_CAPTURE=bounded) and strips the generic variable.

Checks: npm test 54 pass, 0 fail.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hopeatina
hopeatina merged commit ec1a5e9 into main Sep 23, 2026
1 check passed
@hopeatina
hopeatina deleted the fix/plan-v3-stage0 branch September 23, 2026 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant