@bitkyc08/opencodex 2.6.2-preview.20260628 → 2.6.2

package/README.md

@@ -264,6 +264,14 @@ Codex-visible context cap, `modelContextWindows` for model-specific caps, and
 `["text", "image"]`. Context values cap live `/models` metadata; they never raise a smaller live
 context window. See the configuration reference for the full field list.
 
+> **GLM-5.2 1M context via Z.AI:** through the `openai-chat` adapter, both `glm-5.2`
+> and `glm-5.2[1m]` work — opencodex strips the trailing `[1m]` suffix before
+> sending the request, since OpenAI-compatible endpoints reject the bracketed id
+> (Z.AI 400 code 1211). The `[1m]` suffix is a Claude-Code / Anthropic-endpoint
+> convention; to use it natively, point the `anthropic` adapter at Z.AI's coding
+> base (`https://api.z.ai/api/coding/paas/v4`). Set the 1M context window via the
+> model catalog (`modelContextWindows`), not the model name.
+
 Local models work too. Point opencodex at any OpenAI-compatible server running on your machine:
 
 ```json

package/bin/ocx.mjs

@@ -8,7 +8,7 @@
  * Node shim. (Dev still runs `bun run src/cli.ts` directly via the shebang on
  * src/cli.ts — only the published npm `bin` routes through here.)
  */
-import { spawnSync } from "node:child_process";
+import { spawn, spawnSync } from "node:child_process";
 import { createRequire } from "node:module";
 import { existsSync, readFileSync, statSync } from "node:fs";
 import { homedir } from "node:os";
@@ -160,12 +160,44 @@ if (process.argv[2] === "update" && isNodeModulesInstall() && !isBunGlobalInstal
 }
 
 const bun = resolveBun();
-const res = spawnSync(bun, [cliPath, ...process.argv.slice(2)], { stdio: "inherit" });
-if (res.error) {
-  console.error(`opencodex: failed to launch Bun runtime: ${res.error.message}`);
+
+// Run the Bun child asynchronously and FORWARD termination signals to it, then wait
+// for its graceful shutdown before this launcher exits. The previous blocking
+// spawnSync() could not run JS signal handlers and did not forward signals, so a
+// signal delivered only to this launcher (Codex app, IDE terminal, service wrapper,
+// or `kill -INT <launcherPid>`) killed the launcher and ORPHANED the Bun proxy —
+// port left bound, pid/runtime-port files left behind, Codex config not restored.
+const child = spawn(bun, [cliPath, ...process.argv.slice(2)], { stdio: "inherit" });
+
+// Windows has no real POSIX signals (no SIGHUP); forwarding is best-effort there.
+const FORWARDED = process.platform === "win32" ? ["SIGINT", "SIGTERM"] : ["SIGINT", "SIGTERM", "SIGHUP"];
+const handlers = FORWARDED.map(sig => {
+  const handler = () => {
+    try {
+      child.kill(sig);
+    } catch {
+      /* child already exited */
+    }
+  };
+  process.on(sig, handler);
+  return [sig, handler];
+});
+const clearHandlers = () => {
+  for (const [sig, handler] of handlers) process.removeListener(sig, handler);
+};
+
+child.on("error", err => {
+  clearHandlers();
+  console.error(`opencodex: failed to launch Bun runtime: ${err.message}`);
   process.exit(1);
-}
-if (res.signal) {
-  process.kill(process.pid, res.signal);
-}
-process.exit(res.status ?? 1);
+});
+
+child.on("exit", (code, signal) => {
+  clearHandlers();
+  // Mirror the child's terminating signal/exit code so this launcher's status matches.
+  if (signal) {
+    process.kill(process.pid, signal);
+    return;
+  }
+  process.exit(code ?? 1);
+});