@liuyoumi/codex-history 0.5.0 → 0.6.0

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.6.0 - 2026-07-13
+
+### Changed
+
+- Replace typed short-id and command-phrase purge confirmations with a default-no `[y/N]` prompt. Only explicit `y` or `yes` proceeds.
+
+## 0.5.1 - 2026-05-30
+
+### Fixed
+
+- Remove prefixed global-state keys that contain a purged thread id, such as composer draft keys stored as `local:<threadId>`.
+
 ## 0.5.0 - 2026-05-29
 
 ### Changed

package/README.en.md

@@ -57,7 +57,7 @@ codex-history purge --grep "Astro"
 codex-history purge-orphans
 ```
 
-`purge` prints the resolved conversation and asks you to type the standard short id before it deletes anything:
+`purge` prints the resolved conversation, then shows a default-no `[y/N]` prompt. It deletes only after an explicit `y` or `yes`; pressing Enter, entering `n`, or entering anything else cancels:
 
 ```text
 About to purge this local Codex conversation:
@@ -68,7 +68,7 @@ cwd: /Users/me/Projects/example
 updated: 2026-05-28T03:16:01.959Z
 
 This cannot be undone.
-Type 019e6885 to confirm:
+Proceed with permanent deletion? [y/N]:
 ```
 
 ## Commands
@@ -147,7 +147,7 @@ codex-history purge 019e6885
 codex-history purge 019e6885 019e6874
 ```
 
-When multiple targets are provided, the tool resolves all targets and prints a batch plan before deletion. If any id is missing, ambiguous, or active, the whole batch is refused before mutation. Interactive batch purge requires typing `purge-selected`.
+When multiple targets are provided, the tool resolves all targets and prints a batch plan before deletion. If any id is missing, ambiguous, or active, the whole batch is refused before mutation. Interactive batch purge uses the same default-no `[y/N]` prompt and proceeds only after `y` or `yes`.
 
 You can also select local conversations with filters:
 
@@ -158,7 +158,7 @@ codex-history purge --archived
 codex-history purge --cwd /Users/me/Projects/example --grep "Astro"
 ```
 
-`--cwd`, `--grep`, and `--archived` can be combined. Combined filters delete only conversations that match every provided condition. `--cwd` matches working-directory path fragments, while `--grep` matches only title, first user message, and preview. By default, filter mode matches non-archived conversations only; use `--archived` to target archived conversations. Filtered purge prints a batch plan and matched cwd values, then requires typing `purge-selected`. Filters cannot be combined with explicit ids.
+`--cwd`, `--grep`, and `--archived` can be combined. Combined filters delete only conversations that match every provided condition. `--cwd` matches working-directory path fragments, while `--grep` matches only title, first user message, and preview. By default, filter mode matches non-archived conversations only; use `--archived` to target archived conversations. Filtered purge prints a batch plan and matched cwd values, then uses the default-no `[y/N]` prompt. Filters cannot be combined with explicit ids.
 
 For scripts or non-interactive shells, use `--force`:
 
@@ -170,6 +170,8 @@ codex-history purge --cwd /Users/me/Projects/example --force
 
 `--force` skips only interactive confirmation. It still keeps schema validation, active-thread protection, and post-purge verification.
 
+During deletion, `.codex-global-state.json` and `.codex-global-state.json.bak` are structurally rewritten to remove global-state keys that contain the target thread id, such as composer draft keys stored as `local:<threadId>`.
+
 ### `purge-orphans`
 
 Remove orphaned local data: conversations whose `state_5.sqlite.threads.rollout_path` points to a missing session or archived session file, and logs-only records that remain in `logs_2.sqlite.logs` without a matching thread in the `threads` table.
@@ -178,7 +180,7 @@ Remove orphaned local data: conversations whose `state_5.sqlite.threads.rollout_
 codex-history purge-orphans
 ```
 
-The command first prints a cleanup plan, affected SQLite row counts, files to delete, and an estimated local disk space impact. You must type `purge-orphans` before it executes.
+The command first prints a cleanup plan, affected SQLite row counts, files to delete, and an estimated local disk space impact. It then shows the default-no `[y/N]` prompt and executes only after `y` or `yes`.
 
 For scripts or non-interactive shells, use `--force`:
 

package/README.md

@@ -57,7 +57,7 @@ codex-history purge --grep "Astro"
 codex-history purge-orphans
 ```
 
