trace-to-skill 0.1.97 → 0.1.99

package/fixtures/codex-cli-no-response.md

@@ -0,0 +1,46 @@
+# Codex CLI No-Response Hang
+
+Public issue cluster: All models - Codex CLI hangs indefinitely on all prompts, no response generated.
+
+## Symptoms
+
+- Codex CLI accepts prompts and displays them, but no streaming output begins.
+- All models tested, including `gpt-5.4 high`, `gpt-5.3-codex`, and `gpt-5.1-codex-max`, show no response, no error, and no timeout.
+- The status bar remains `gpt-5.4 high - 100% left`; no tokens are being consumed while the prompt is stuck.
+- A `status.openai.com/incidents` status incident note says Codex CLI hanging or no response may come from unhealthy clusters and rerouted traffic.
+- Simple greetings, questions, codebase analysis, and every message hang the same way.
+- In another report, Codex hangs during terminal command execution; basic shell commands get stuck, it does half the job then stuck, and the VS Code client remains on Thinking or Working.
+- `/exit`, Stop, or Ctrl+C does not respond for minutes, so the user has to kill the Codex process.
+
+## Minimal Reproduction
+
+The `codex exec --sandbox read-only --model gpt-5.3-codex 'ping'` run has no output and hangs after MCP startup with `unhandled responses event` SSE lines:
+
+```bash
+RUST_LOG='codex_api::sse::responses=trace' codex exec --sandbox read-only --model gpt-5.3-codex 'ping'
+```
+
+Observed output stops after:
+
+```text
+mcp startup: no servers
+unhandled responses event: response.in_progress
+unhandled responses event: response.content_part.added
+unhandled responses event: response.output_text.done
+unhandled responses event: response.content_part.done
+```
+
+## Status and Recovery Notes
+
+- A collaborator note linked a status incident and said unhealthy clusters were rerouted.
+- Users still reported Codex is down, Reconnecting, stream disconnected before completion, and no response in both CLI and VS Code after the incident note.
+- Downgrading, starting a new thread, logout/login, API billing path, or a minimal config without MCPs should be recorded as separate recovery attempts.
+
+## Evidence Checklist
+
+- CLI/app/extension version and whether it is Terminal, WSL, VS Code, or Desktop.
+- OS, shell, subscription/workspace, selected model, reasoning effort, and speed/service tier.
+- Prompt timestamp, exact prompt, and whether the prompt is accepted but no streaming output, error, or timeout appears.
+- Status bar or usage percent such as `100% left`, first assistant timestamp if it eventually appears, and whether tokens were consumed.
+- `RUST_LOG` SSE snippets, transport (`responses_http` or websocket), first `response_item`, unhandled responses events, reconnect or stream-disconnect lines, and status incident link.
+- Stop, Ctrl+C, `/exit`, forced kill, new thread, downgrade, logout/login, API billing path, and minimal-config recovery results.

package/fixtures/codex-platform-availability.md

