@gkorepanov/ccodex 0.4.20 → 0.4.23

package/scripts/install-claude-stack.sh

@@ -20,9 +20,32 @@ done
 
 if ! command -v claude >/dev/null 2>&1; then
   echo "codex MCP server: skipped (claude CLI not found)" >&2
-elif claude mcp get codex >/dev/null 2>&1; then
-  echo "codex MCP server: already registered"
 else
-  claude mcp add --scope user codex -- codex mcp-server
-  echo "codex MCP server: registered (user scope)"
+  # Inherited tools take precedence over the agent's inline server declaration.
+  node --input-type=module <<'NODE'
+import { execFileSync } from "node:child_process";
+import { existsSync, readFileSync, renameSync, statSync, writeFileSync } from "node:fs";
+import { homedir } from "node:os";
+import { join } from "node:path";
+
+const configDir = process.env.CLAUDE_CONFIG_DIR;
+const legacyPath = join(configDir || join(homedir(), ".claude"), ".config.json");
+const configPath = existsSync(legacyPath) ? legacyPath : join(configDir || homedir(), ".claude.json");
+const config = existsSync(configPath) ? JSON.parse(readFileSync(configPath, "utf8")) : {};
+const server = config.mcpServers?.codex;
+const timeout = Math.max(server?.timeout ?? 0, 86_400_000);
+if (server) {
+  if (server.timeout !== timeout) {
+    server.timeout = timeout;
+    const temporaryPath = `${configPath}.${process.pid}.tmp`;
+    writeFileSync(temporaryPath, `${JSON.stringify(config, null, 2)}\n`, { mode: statSync(configPath).mode & 0o777 });
+    renameSync(temporaryPath, configPath);
+  }
+} else {
+  execFileSync("claude", ["mcp", "add-json", "--scope", "user", "codex", JSON.stringify({
+    type: "stdio", command: "codex", args: ["mcp-server"], timeout,
+  })], { stdio: "inherit" });
+}
+console.log("codex MCP server: configured (user scope, timeout at least 24 hours)");
+NODE
 fi

package/vendor/codex/continuation.md

@@ -19,6 +19,11 @@ Budget:
 Work from evidence:
 Use the current worktree and external state as authoritative. Previous conversation context can help locate relevant work, but inspect the current state before relying on it. Improve, replace, or remove existing work as needed to satisfy the actual objective.
 
+No-progress check:
+- Classify the previous goal turn as progress, a verified wait, or no progress. Progress changes authoritative state, completes work, or yields evidence that changes the next action; status restatements and unexecuted plans are no progress.
+- A verified wait polls a specific process, session, job, or tool handle confirmed live now. Conversation, intent, prior output, or a lock or state file alone is insufficient. Treat work as stopped only when authoritative state says it is terminal or its handle is missing. An observation timeout or transient polling failure is not terminal: re-poll the same handle or inspect other authoritative state; never restart solely because observation expired.
+- Revalidate a no-progress turn and take the next available safe action. If none exists because the same genuine blocker remains, report it and leave the goal active until the blocked audit threshold is met. Treat equivalent blockers as the same condition across turns even when their wording or stated next step changes.
+
 Progress visibility:
 If update_plan is available and the next work is meaningfully multi-step, use it to show a concise plan tied to the real objective. Keep the plan current as steps complete or the next best action changes. Skip planning overhead for trivial one-step progress, and do not treat a plan update as a substitute for doing the work.