commandmate 0.47.0 → 0.48.0

package/dist/server/src/types/auto-yes-answer-mode.js

@@ -0,0 +1,38 @@
+"use strict";
+/**
+ * How Auto-Yes answers a question the agent asks (Issue #3863).
+ *
+ * - `recommended` (おまかせ, the default) — a single-select question on the
+ *   screen is answered too: the option whose title ends in a recommendation
+ *   marker (`(Recommended)` / `（推奨）` / `(推奨)`), or the default (the
+ *   cursor, else option 1) when none does. A question it cannot read that far
+ *   (two markers, a marker on a free-text or multi-select row, a title it
+ *   cannot tell from its description) is left to a human.
+ * - `careful` (慎重) — a question is never answered; it is left to a human
+ *   (`question-left-to-human`).
+ *
+ * The two differ only there. Permissions are answered alike (the one "allow
+ * this call once" row, #3822), and what a contract's `autoYes` block withholds
+ * stays withheld under either (the contract is the ceiling; the answer mode is
+ * below it).
+ *
+ * Set each time Auto-Yes is turned on (worktree × instance). Turning it on
+ * from off — or after it ran out — starts at `recommended` unless a mode is
+ * given; turning it on again while it is on keeps the mode it has.
+ *
+ * Dependency-free so the CLI build (`tsconfig.cli.json`, no path aliases) can
+ * import it by a relative path.
+ *
+ * @module types/auto-yes-answer-mode
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DEFAULT_AUTO_YES_ANSWER_MODE = exports.AUTO_YES_ANSWER_MODES = void 0;
+exports.isAutoYesAnswerMode = isAutoYesAnswerMode;
+/** Every {@link AutoYesAnswerMode}, the default first. */
+exports.AUTO_YES_ANSWER_MODES = ['recommended', 'careful'];
+/** The mode of a grant that names none: one turned on without a mode, or kept from before the field. */
+exports.DEFAULT_AUTO_YES_ANSWER_MODE = 'recommended';
+/** Type guard for a value read off a request body or the wire. */
+function isAutoYesAnswerMode(value) {
+    return value === 'recommended' || value === 'careful';
+}

package/dist/server/src/types/auto-yes-decision.js

@@ -0,0 +1,61 @@
+"use strict";
+/**
+ * Auto-Yes's decision about the confirmation on screen, as published
+ * (Issue #3821).
+ *
+ * The server's Auto-Yes poller is the only thing that answers a screen
+ * confirmation automatically (the browser no longer does, and the Enter on an
+ * unreadable screen is gone). What it decided for the confirmation it last
+ * judged is published next to the prompt it was judged for, so the answer
+ * surfaces know whether a human has to answer it:
+ *
+ * - `answering` — an automatic answer to this confirmation is under way (being
+ *   sent, or sent and the screen not redrawn yet);
+ * - `withheld` — Auto-Yes has left this confirmation to a human, with a
+ *   `reason` (the contract, a screen it cannot read, a question, no poller
+ *   running for the instance, …);
+ * - `none` — no confirmation, or one not judged yet. Never read as answering.
+ *
+ * Client-safe: no imports but the dependency-free answer mode (Issue #3863),
+ * so the browser hooks and the server read one shape.
+ *
+ * @module types/auto-yes-decision
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.NO_AUTO_ANSWER_DECISION_REASON = exports.SERVER_POLLER_INACTIVE_DECISION_REASON = void 0;
+exports.isAutoYesAnswering = isAutoYesAnswering;
+exports.laterAutoYesDecision = laterAutoYesDecision;
+/** The reasons this record adds to the poller's suppression reasons. */
+exports.SERVER_POLLER_INACTIVE_DECISION_REASON = 'server-poller-inactive';
+exports.NO_AUTO_ANSWER_DECISION_REASON = 'no-auto-answer';
+/**
+ * Whether the answer panel may stay hidden under Auto-Yes for a prompt with
+ * this decision: only while an automatic answer is under way. A missing
+ * decision (an older server, a delivery path that did not carry it) is not
+ * `answering`.
+ */
+function isAutoYesAnswering(decision) {
+    return decision?.state === 'answering';
+}
+/**
+ * Of two decisions about the SAME prompt window, the one observed later
+ * (Issue #3821). The HTTP poll and the push deliver the same payload over two
+ * paths whose arrival order is not their build order; a decision observed
+ * before the one already applied is not applied over it.
+ *
+ * Only for the same confirmation (`confirmation`): a window with the same
+ * question and options may approve something else, and a decision about
+ * another confirmation — or one that does not say which (`confirmation`
+ * absent on one side only) — is dropped for the one this delivery carries,
+ * whatever their times. Two without the field are compared by time.
+ *
+ * @param previous - What is applied now for this window, if anything
+ * @param next - What this delivery carries
+ */
+function laterAutoYesDecision(previous, next) {
+    if (previous === undefined || next === undefined)
+        return next;
+    if ((previous.confirmation ?? null) !== (next.confirmation ?? null))
+        return next;
+    return next.observedAt < previous.observedAt ? previous : next;
+}