@@ -0,0 +1,35 @@
+# Codex Platform Availability Gap
+
+Public issue cluster: Codex Desktop App macOS Intel support, Codex desktop app for Linux, and JetBrains IDE extension demand.
+
+## macOS Intel / Universal Build
+
+- A user requests macOS Intel x86_64 support for the Codex Desktop App or a Universal build with arm64 + x86_64.
+- Environment evidence: Intel Mac, `uname -m => x86_64`, macOS 13/14/15, Codex `.dmg`, and `Codex.app`.
+- When the `.dmg` is mounted, `Codex.app` shows the prohibited symbol and macOS says the app can't run on this Mac because of incompatible architecture.
+- Codex CLI works fine on the same machine, but the desktop app cannot launch: `which codex => /usr/local/bin/codex` and `codex --version => codex-cli 0.58.0`.
+- The request is specifically for the desktop GUI app, not the CLI.
+- If Intel support is not planned, users ask for an explicit statement in docs or release notes so they do not keep troubleshooting.
+
+## Linux Desktop App
+
+- Users ask for an official Codex desktop app on Linux because they want the app experience on Ubuntu, Arch, NixOS, Fedora, Debian, Wayland, and X11 desktops.
+- Comments mention package expectations such as AppImage, Flatpak, Snap, `.deb`, `.rpm`, and distro packages.
+- Some users point to an AUR package or a signup form, but still want an official release and support policy.
+- Evidence should separate tested community packages from official OpenAI releases.
+
+## JetBrains IDE Extension
+
+- Users request an official Codex extension or plugin for JetBrains IDEs such as PyCharm, IntelliJ, WebStorm, CLion, and Rider.
+- Requested capabilities include terminal integration, version control integration, PR title and summary generation, commit message generation, code review, inline suggestions, refactoring, docs, and multi-language project context.
+- The gap is broader than VS Code: teams using JetBrains want Codex in their normal IDE workflow without switching tools or losing context.
+
+## Evidence Checklist
+
+- Requested surface: Desktop app, IDE extension, packaged build, or official plugin.
+- Platform and architecture: macOS Intel x86_64, Apple Silicon arm64, Linux distro, Wayland/X11, or JetBrains IDE name/version.
+- Install artifact: `.dmg`, `Codex.app`, AppImage, Flatpak, Snap, `.deb`, `.rpm`, AUR, marketplace plugin, or extension id.
+- Exact launch/install error and screenshot text: prohibited icon, incompatible architecture, can't run on this Mac, missing package, or marketplace absence.
+- CLI comparison: `which codex`, `codex --version`, whether Codex CLI works on the same machine, and whether only the GUI/IDE surface is blocked.
+- Demand evidence: linked issue, comments, reactions, signup form, repeated `+1` comments, or enterprise/school hardware constraints.
+- Support-policy evidence: docs, release notes, roadmap, or explicit statement that support is planned, not planned, or unknown.

package/fixtures/github-codex-issues-export.json

@@ -156,6 +156,70 @@
     "reactions": { "totalCount": 851 },
     "updatedAt": "2026-05-14T21:25:03Z"
   },
