commandmate 0.40.0 → 0.40.1

package/dist/server/src/lib/detection/model-info-extractor.js

@@ -62,7 +62,7 @@
  * @see Issue #1784, Phase 2 of the model/effort visibility series
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.ANTIGRAVITY_MODEL_ID_EFFORT_PATTERN = exports.COMMAND_CODE_BANNER_MODELS_PATTERN = exports.OPENCODE_STEP_MODEL_PATTERN = exports.COPILOT_MODEL_CHANGE_PATTERN = exports.ANTIGRAVITY_BANNER_MODEL_PATTERN = exports.ANTIGRAVITY_STATUS_BAR_HINT_PATTERN = exports.CLAUDE_MODEL_SWITCH_PATTERN = exports.CLAUDE_STARTUP_BANNER_PATTERN = exports.CODEX_STATUS_BAR_WITH_TRAILER_PATTERN = exports.CODEX_FOOTER_MODEL_PATTERN = exports.REASONING_EFFORT_LEVELS = void 0;
+exports.ANTIGRAVITY_MODEL_ID_EFFORT_PATTERN = exports.COMMAND_CODE_BANNER_MODELS_PATTERN = exports.OPENCODE_STEP_MODEL_PATTERN = exports.COPILOT_MODEL_CHANGE_PATTERN = exports.ANTIGRAVITY_BANNER_MODEL_PATTERN = exports.ANTIGRAVITY_STATUS_BAR_HINT_PATTERN = exports.CLAUDE_MODEL_SWITCH_PATTERN = exports.CLAUDE_STARTUP_BANNER_PATTERN = exports.CODEX_STATUS_BAR_WITH_TRAILER_PATTERN = exports.CODEX_FOOTER_EFFORT_SLOT_PATTERN = exports.CODEX_FOOTER_MODEL_PATTERN = exports.REASONING_EFFORT_LEVELS = void 0;
 exports.resolveEffortToken = resolveEffortToken;
 exports.extractModelInfo = extractModelInfo;
 exports.deriveEffortFromModelId = deriveEffortFromModelId;
@@ -72,11 +72,27 @@ const cli_patterns_1 = require("./cli-patterns");
 /**
  * The reasoning-effort vocabulary these tools actually print.
  *
- * `minimal` and `xhigh` are the ends Codex exposes; Claude prints `xhigh` too.
+ * `minimal` and `xhigh` are the ends Codex exposed until 0.155; Claude prints
+ * `xhigh` too. Issue #2835 adds the three levels above `xhigh` that codex 0.155.1
+ * defines (`ReasoningEffort` in `codex-rs/protocol/src/openai_models.rs`, tag
+ * `rust-v0.155.1`: `max` / `ultra` / `persistent`, drawn in the status bar
+ * verbatim by `status_line_reasoning_effort_label`). Its `None` is drawn as
+ * `default` and is deliberately NOT a level — it names no effort. Command Code's
+ * `with max effort` banner resolves through the same list.
+ *
  * Anything outside this list is treated as "not an effort token", which is what
  * keeps a stray word at the end of a status bar from being published as one.
  */
-exports.REASONING_EFFORT_LEVELS = ['minimal', 'low', 'medium', 'high', 'xhigh'];
+exports.REASONING_EFFORT_LEVELS = [
+    'minimal',
+    'low',
+    'medium',
+    'high',
+    'xhigh',
+    'max',
+    'ultra',
+    'persistent',
+];
 /**
  * Longest string accepted as a model name.
  *
@@ -156,7 +172,23 @@ function resolveEffortToken(token, options = {}) {
  * optional `\s+<keyword>` are adjacent, never nested (ReDoS-safe, same rule
  * `cli-patterns.ts` documents).
  */