package/dist/server/src/types/auto-yes.js

@@ -10,3 +10,9 @@
  * `AutoYesToggleParams` from the component keep working unchanged.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.isAutoYesAnswerMode = exports.DEFAULT_AUTO_YES_ANSWER_MODE = exports.AUTO_YES_ANSWER_MODES = void 0;
+// Issue #3863: the answer mode, declared dependency-free for the CLI build.
+var auto_yes_answer_mode_1 = require("./auto-yes-answer-mode");
+Object.defineProperty(exports, "AUTO_YES_ANSWER_MODES", { enumerable: true, get: function () { return auto_yes_answer_mode_1.AUTO_YES_ANSWER_MODES; } });
+Object.defineProperty(exports, "DEFAULT_AUTO_YES_ANSWER_MODE", { enumerable: true, get: function () { return auto_yes_answer_mode_1.DEFAULT_AUTO_YES_ANSWER_MODE; } });
+Object.defineProperty(exports, "isAutoYesAnswerMode", { enumerable: true, get: function () { return auto_yes_answer_mode_1.isAutoYesAnswerMode; } });

package/dist/server/src/types/prompt-reading.js

@@ -0,0 +1,32 @@
+"use strict";
+/**
+ * What a prompt screen was READ as, kept beside the prompt (Issue #3881).
+ *
+ * The detectors hand on `PromptData` — a question, options, and the deny
+ * surface — and drop what they knew about the screen while reading it: which
+ * kind of dialog it was, which rows were live, whether the approval target is
+ * the whole of what the panel asks about. Each later path then decided those
+ * again from the cut-down strings, and they disagreed: the chat transcript drew
+ * Claude's 16-column `Ready to submit your answers?` page — which the Auto-Yes
+ * poller leaves to a human as `question-confirm-page` — as a tool approval,
+ * because the stored options read `Submit` / `Cancel` and the review list was
+ * cut off the stored question.
+ *
+ * So the reading is decided once, where the frame is still in hand (the
+ * response poller's save, `polling/prompt-screen-reading`), and stored with
+ * the row. Readers take it as stated and never derive it again from the text;
+ * a row without one (written before #3881, or by a producer that has no frame)
+ * goes through each reader's own compatibility rules, explicitly.
+ *
+ * Types only: imported by `types/models` and by client code.
+ *
+ * @module types/prompt-reading
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.PROMPT_READING_VERSION = void 0;
+/**
+ * The version of {@link PromptReading} a row carries. A reader that meets
+ * another version treats the row as having no reading (its compatibility
+ * rules), rather than guess at fields it does not know.
+ */
+exports.PROMPT_READING_VERSION = 1;

package/dist/types/auto-yes-answer-mode.d.ts

