@paperclipai/adapter-codex-local 2026.714.0-canary.13 → 2026.714.0-canary.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@paperclipai/adapter-codex-local",
3
- "version": "2026.714.0-canary.13",
3
+ "version": "2026.714.0-canary.14",
4
4
  "license": "MIT",
5
5
  "homepage": "https://github.com/paperclipai/paperclip",
6
6
  "bugs": {
@@ -39,7 +39,7 @@
39
39
  ],
40
40
  "dependencies": {
41
41
  "@agentclientprotocol/codex-acp": "^1.1.0",
42
- "@paperclipai/adapter-utils": "2026.714.0-canary.13",
42
+ "@paperclipai/adapter-utils": "2026.714.0-canary.14",
43
43
  "picocolors": "^1.1.1"
44
44
  },
45
45
  "devDependencies": {
@@ -258,6 +258,19 @@ When the board accepts, your wake delivers `result.selectedOptionIds` — the op
258
258
 
259
259
  For full payload schemas, validation limits (option count, label lengths, min/max rules), accept/reject route bodies, and result fields, see `references/api-reference.md` -> **Checkbox confirmations**.
260
260
 
261
+ ## MCP Tool Approval Gates
262
+
263
+ Some MCP tools are configured as **ask first**. Their `tools/list` description says that human approval is required. When you call one:
264
+
265
+ 1. Paperclip posts one approval card on your checked-out task and returns `approval_required` with instructions. Do not retry the call while the card is pending. Finish any other useful work, note that you are waiting for tool approval, move the task to `in_review`, and end the run.
266
+ 2. Paperclip wakes the assignee after either approval or rejection. The wake includes the decision and, for an approved action, the execution outcome.
267
+ 3. Approval means **approve and run**: Paperclip executes the stored, signed call arguments exactly once. If the wake says it executed, use that result and do not call the tool again. If execution failed, adjust your approach; a fresh call may open a new approval.
268
+ 4. Rejection means the action did not run. Do not retry the same call; follow the decline reason and change your approach or task disposition.
269
+
270
+ Approval requests expire after 60 minutes. After expiry, call the tool again to request a fresh approval. Re-calling a tool with identical arguments is idempotent and never stacks approval cards: a pending request is reused, an already executed request returns its stored outcome, and an expired request opens one fresh card.
271
+
272
+ If the gateway returns `approval_path_missing`, the MCP session is not attached to a checked-out task, so Paperclip has nowhere to post the card. Re-run the action from a run that has the task checked out.
273
+
261
274
  Create `request_item_verdicts` when each known item needs its own verdict:
262
275
 
263
276
  ```json