-exports.CODEX_FOOTER_MODEL_PATTERN = /^\s*([^\s·]+)(?:\s+(minimal|low|medium|high|xhigh)\b)?/i;
+exports.CODEX_FOOTER_MODEL_PATTERN = /^\s*([^\s·]+)(?:\s+(minimal|low|medium|high|xhigh|max|ultra|persistent)\b)?/i;
+/**
+ * The head of a Codex status bar that has a word where the effort goes
+ * (Issue #2835).
+ *
+ * codex draws `<model> <effort>` and, for an effort it has no name for, still
+ * draws a word there: `default` for `None` (`status_line_reasoning_effort_label`,
+ * codex 0.155.1; live in `tests/fixtures/agent-mode-2592/codex-default.txt`), or
+ * a model-defined value verbatim. A head whose second token is a word is
+ * therefore a bar that SHOWS an effort, even when {@link CODEX_FOOTER_MODEL_PATTERN}
+ * cannot name it. The legacy o4-mini head (`o4-mini            50% left`) has no
+ * such slot — its second token starts with a digit — and neither does a status
+ * line configured to show the model alone.
+ *
+ * No /g. No nested quantifiers: two adjacent runs and a lookahead.
+ */
+exports.CODEX_FOOTER_EFFORT_SLOT_PATTERN = /^\s*[^\s·]+\s+[A-Za-z][A-Za-z_-]*(?=\s|$)/;
 /**
  * A codex status bar with something AFTER the path (Issue #2592).
  *
@@ -202,7 +234,8 @@ function readCodexFooter(line) {
     const separator = line.indexOf('·');
     if (separator < 0)
         return null;
-    const match = exports.CODEX_FOOTER_MODEL_PATTERN.exec(line.slice(0, separator));
+    const head = line.slice(0, separator);
+    const match = exports.CODEX_FOOTER_MODEL_PATTERN.exec(head);
     if (!match)
         return null;
     const model = match[1];
@@ -219,6 +252,13 @@ function readCodexFooter(line) {
     // beside it is what separates chrome from prose.
     if (effort === null && !/\d/.test(model))
         return null;
+    // Issue #2835: a bar that shows an effort this module cannot name says the
+    // latched effort is no longer current. Publishing the old one would be a
+    // wrong value, which is worse than none — the case that found it was a
+    // session moved from `xhigh` to `max` while `max` was not yet a level.
+    if (effort === null && exports.CODEX_FOOTER_EFFORT_SLOT_PATTERN.test(head)) {
+        return { model, effort: null, effortUnreadable: true };
+    }
     return { model, effort };
 }
 // =============================================================================
@@ -612,11 +652,10 @@ function readOpencodeStepMarker(line) {
  *    footer reads `? for shortcuts · taste on`), so everything from the dot on
  *    is dropped, and the dot itself is optional.
  *  - **The effort is read when the banner prints one, through the shared
- *    vocabulary.** `low` / `high` resolve; `max` is not a
- *    {@link ReasoningEffort} and answers null rather than widening a list every
- *    other reader and the UI type depend on. The model half is published either
- *    way: the ` with … effort` frame delimits it cleanly, so nothing is
- *    half-read.
+ *    vocabulary.** `low` / `high` / `max` resolve (`max` since Issue #2835,
+ *    which added it to {@link REASONING_EFFORT_LEVELS} for codex; before that it
+ *    answered null). The model half is published either way: the
+ *    ` with … effort` frame delimits it cleanly, so nothing is half-read.
  *
  * ## After a `/model` switch (measured, 1.49.0)
  *

package/dist/server/src/lib/session/agent-event-state.js

@@ -1363,6 +1363,13 @@ function getLastKnownAgentModel(worktreeId, cliToolId, instanceId) {
  * which is the honest state for gemini/copilot and for any session whose chrome
  * this module has no rule for.
  *
+ * **The one exception is an effort the frame shows but cannot name** (Issue
+ * #2835, `info.effortUnreadable`). A codex bar that draws `default` or a
+ * model-defined value where `xhigh` used to be is not "not showing" the effort
+ * — it is showing a different one. Keeping `xhigh` would publish a value the
+ * session is no longer running at, so the effort half is dropped to null and
+ * the model half latches as usual.
+ *
  * @param info - {@link import('../../lib/detection/model-info-extractor').extractModelInfo}'s answer
  */
 function recordCapturedModelInfo(worktreeId, cliToolId, instanceId, info, at = Date.now()) {
@@ -1373,7 +1380,7 @@ function recordCapturedModelInfo(worktreeId, cliToolId, instanceId, info, at = D
     const model = info.model ? info.model.slice(0, agent_event_types_1.MAX_EVENT_DETAIL_LENGTH) : (previous?.model ?? null);
     capturedModelInfo.set(key, {
         model,
-        effort: info.effort ?? previous?.effort ?? null,
+        effort: info.effortUnreadable ? null : (info.effort ?? previous?.effort ?? null),
         // Issue #2361: the change stamp moves only when the model half takes a
         // different value. A banner re-read on every poll keeps the stamp where the
         // first sighting put it, so it never out-dates a hook by mere repetition.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "commandmate",
-  "version": "0.40.0",
+  "version": "0.40.1",
   "description": "A local control plane for agent CLIs — orchestration and visibility for Claude Code, Codex, Gemini CLI, and more across Git worktrees",
   "keywords": [
     "claude-code",

package/release-notes/0.40.1.json

@@ -0,0 +1,20 @@
+{
+  "version": "0.40.1",
+  "date": "2026-09-22",
+  "highlight": {
+    "ja": "Codex の推論の強さが max のとき、セッション一覧とインスタンス一覧に表示されない問題を直しました。",
+    "en": "Fixed Codex sessions with max reasoning effort not showing that effort in the session and instance lists."
+  },
+  "added": [],
+  "improved": [],
+  "fixed": [
+    {
+      "ja": "Codex の推論の強さが max・ultra・persistent のとき、一覧に表示されるようになりました。",
+      "en": "Codex reasoning effort set to max, ultra, or persistent now appears in the session and instance lists."
+    },
+    {
+      "ja": "Codex で推論の強さを切り替えたあと、前の値が表示され続ける問題を直しました。",
+      "en": "Fixed the previous reasoning effort staying on screen after switching effort in a Codex session."
+    }
+  ]
+}