@@ -0,0 +1,35 @@
+/**
+ * How Auto-Yes answers a question the agent asks (Issue #3863).
+ *
+ * - `recommended` (おまかせ, the default) — a single-select question on the
+ *   screen is answered too: the option whose title ends in a recommendation
+ *   marker (`(Recommended)` / `（推奨）` / `(推奨)`), or the default (the
+ *   cursor, else option 1) when none does. A question it cannot read that far
+ *   (two markers, a marker on a free-text or multi-select row, a title it
+ *   cannot tell from its description) is left to a human.
+ * - `careful` (慎重) — a question is never answered; it is left to a human
+ *   (`question-left-to-human`).
+ *
+ * The two differ only there. Permissions are answered alike (the one "allow
+ * this call once" row, #3822), and what a contract's `autoYes` block withholds
+ * stays withheld under either (the contract is the ceiling; the answer mode is
+ * below it).
+ *
+ * Set each time Auto-Yes is turned on (worktree × instance). Turning it on
+ * from off — or after it ran out — starts at `recommended` unless a mode is
+ * given; turning it on again while it is on keeps the mode it has.
+ *
+ * Dependency-free so the CLI build (`tsconfig.cli.json`, no path aliases) can
+ * import it by a relative path.
+ *
+ * @module types/auto-yes-answer-mode
+ */
+/** Auto-Yes's answer mode (Issue #3863). */
+export type AutoYesAnswerMode = 'recommended' | 'careful';
+/** Every {@link AutoYesAnswerMode}, the default first. */
+export declare const AUTO_YES_ANSWER_MODES: readonly AutoYesAnswerMode[];
+/** The mode of a grant that names none: one turned on without a mode, or kept from before the field. */
+export declare const DEFAULT_AUTO_YES_ANSWER_MODE: AutoYesAnswerMode;
+/** Type guard for a value read off a request body or the wire. */
+export declare function isAutoYesAnswerMode(value: unknown): value is AutoYesAnswerMode;
+//# sourceMappingURL=auto-yes-answer-mode.d.ts.map

package/dist/types/auto-yes-answer-mode.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"auto-yes-answer-mode.d.ts","sourceRoot":"","sources":["../../src/types/auto-yes-answer-mode.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAEH,4CAA4C;AAC5C,MAAM,MAAM,iBAAiB,GAAG,aAAa,GAAG,SAAS,CAAC;AAE1D,0DAA0D;AAC1D,eAAO,MAAM,qBAAqB,EAAE,SAAS,iBAAiB,EAA+B,CAAC;AAE9F,wGAAwG;AACxG,eAAO,MAAM,4BAA4B,EAAE,iBAAiC,CAAC;AAE7E,kEAAkE;AAClE,wBAAgB,mBAAmB,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,iBAAiB,CAE9E"}

package/dist/types/auto-yes-answer-mode.js

@@ -0,0 +1,38 @@
+"use strict";
+/**
+ * How Auto-Yes answers a question the agent asks (Issue #3863).
+ *
+ * - `recommended` (おまかせ, the default) — a single-select question on the
+ *   screen is answered too: the option whose title ends in a recommendation
+ *   marker (`(Recommended)` / `（推奨）` / `(推奨)`), or the default (the
+ *   cursor, else option 1) when none does. A question it cannot read that far
+ *   (two markers, a marker on a free-text or multi-select row, a title it
+ *   cannot tell from its description) is left to a human.
+ * - `careful` (慎重) — a question is never answered; it is left to a human
+ *   (`question-left-to-human`).
+ *
+ * The two differ only there. Permissions are answered alike (the one "allow
+ * this call once" row, #3822), and what a contract's `autoYes` block withholds
+ * stays withheld under either (the contract is the ceiling; the answer mode is
+ * below it).
+ *
+ * Set each time Auto-Yes is turned on (worktree × instance). Turning it on
+ * from off — or after it ran out — starts at `recommended` unless a mode is
+ * given; turning it on again while it is on keeps the mode it has.
+ *
+ * Dependency-free so the CLI build (`tsconfig.cli.json`, no path aliases) can
+ * import it by a relative path.
+ *
+ * @module types/auto-yes-answer-mode
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DEFAULT_AUTO_YES_ANSWER_MODE = exports.AUTO_YES_ANSWER_MODES = void 0;
+exports.isAutoYesAnswerMode = isAutoYesAnswerMode;
+/** Every {@link AutoYesAnswerMode}, the default first. */
+exports.AUTO_YES_ANSWER_MODES = ['recommended', 'careful'];
+/** The mode of a grant that names none: one turned on without a mode, or kept from before the field. */
+exports.DEFAULT_AUTO_YES_ANSWER_MODE = 'recommended';
+/** Type guard for a value read off a request body or the wire. */
+function isAutoYesAnswerMode(value) {
+    return value === 'recommended' || value === 'careful';
+}

