Skip to content

Teach the Cursor plugin that only a person settles a decision - #21

Merged
hopeatina merged 1 commit into
mainfrom
claude/truthful-states
Oct 2, 2026
Merged

hopeatina merged 1 commit into
mainfrom
claude/truthful-states

Conversation

@hopeatina

Copy link
Copy Markdown
Contributor

The OrgX MCP server now reports real state: approve/reject tools return where the person decides (the decisions widget's Approve button for ordinary decisions, otherwise the review_url), and orgx_command_status reports what happened to a decision, run or command. Cursor uses the default v2 profile, which exposes it.

  • commands/orgx-review-pending-decisions.md: the agent points the person to the widget or review_url, never calls the widget-only orgx_widget_decide, and only reports a decision as settled when orgx_command_status shows it.
  • rules/orgx-execution-loop.mdc (always applied): report the state OrgX holds; decisions wait on a person; spawned work is checked with orgx_command_status until next_poll_after_ms is null.
  • skills/orgx-runtime-reporting: new step "Report started work as started" (states, waiting_on, polling, same-key retries).
  • skills/orgx-execution-control-plane and agents/orchestrator.md: the same rule in one line each.

Verified: npm run check (manifest, MCP config and hooks valid; 55 tests: 54 pass, 1 skipped, 0 fail). No version bump.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RM5b4LVyYeCd4HzETsPviS


Generated by Claude Code

The OrgX MCP server no longer lets a model approve or reject a decision:
approve_decision, reject_decision, and orgx_decide approve/reject return
where the person decides (the decisions widget for ordinary decisions,
otherwise the review_url in OrgX). It also added orgx_command_status, which
the default v2 profile this plugin connects with exposes.

- commands/orgx-review-pending-decisions: drop "do not auto-approve without
  confirmation", which implied the agent could approve; point the person to
  the widget or review_url, never call orgx_widget_decide, and confirm a
  settled decision with orgx_command_status.
- rules/orgx-execution-loop: report the state OrgX holds; decisions wait on a
  person, spawned work is checked with orgx_command_status until
  next_poll_after_ms is null.
- skills/orgx-runtime-reporting: decisions wait on the person; a new step
  reports started work as started and reads its real state; unclear writes
  retry with the same idempotency key.
- skills/orgx-execution-control-plane, agents/orchestrator: the same rule in
  one line each.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RM5b4LVyYeCd4HzETsPviS
@hopeatina
hopeatina marked this pull request as ready for review October 2, 2026 01:12
@hopeatina
hopeatina merged commit 9090c78 into main Oct 2, 2026
2 checks passed
hopeatina pushed a commit that referenced this pull request Oct 2, 2026
Ships #20 (pin the Cursor work capture mode explicitly), #21 (teach the
Cursor plugin that only a person settles a decision) and #22 (send a
stable Idempotency-Key on Work Graph report posts). 0.1.9 was tagged but
never reached npm, so this is the first published release carrying #20.
Versions aligned across package.json, package-lock.json and
.cursor-plugin/plugin.json.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SeH94jeHnhDbgzKm6yHqZ9
hopeatina added a commit that referenced this pull request Oct 2, 2026
…ce (#23)

Ships #20 (pin the Cursor work capture mode explicitly), #21 (teach the Cursor plugin that only a person settles a decision) and #22 (send a stable Idempotency-Key on Work Graph report posts). 0.1.9 was tagged but never reached npm, so this is the first published release carrying #20. Versions aligned across package.json, package-lock.json and .cursor-plugin/plugin.json.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

2 participants