-`purge` 会先展示解析到的对话信息，并要求你输入标准短 id，确认后才会删除：
+`purge` 会先展示解析到的对话信息，再显示默认拒绝的 `[y/N]` 确认提示。只有显式输入 `y` 或 `yes` 才会删除；直接回车、输入 `n` 或任何其他内容都会取消：
 
 ```text
 About to purge this local Codex conversation:
@@ -68,7 +68,7 @@ cwd: /Users/me/Projects/example
 updated: 2026-05-28T03:16:01.959Z
 
 This cannot be undone.
-Type 019e6885 to confirm:
+Proceed with permanent deletion? [y/N]:
 ```
 
 ## 命令
@@ -147,7 +147,7 @@ codex-history purge 019e6885
 codex-history purge 019e6885 019e6874
 ```
 
-删除多个目标时，工具会先解析全部目标并展示批量计划；只要任意一个 id 不存在、不唯一，或命中 active thread，整个批量操作都会拒绝执行，不会部分删除。交互式批量删除需要输入 `purge-selected` 确认。
+删除多个目标时，工具会先解析全部目标并展示批量计划；只要任意一个 id 不存在、不唯一，或命中 active thread，整个批量操作都会拒绝执行，不会部分删除。交互式批量删除同样使用默认拒绝的 `[y/N]` 确认提示，只有输入 `y` 或 `yes` 才会继续。
 
 也可以直接用过滤条件选择要删除的本地对话：
 
@@ -158,7 +158,7 @@ codex-history purge --archived
 codex-history purge --cwd /Users/me/Projects/example --grep "Astro"
 ```
 
-`--cwd`、`--grep`、`--archived` 可以组合，组合后只删除同时满足全部条件的对话。`--cwd` 会匹配工作目录路径片段，`--grep` 只匹配标题、首条用户消息和预览。默认只匹配未归档对话；如果要删除已归档对话，请使用 `--archived`。过滤式删除会展示批量计划和匹配到的 cwd，并要求输入 `purge-selected` 确认。过滤条件不能和 id 同时使用。
+`--cwd`、`--grep`、`--archived` 可以组合，组合后只删除同时满足全部条件的对话。`--cwd` 会匹配工作目录路径片段，`--grep` 只匹配标题、首条用户消息和预览。默认只匹配未归档对话；如果要删除已归档对话，请使用 `--archived`。过滤式删除会展示批量计划和匹配到的 cwd，并使用默认拒绝的 `[y/N]` 确认提示。过滤条件不能和 id 同时使用。
 
 脚本或非交互环境可以使用 `--force`：
 
@@ -170,6 +170,8 @@ codex-history purge --cwd /Users/me/Projects/example --force
 
 `--force` 只跳过交互确认，不会跳过数据结构校验、active thread 保护和删除后的验证。
 
+删除时会结构化重写 `.codex-global-state.json` 和 `.codex-global-state.json.bak`，移除包含目标 thread id 的全局状态键，例如输入草稿缓存里的 `local:<threadId>`。
+
 ### `purge-orphans`
 
 清理本地孤儿数据：包括 `state_5.sqlite.threads.rollout_path` 指向的 session / archived session 文件已经不存在的对话，以及只残留在 `logs_2.sqlite.logs` 中、但 `threads` 表里已经没有对应 thread 的日志记录。