package/docs/en/user-guide/webapp-guide.md

@@ -200,7 +200,24 @@ Useful when you want to run continuous processes without interruption.
    - Default is **1 hour**
    - Select the minimum time needed for your work
 5. The description text changes dynamically based on your selection (e.g., "Will automatically turn OFF after 3 hours.")
-6. Click **"Agree and Enable"**
+6. **Choose how questions are answered** ("Answer questions with the recommended option (Recommended)" / "Answer questions yourself (Careful)"; see "Answer Modes" below)
+7. Click **"Agree and Enable"**
+
+### Answer Modes (Issue #3863)
+
+The dialog that turns Auto Yes on asks how a question from the agent (one that picks a single option) is answered. You choose each time you turn it on, and the dialog always opens with **Recommended** selected.
+
+| Option | Questions | Permission confirmations |
+|--------|-----------|--------------------------|
+| **Answer questions with the recommended option (Recommended)** (default) | Answered with the option marked as recommended (a title ending in `(Recommended)` / `（推奨）`), or the default option (the cursor, else option 1) when none is. A question with two or more recommended options, or one it cannot read that far, is left for you to answer from the answer panel | Answered automatically ("allow this once" is chosen) |
+| **Answer questions yourself (Careful)** | Not answered. Auto Yes stays ON and you answer from the answer panel | Answered automatically ("allow this once" is chosen) |
+
+- While ON, the mode (**Recommended** / **Careful**; 「おまかせ」 / 「慎重」 in the Japanese UI) is shown beside the toggle — in each PC split, under the phone's composer, and after a change made from another tab, which the periodic re-read picks up
+- Connected to an older server that does not report the mode, no mode is shown (it is not assumed to be Recommended)
+- A tile on the Sessions screen offers the same dialog and, while ON, shows the mode beside its toggle (a reload or a change from another tab shows up on the next list read)
+- In the new-task dialog, picking an Auto Yes duration brings up the same two options (Recommended by default); Auto Yes is turned on in the chosen mode before the message is sent
+- A question's Submit / Cancel page and OpenCode's API questions are answered by you in either mode. Copilot's and codex's questions carry no question marker on screen, so under Careful a copilot / codex numbered list whose options do not read as permission wording (`Yes` / `Allow` and so on) is left to you as possibly a question (under Recommended it is answered as before)
+- The CLI and the API can choose it too ([CLI Operations Guide](./cli-operations-guide.md#answer-modes-recommended-and-careful-issue-3863))
 
 ### Active Duration
 
@@ -223,7 +240,8 @@ POST /api/worktrees/:id/auto-yes
 
 {
   "enabled": true,
-  "duration": 3600000 | 10800000 | 28800000  // Optional (default: 3600000)
+  "duration": 3600000 | 10800000 | 28800000,  // Optional (default: 3600000)
+  "answerMode": "recommended" | "careful"     // Optional (Issue #3863; recommended for a new grant, the current mode for one that is on)
 }
 ```
 
@@ -262,10 +280,21 @@ looks and what it depends on.
 
 See [Agent event hooks](./agent-event-hooks.md) for the per-route technical detail.
 
+### Confirmations Auto Yes Does Not Answer Are Yours to Answer (Issue #3821)
+
+Only the **server** answers automatically (the poller that reads the screen, hooks approval, and the API adjudication). **The browser sends no automatic answers.**
+
+- With Auto Yes on, a confirmation the server is not answering **shows its answer panel**: one the execution contract withholds, a screen CommandMate cannot read, a question from the agent, or a screen of an agent whose poller is not running (the concurrent poller limit was reached, for one). The panel stays hidden only while the server is answering that confirmation
+- A question OpenCode asks over its API always shows its panel, Auto Yes or not. Command Code's Review page is still answered from its manual-action card
+- Answering from the panel by hand leaves Auto Yes on. Once you start answering by hand, an automatic answer the server was in the middle of sends no further key, and for about 10 seconds after that the server does not answer that agent's confirmations (so your keys and its keys do not mix)
+- Auto Yes does not answer the screen of an agent with no poller running (hooks approval and the API adjudication run apart from the poller)
+- The single Enter Auto Yes used to send to an unreadable choice screen, and the "Auto responded" notice next to the toggle, are gone
+- A tab opened before this release that still sends an automatic answer is refused by the server with 409. A tab on a bundle from before Auto Yes marked its answers with their origin (before Issue #3820), however, cannot be told from a person answering; reload old tabs
+
 ### Important Notes
 
-- While Auto Yes is active, all confirmations are automatically answered with "Yes"
-- Important changes (file deletions, etc.) are also auto-approved, so use with caution
+- While Auto Yes is active, the server answers the agent's requests for permission to run a tool (editing, creating or deleting files, running commands, …). Important changes (file deletions, etc.) are also auto-approved, so use with caution
+- It does not answer these, and leaves them to you (their answer panel shows): a confirmation the execution contract (`autoYes`) withholds, a question from the agent under the Careful mode (or one whose recommended option cannot be told under Recommended) and its Submit / Cancel page, a screen CommandMate cannot read, a confirmation that needs checkboxes or typed text, a CLI's launch confirmations, any confirmation of an agent whose poller is not running, and the few seconds after you answer from the panel by hand (see "Confirmations Auto Yes Does Not Answer Are Yours to Answer" above)
 - You can disable it by turning off the toggle
 - Auto Yes automatically turns OFF after the selected duration
 - **When the server restarts (`/rebuild`, `commandmate stop`, etc.), an active Auto Yes is turned OFF and does not come back.** The affected instance shows **"Released by restart"** (「再起動で解除」 in the Japanese UI). The label stays until the original grant's deadline, and disappears when you turn the toggle on again or turn it off manually (it is not shown after SIGKILL or a crash). A manual OFF or an expiry does not show it

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "commandmate",
-  "version": "0.47.0",
+  "version": "0.48.0",
   "description": "No long blocks of time? Run an AI team from your phone. Git worktree sessions, task contracts and verification gates for Claude Code, Codex, Gemini CLI, Copilot, OpenCode, Antigravity and Command Code.",
   "keywords": [
     "ai-agents",
@@ -99,7 +99,7 @@
     "jsdom": "^28.1.0",
     "lucide-react": "^0.554.0",
     "mermaid": "^11.12.2",
-    "next": "^15.5.25",
+    "next": "^15.5.28",
     "next-intl": "^4.8.2",
     "next-themes": "^0.4.6",
     "postcss": "^8.5.6",

package/public/sw.js

@@ -181,30 +181,92 @@ self.addEventListener('message', function (event) {
 // This is also why there is no "close and show nothing" branch: a resolution
 // with nothing to close still shows its card. That is the contract, not an
 // oversight.
-function replaceStaleNotifications(title, options) {
+//
+// --- Issue #3798 (the resolution names its episode) -------------------------
+// A resolution may carry `resolvedEpisodeId`: the waiting episode whose card it
+// clears. It can arrive after the card of a NEWER wait in the same worktree
+// (same tag) — the next prompt's push overtook it — and closing that card would
+// hide a wait that is still open.
+//
+// A different id alone does NOT make a card newer. Delivery fails per device,
+// and the server sends a resolution only once nothing in the worktree is still
+// waiting, so a device that missed wait B's card can still be showing wait A's
+// when B's resolution arrives — A is over too, and nothing would ever close it
+// again (the server's mark is spent). Nor does the wait's start (`since`): a
+// structured since is reused by the next wait and can be older than the
+// observation, and two waits can start and end in one millisecond.
+//
+// Newer is proved by `order`: a per-worktree counter the server advances, in
+// one database statement, for every episode-named card it sends and for every
+// resolution it decides (`nextPromptOrder`). A wait open when the resolution
+// was decided would have stopped it, so a card whose order is greater than the
+// resolution's can only be a wait that opened later.
+//
+// So: a card of another episode with a greater order is closed and shown again
+// with the same content, silently (`silent: true`, `renotify: false`), INSTEAD
+// of the resolution; every other card — the resolved episode's, one naming no
+// episode or carrying no order, one sent before the resolution — is closed and
+// the resolution shown in its place, as before. Every branch still calls
+// `showNotification` exactly once, so the `userVisibleOnly` contract above
+// holds. A resolution without the id or the order (a server before #3798)
+// clears the tag as it always has.
+function isNewerThanResolution(card, resolvedEpisodeId, resolvedOrder) {
+  var data = card.data || {};
+  return (
+    typeof resolvedEpisodeId === 'string' &&
+    typeof resolvedOrder === 'number' &&
+    typeof data.episodeId === 'string' &&
+    data.episodeId !== resolvedEpisodeId &&
+    typeof data.order === 'number' &&
+    data.order > resolvedOrder
+  );
+}
+
+function replaceStaleNotifications(title, options, resolvedEpisodeId, resolvedOrder) {
   var registration = self.registration;
   var tag = options.tag;
   var closing;
 
   if (!tag || typeof registration.getNotifications !== 'function') {
-    closing = Promise.resolve();
+    closing = Promise.resolve(null);
   } else {
     closing = registration
       // Correct either way: whether an engine hands back every card carrying the tag or only the newest one, the loop closes exactly what it was handed (iOS is still unmeasured on this point — Issue #2155).
       .getNotifications({ tag: tag })
       .then(function (stale) {
+        var newer = null;
         for (var i = 0; i < stale.length; i++) {
+          if (
+            isNewerThanResolution(stale[i], resolvedEpisodeId, resolvedOrder) &&
+            // Of several, the card the server sent last.
+            (newer === null || stale[i].data.order > newer.data.order)
+          ) {
+            newer = stale[i];
+          }
           stale[i].close();
         }
+        return newer;
       })
       .catch(function (_err) {
         // A registration that cannot enumerate its notifications still has to
         // show one. Showing the replacement below is what keeps the promise;
         // on this path the tag alone collapses the stale card on most engines.
+        return null;
       });
   }
 
-  return closing.then(function () {
+  return closing.then(function (newer) {
+    if (newer) {
+      return registration.showNotification(newer.title, {
+        body: newer.body,
+        tag: tag,
+        renotify: false,
+        silent: true,
+        icon: newer.icon || options.icon,
+        badge: newer.badge || options.badge,
+        data: newer.data,
+      });
+    }
     return registration.showNotification(title, options);
   });
 }
@@ -243,6 +305,16 @@ self.addEventListener('push', function (event) {
   // different, louder instruction.
   if (resolved) options.silent = true;
 
+  // Issue #3798: a waiting card remembers its episode, so a later resolution
+  // can tell it from the card it is clearing. Absent from older payloads.
+  if (typeof payload.episodeId === 'string') options.data.episodeId = payload.episodeId;
+  // ...and its place in the worktree's order, so a later resolution can tell
+  // whether the card was sent after the resolution was decided.
+  if (typeof payload.order === 'number') options.data.order = payload.order;
+  var resolvedEpisodeId =
+    resolved && typeof payload.resolvedEpisodeId === 'string' ? payload.resolvedEpisodeId : null;
+  var resolvedOrder = resolved && typeof payload.order === 'number' ? payload.order : null;
+
   // --- Issue #2155 ---------------------------------------------------------
   // Every TAGGED push takes the close-then-show path, not just resolutions.
   // Safari/iOS does not collapse same-tag cards on a plain `showNotification`,
@@ -253,7 +325,7 @@ self.addEventListener('push', function (event) {
   // nothing to replace and goes straight to `showNotification`.
   event.waitUntil(
     options.tag
-      ? replaceStaleNotifications(title, options)
+      ? replaceStaleNotifications(title, options, resolvedEpisodeId, resolvedOrder)
       : self.registration.showNotification(title, options)
   );
 });

package/release-notes/0.47.1.json

@@ -0,0 +1,20 @@
+{
+  "version": "0.47.1",
+  "date": "2026-10-23",
+  "highlight": {
+    "ja": "Auto-Yes が実行契約の制限を守らずに答えたり、危険なコマンドを見落としたりする問題を直しました。",
+    "en": "Fixed cases where Auto-Yes answered without honoring the execution contract's limits or missed a dangerous command."
+  },
+  "added": [],
+  "improved": [],
+  "fixed": [
+    {
+      "ja": "実行契約を一時的に読めなかったとき、Auto-Yes が契約の制限を無視して答えていた問題を直しました。読めない間は答えません。",
+      "en": "Fixed Auto-Yes answering without the contract's limits when the execution contract briefly could not be read. It now waits instead."
+    },
+    {
+      "ja": "承認を求めるコマンドの途中に「>」で始まる行があると、その上の危険なコマンドが拒否の判定から漏れていた問題を直しました。",
+      "en": "Fixed a dangerous command being missed by the deny check when the command awaiting approval contained a line starting with \">\"."
+    }
+  ]
+}

package/release-notes/0.47.2.json

@@ -0,0 +1,20 @@
+{
+  "version": "0.47.2",
+  "date": "2026-10-23",
+  "highlight": {
+    "ja": "依存パッケージの脆弱性を直しました。Next.js の重大な脆弱性への対応を含みます。",
+    "en": "Fixed vulnerabilities in dependencies, including a critical one in Next.js."
+  },
+  "added": [],
+  "improved": [],
+  "fixed": [
+    {
+      "ja": "Next.js を更新し、画像の最適化で外部からコードを実行されうる重大な脆弱性と、サービス停止の脆弱性を直しました。",
+      "en": "Updated Next.js to fix a critical vulnerability that could allow remote code execution through image optimization, and a denial-of-service issue."
+    },
+    {
+      "ja": "Markdown の表示に使うライブラリを更新し、高リスクの脆弱性を直しました。",
+      "en": "Updated libraries used to render Markdown to fix high-severity vulnerabilities."
+    }
+  ]
+}

package/release-notes/0.48.0.json

@@ -0,0 +1,57 @@
+{
+  "version": "0.48.0",
+  "date": "2026-10-25",
+  "highlight": {
+    "ja": "Auto-Yes の答え方を見直しました。質問への答え方を「おまかせ」と「慎重」から選べ、判断できない確認には答えず人に返します。",
+    "en": "Auto-Yes now lets you choose how it answers (Recommended or Careful), and leaves confirmations it cannot judge to you."
+  },
+  "added": [
+    {
+      "ja": "Auto-Yes に答え方のモードを追加しました。おまかせは質問に推奨の選択肢で答え、慎重は質問を人に任せます。",
+      "en": "Added answer modes to Auto-Yes: Recommended answers questions with the recommended option, Careful leaves questions to you."
+    }
+  ],
+  "improved": [],
+  "fixed": [
+    {
+      "ja": "Auto-Yes が許可の確認で、常に許可やモード変更ではなく「今回だけ許可」を選ぶようにしました。",
+      "en": "Auto-Yes now picks only the allow-this-time option on permission prompts, never permanent permission or mode changes."
+    },
+    {
+      "ja": "Auto-Yes が根拠の無い y/n や読めない選択画面に答えないようにし、ブラウザからの自動回答をやめました。",
+      "en": "Auto-Yes no longer answers unverified y/n prompts or unreadable choice screens, and the browser no longer answers automatically."
+    },
+    {
+      "ja": "送信に失敗した、または届いたか分からない回答を、Auto-Yes が同じ確認へ打ち直す問題を直しました。",
+      "en": "Fixed Auto-Yes re-sending an answer to the same prompt after a failed or uncertain send."
+    },
+    {
+      "ja": "確認画面の種類を一度で判定し、Auto-Yes とチャットの表示が食い違わないようにしました。",
+      "en": "Confirmation screens are now classified once, so Auto-Yes and the chat view no longer disagree about them."
+    },
+    {
+      "ja": "Antigravity の番号付きの画面に、Auto-Yes が既定で答えないようにしました。",
+      "en": "Auto-Yes no longer answers numbered Antigravity screens by default."
+    },
+    {
+      "ja": "Auto-Yes が答えた後に、答えていないという誤った通知が出る問題を直しました。",
+      "en": "Fixed false notifications saying Auto-Yes had not answered after it did."
+    },
+    {
+      "ja": "狭い・低いペインで Claude の確認画面を見落とす問題を直しました。",
+      "en": "Fixed Claude confirmation screens being missed in narrow or short panes."
+    },
+    {
+      "ja": "ターミナルの表示が、購読の切り替えで止まったり切断と表示されたりする問題を直しました。",
+      "en": "Fixed the terminal view stopping or showing as disconnected when switching subscriptions."
+    },
+    {
+      "ja": "サーバーと更新のログファイルの権限を本人だけが読める設定にそろえ、大きくなったら切り替えるようにしました。",
+      "en": "Server and update log files are now readable only by you and are rotated when they grow large."
+    },
+    {
+      "ja": "依存パッケージを更新し、高リスクの脆弱性を直しました。",
+      "en": "Updated a dependency to fix a high-severity vulnerability."
+    }
+  ]
+}

package/scripts/hooks/cmate-agent-event.sh

@@ -71,6 +71,14 @@ json_string_field() {
     sed -n 's/.*"'"$2"'"[[:space:]]*:[[:space:]]*"\([^"]*\)".*/\1/p'
 }
 
+# Extract a flat JSON non-negative integer field (digits only). A value that is
+# not a bare run of digits — a string, a negative or fractional number — yields
+# nothing. Text inside a string cannot produce the match: its quotes are escaped.
+json_integer_field() {
+  printf '%s' "$1" | tr -d '\n' |
+    sed -n 's/.*"'"$2"'"[[:space:]]*:[[:space:]]*\([0-9][0-9]*\)[[:space:]]*[,}].*/\1/p'
+}
+
 # Escape a value for embedding in a JSON string literal.
 json_escape() {
   printf '%s' "$1" | sed -e 's/\\/\\\\/g' -e 's/"/\\"/g'
@@ -317,6 +325,20 @@ if [ "$EVENT" = "stop" ] && [ "$TOOL" = "claude" ] && [ -n "$HOOK_JSON" ]; then
       ;;
   esac
 fi
+# Issue #3820 (design docs/design/auto-yes-measurement-3820.md §2.4). agy's
+# `PostToolUse` names its call by `stepIdx` (unique within a conversation; the
+# conversation is the `sessionId` above), and the server ties it to the
+# `PreToolUse` of the same call — which reaches the permission route directly,
+# not through here — to tell when the call ended. Forwarded as a number on
+# antigravity's post_tool_use only, so every other tool and event keeps the
+# body it had; omitted when the payload has none (an older agy), which the
+# server reads as before. Bounded to 15 digits so it stays a safe integer.
+if [ "$EVENT" = "post_tool_use" ] && [ "$TOOL" = "antigravity" ] && [ -n "$HOOK_JSON" ]; then
+  STEP_IDX="$(json_integer_field "$HOOK_JSON" 'stepIdx')"
+  if [ -n "$STEP_IDX" ] && [ "${#STEP_IDX}" -le 15 ]; then
+    BODY="$BODY,\"stepIdx\":$STEP_IDX"
+  fi
+fi
 BODY="$BODY}"
 
 # Token via --header rather than the command line of a subprocess: argv is world