+  {
+    "number": 10410,
+    "title": "Codex Desktop App: macOS Intel (x86_64) support",
+    "body": "Request macOS Intel x86_64 support for the Codex Desktop App or a Universal build. Environment: Intel Mac, uname -m => x86_64, Codex .dmg, Codex.app. The app shows the prohibited symbol and macOS says it can't run on this Mac due to incompatible architecture, suggesting Apple Silicon only. Codex CLI works fine on the same machine with which codex and codex --version, so this is specifically for the desktop GUI app. Users ask for an explicit docs or release notes statement if Intel support is not planned.",
+    "url": "https://github.com/openai/codex/issues/10410",
+    "labels": [
+      { "name": "enhancement" },
+      { "name": "app" }
+    ],
+    "commentsCount": 190,
+    "reactions": { "totalCount": 377 },
+    "updatedAt": "2026-04-22T01:13:54Z"
+  },
+  {
+    "number": 11023,
+    "title": "Codex desktop app for Linux",
+    "body": "Users request an official Codex desktop app for Linux. Comments mention Ubuntu, Arch, NixOS, Wayland, distro packages, AUR package experiments, and a signup form to be notified when Linux or Windows releases. Users want an official app release and support policy instead of relying on community packages.",
+    "url": "https://github.com/openai/codex/issues/11023",
+    "labels": [
+      { "name": "enhancement" },
+      { "name": "app" }
+    ],
+    "commentsCount": 68,
+    "reactions": { "totalCount": 537 },
+    "updatedAt": "2026-05-31T23:27:54Z"
+  },
+  {
+    "number": 4313,
+    "title": "Extension for JetBrains IDEs (PyCharm, IntelliJ, etc.)",
+    "body": "Request an official Codex extension for JetBrains IDEs including PyCharm, IntelliJ, WebStorm, CLion, and Rider. Desired capabilities include Codex terminal integration, version control integration, PR title and summary generation, commit message generation, code review, inline suggestions, refactoring, documentation, and multi-language project support. Users want Codex in their normal IDE workflow with shared context instead of switching to VS Code or a separate terminal.",
+    "url": "https://github.com/openai/codex/issues/4313",
+    "labels": [
+      { "name": "enhancement" }
+    ],
+    "commentsCount": 70,
+    "reactions": { "totalCount": 454 },
+    "updatedAt": "2026-02-27T22:41:04Z"
+  },
+  {
+    "number": 14048,
+    "title": "All models - Codex CLI hangs indefinitely on all prompts, no response generated",
+    "body": "Codex CLI accepts prompts but produces massively delayed response. It hangs indefinitely with no streaming output, no error, no timeout, all prompt types fail, status bar says gpt-5.4 high - 100% left, and no tokens are consumed. RUST_LOG codex exec ping shows unhandled responses event response.in_progress, response.content_part.added, response.output_text.done, response.content_part.done; other runs stop after mcp startup: no servers. Ctrl-C and /exit do not respond for minutes.",
+    "url": "https://github.com/openai/codex/issues/14048",
+    "labels": [
+      { "name": "bug" },
+      { "name": "agent" }
+    ],
+    "commentsCount": 131,
+    "reactions": { "totalCount": 79 },
+    "updatedAt": "2026-03-16T09:23:48Z"
+  },
+  {
+    "number": 7156,
+    "title": "Codex hangs during cli command execution",
+    "body": "Codex hangs during terminal command execution. Users report basic bash CLI commands get stuck, the tool does half the job then stuck, sometimes one response arrives then hangs, and VS Code/Codex says Thinking or Working. Collaborators linked a status incident and unhealthy clusters / service down in some geographies; users report Reconnecting, stream disconnected before completion, and Ctrl-C or exit delays.",
+    "url": "https://github.com/openai/codex/issues/7156",
+    "labels": [
+      { "name": "bug" },
+      { "name": "CLI" }
+    ],
+    "commentsCount": 70,
+    "reactions": { "totalCount": 24 },
+    "updatedAt": "2025-12-04T17:00:05Z"
+  },
   {
     "number": 6465,
     "title": "MCP servers not detected in Codex VS Code extension but working in Codex CLI",

package/llms.txt

@@ -93,6 +93,8 @@ npx trace-to-skill demo subagent-prompt-leakage
 npx trace-to-skill demo usage-bucket-confusion
 npx trace-to-skill demo context-visibility
 npx trace-to-skill demo remote-connection
+npx trace-to-skill demo platform-availability
+npx trace-to-skill demo cli-no-response
 npx trace-to-skill demo mcp-discovery-mismatch
 npx trace-to-skill demo mcp-streamable-http
 npx trace-to-skill demo hooks-runtime
@@ -132,7 +134,7 @@ gh issue list --repo openai/codex --state all --limit 100 --json number,title,bo
 ## GitHub Action
 
 ```yaml
-- uses: grnbtqdbyx-create/trace-to-skill@v0.1.97
+- uses: grnbtqdbyx-create/trace-to-skill@v0.1.99
   with:
     mode: all
     doctor-threshold: "85"
@@ -145,7 +147,7 @@ gh issue list --repo openai/codex --state all --limit 100 --json number,title,bo
 ## Weekly Codex Issue Radar
 
 ```yaml
-- uses: grnbtqdbyx-create/trace-to-skill@v0.1.97
+- uses: grnbtqdbyx-create/trace-to-skill@v0.1.99
   with:
     mode: issue-map
     issue-map-repo: openai/codex

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "trace-to-skill",
-  "version": "0.1.97",
+  "version": "0.1.99",
   "description": "Turn failed AI coding-agent runs into reusable AGENTS.md rules, SKILL.md files, and eval evidence.",
   "type": "module",
   "main": "dist/src/index.js",
@@ -77,6 +77,10 @@
     "codex-latency",
     "codex-thinking-hang",
     "codex-stuck-thinking",
+    "codex-cli-hang",
+    "codex-no-response",
+    "codex-cli-no-response",
+    "codex-status-incident",
     "codex-clipboard",
     "codex-paste",
     "codex-attachments",
@@ -115,6 +119,10 @@
     "token-exchange-failed",
     "codex-remote-control",
     "codex-remote-connection",
+    "codex-platform",
+    "codex-macos-intel",
+    "codex-linux",
+    "codex-jetbrains",
     "codex-ssh",
     "remote-ssh",
     "remote-workspace",

package/schemas/analysis-result.schema.json

@@ -86,6 +86,7 @@
         "codex_connectivity",
         "codex_remote_control",
         "codex_remote_connection",
+        "codex_platform_availability",
         "codex_terminal_output_integrity",
         "codex_subagent_lifecycle",
         "codex_mcp_discovery_mismatch",