@@ -178,7 +180,7 @@ codex-history purge --cwd /Users/me/Projects/example --force
 codex-history purge-orphans
 ```
 
-该命令会先展示清理计划、受影响的 SQLite 行数、将删除的文件数量，以及估算的本地磁盘空间影响。确认后需要输入 `purge-orphans` 才会执行。
+该命令会先展示清理计划、受影响的 SQLite 行数、将删除的文件数量，以及估算的本地磁盘空间影响。随后会显示默认拒绝的 `[y/N]` 确认提示；只有输入 `y` 或 `yes` 才会执行。
 
 脚本或非交互环境可以使用 `--force`：
 

package/dist/cli.js

@@ -580,7 +580,7 @@ function removeThreadReferences(value, threadId) {
     let changed = false;
     const next = {};
     for (const [key, child] of Object.entries(value)) {
-      if (key === threadId) {
+      if (key.includes(threadId)) {
         changed = true;
         continue;
       }
@@ -1105,6 +1105,12 @@ function executePurgeOrphansPlanCommand(paths, plan) {
   return executePurgeOrphans(paths, plan);
 }
 
+// src/core/confirmation.ts
+var affirmativeResponses = /* @__PURE__ */ new Set(["y", "yes"]);
+function isDestructiveActionConfirmed(answer) {
+  return affirmativeResponses.has(answer.trim().toLowerCase());
+}
+
 // src/core/output.ts
 function printOutput(value) {
   if (typeof value === "string") {
@@ -1180,12 +1186,18 @@ program.command("purge").argument("[threadIds...]", "Codex thread id(s) or uniqu
     }
     if (plan.plans.length === 1 && !useBatchConfirmation) {
       if (!force) {
-        await confirmPurge(plan.plans[0]);
+        await confirmDestructiveAction(
+          "Purge requires an interactive terminal. Use --force to skip confirmation.",
+          formatPurgeConfirmation(plan.plans[0])
+        );
       }
       return formatPurgeResult(executePurgePlanCommand(paths, plan.plans[0]));
     }
     if (!force) {
-      await confirmBatchPurge(plan);
+      await confirmDestructiveAction(
+        "Batch purge requires an interactive terminal. Use --force to skip confirmation.",
+        formatBatchPurgeConfirmation(plan)
+      );
     }
     return formatBatchPurgeResult(executeBatchPurgePlanCommand(paths, plan));
   })
@@ -1199,7 +1211,10 @@ program.command("purge-orphans").option("--force", "Skip interactive confirmatio
       return formatPurgeOrphansPlan(plan);
     }
     if (!force) {
-      await confirmPurgeOrphans(plan);
+      await confirmDestructiveAction(
+        "purge-orphans requires an interactive terminal. Use --force to skip confirmation.",
+        formatPurgeOrphansConfirmation(plan)
+      );
     }
     return formatPurgeOrphansResult(executePurgeOrphansPlanCommand(paths, plan));
   })
@@ -1234,58 +1249,19 @@ function parsePretty(value) {
 function shouldUsePager(options) {
   return Boolean(options.limit === void 0 && process.stdout.isTTY);
 }
-async function confirmPurge(plan) {
-  if (!process.stdin.isTTY || !process.stdout.isTTY) {
-    throw new SafetyRefusalError("Purge requires an interactive terminal. Use --force to skip confirmation.");
-  }
-  const expected = shortId(plan.target.id);
-  process.stdout.write(formatPurgeConfirmation(plan));
-  const readline = createInterface({
-    input: process.stdin,
-    output: process.stdout
-  });
-  try {
-    const answer = await readline.question(`Type ${colorize("yellow", expected)} to confirm: `);
-    if (answer.trim() !== expected) {
-      throw new SafetyRefusalError("Confirmation did not match. No local Codex data was modified.");
-    }
-  } finally {
-    readline.close();
-  }
-}
-async function confirmBatchPurge(plan) {
-  if (!process.stdin.isTTY || !process.stdout.isTTY) {
-    throw new SafetyRefusalError("Batch purge requires an interactive terminal. Use --force to skip confirmation.");
-  }
-  const expected = "purge-selected";
-  process.stdout.write(formatBatchPurgeConfirmation(plan));
-  const readline = createInterface({
-    input: process.stdin,
-    output: process.stdout
-  });
-  try {
-    const answer = await readline.question(`Type ${colorize("yellow", expected)} to confirm: `);
-    if (answer.trim() !== expected) {
-      throw new SafetyRefusalError("Confirmation did not match. No local Codex data was modified.");
-    }
-  } finally {
-    readline.close();
-  }
-}
-async function confirmPurgeOrphans(plan) {
+async function confirmDestructiveAction(terminalRefusalMessage, confirmationOutput) {
   if (!process.stdin.isTTY || !process.stdout.isTTY) {
-    throw new SafetyRefusalError("purge-orphans requires an interactive terminal. Use --force to skip confirmation.");
+    throw new SafetyRefusalError(terminalRefusalMessage);
   }
-  const expected = "purge-orphans";
-  process.stdout.write(formatPurgeOrphansConfirmation(plan));
+  process.stdout.write(confirmationOutput);
   const readline = createInterface({
     input: process.stdin,
     output: process.stdout
   });
   try {
-    const answer = await readline.question(`Type ${colorize("yellow", expected)} to confirm: `);
-    if (answer.trim() !== expected) {
-      throw new SafetyRefusalError("Confirmation did not match. No local Codex data was modified.");
+    const answer = await readline.question(`Proceed with permanent deletion? ${colorize("yellow", "[y/N]")}: `);
+    if (!isDestructiveActionConfirmed(answer)) {
+      throw new SafetyRefusalError("Confirmation was declined. No local Codex data was modified.");
     }
   } finally {
     readline.close();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@liuyoumi/codex-history",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "CLI for listing and safely purging local Codex conversation history",
   "type": "module",
   "bin": {