trace-to-skill 0.1.97 → 0.1.99

package/docs/CODEX_GITHUB_ISSUE_PAIN_MAP.md

@@ -1,9 +1,9 @@
 # GitHub Issue Pain Map
 
-Generated: 2026-06-01T03:25:54.011Z
+Generated: 2026-06-01T03:51:24.368Z
 
-Issues analyzed: **15**
-Matched issues: **14**
+Issues analyzed: **20**
+Matched issues: **19**
 Unmatched issues: **1**
 
 This report maps GitHub issues onto deterministic `trace-to-skill` failure classes. Fetch a repository directly with `--repo`, or export issues with `gh issue list` / `gh search issues` and pass the JSON file.
@@ -19,9 +19,11 @@ gh issue list --repo openai/codex --state all --limit 100 --json number,title,bo
 
 | Priority | Kind | Severity | Issues | Comments | Reactions | Example |
 | ---: | --- | --- | ---: | ---: | ---: | --- |
+| 3101 | `codex_platform_availability` | high | 3 | 328 | 1368 | [#10410 Codex Desktop App: macOS Intel (x86_64) support](https://github.com/openai/codex/issues/10410) |
 | 1895 | `codex_remote_connection` | high | 1 | 176 | 851 | [#10450 Remote Development in Codex Desktop App](https://github.com/openai/codex/issues/10450) |
 | 1051 | `codex_token_burn` | high | 2 | 918 | 53 | [#14593 Burning tokens very fast](https://github.com/openai/codex/issues/14593) |
-| 460 | `weak_evidence` | medium | 15 | 1985 | 991 | [#14593 Burning tokens very fast](https://github.com/openai/codex/issues/14593) |
+| 827 | `weak_evidence` | medium | 20 | 2514 | 2462 | [#14593 Burning tokens very fast](https://github.com/openai/codex/issues/14593) |
+| 434 | `codex_thinking_hang` | high | 2 | 201 | 103 | [#14048 All models - Codex CLI hangs indefinitely on all prompts, no response generated](https://github.com/openai/codex/issues/14048) |
 | 409 | `codex_auth_verification` | high | 2 | 346 | 18 | [#20161 Phone number verification doesn't work](https://github.com/openai/codex/issues/20161) |
 | 304 | `codex_model_routing_mismatch` | high | 3 | 231 | 18 | [#11189 GPT-5.3-Codex being routed to GPT-5.2](https://github.com/openai/codex/issues/11189) |
 | 257 | `codex_context_visibility` | high | 3 | 168 | 26 | [#23794 Codex Desktop no longer shows visible context/token usage indicator](https://github.com/openai/codex/issues/23794) |
@@ -29,20 +31,31 @@ gh issue list --repo openai/codex --state all --limit 100 --json number,title,bo
 | 137 | `codex_remote_compact` | high | 1 | 90 | 15 | [#14860 Error running remote compact task](https://github.com/openai/codex/issues/14860) |
 | 137 | `context_compaction` | high | 1 | 90 | 15 | [#14860 Error running remote compact task](https://github.com/openai/codex/issues/14860) |
 | 88 | `codex_mcp_discovery_mismatch` | high | 1 | 55 | 8 | [#6465 MCP servers not detected in Codex VS Code extension but working in Codex CLI](https://github.com/openai/codex/issues/6465) |
-| 22 | `codex_usage_bucket_confusion` | high | 1 | 1 | 2 | [#25471 Codex usage popover shows confusing remaining percentages for 5h vs weekly buckets](https://github.com/openai/codex/issues/25471) |
 
 ## Maintainer Roadmap
 
 | Rank | Next artifact | Why now | Command |
 | ---: | --- | --- | --- |
-| 1 | Remote connection fixture and SSH workspace evidence report | 1 issue(s), 176 comment(s), severity high; top signal: codex_remote_connection. | `trace-to-skill codex-report ./runs --output openai-codex-remote-connection.md` |
-| 2 | Usage evidence fixture and support-ready token report | 2 issue(s), 918 comment(s), severity high; top signal: codex_token_burn. | `trace-to-skill usage-evidence ./usage-notes.md --output usage-evidence.md` |
-| 3 | Auth verification fixture and login support report | 2 issue(s), 346 comment(s), severity high; top signal: codex_auth_verification. | `trace-to-skill codex-report ./runs --output openai-codex-auth-issue.md` |
-| 4 | Model-routing fixture and SSE evidence report | 3 issue(s), 231 comment(s), severity high; top signal: codex_model_routing_mismatch. | `trace-to-skill codex-report ./runs --output openai-codex-model-routing.md` |
-| 5 | Context visibility fixture and Desktop UI evidence report | 3 issue(s), 168 comment(s), severity high; top signal: codex_context_visibility. | `trace-to-skill codex-report ./runs --output openai-codex-context-visibility.md` |
+| 1 | Platform availability fixture and support-policy evidence report | 3 issue(s), 328 comment(s), severity high; top signal: codex_platform_availability. | `trace-to-skill codex-report ./runs --output openai-codex-platform-availability.md` |
+| 2 | Remote connection fixture and SSH workspace evidence report | 1 issue(s), 176 comment(s), severity high; top signal: codex_remote_connection. | `trace-to-skill codex-report ./runs --output openai-codex-remote-connection.md` |
+| 3 | Usage evidence fixture and support-ready token report | 2 issue(s), 918 comment(s), severity high; top signal: codex_token_burn. | `trace-to-skill usage-evidence ./usage-notes.md --output usage-evidence.md` |
+| 4 | Codex-ready issue report and failure fixture | 2 issue(s), 201 comment(s), severity high; top signal: codex_thinking_hang. | `trace-to-skill codex-report ./runs --output openai-codex-issue.md` |
+| 5 | Auth verification fixture and login support report | 2 issue(s), 346 comment(s), severity high; top signal: codex_auth_verification. | `trace-to-skill codex-report ./runs --output openai-codex-auth-issue.md` |
 
 ## Suggested Next Actions
 
+### codex_platform_availability
+
+Priority score: 3101. 3 issue(s), 328 comment(s).
+
+Example issues:
+- [#10410 Codex Desktop App: macOS Intel (x86_64) support](https://github.com/openai/codex/issues/10410) (190 comments; labels: enhancement, app)
+- [#11023 Codex desktop app for Linux](https://github.com/openai/codex/issues/11023) (68 comments; labels: enhancement, app)
+- [#4313 Extension for JetBrains IDEs (PyCharm, IntelliJ, etc.)](https://github.com/openai/codex/issues/4313) (70 comments; labels: enhancement)
+
+Evidence rule prompts:
+- When reporting Codex platform availability gaps, capture requested surface (Desktop app, IDE extension, or packaged build), platform and architecture such as macOS Intel x86_64 or Linux distro/window system, install artifact and version, exact launch/install error, screenshot text such as prohibited icon or incompatible architecture, CLI version and whether CLI works on the same machine, alternative surfaces tried, package format requested, ecosystem workflow such as JetBrains/PyCharm/IntelliJ, demand evidence from comments/reactions or signup forms, and whether docs/release notes state the support policy.
+
 ### codex_remote_connection
 
 Priority score: 1895. 1 issue(s), 176 comment(s).
@@ -64,40 +77,27 @@ Example issues:
 Evidence rule prompts:
 - When reporting Codex token burn, capture plan/workspace, client and version, model and reasoning/speed settings, fast-mode/large-context/subagent/review flags, recent /status and usage-dashboard deltas, local token totals including cached input/output/reasoning if available, background process ids and write_stdin poll cadence, compaction attempts and failures, retry/tool-loop counts, whether the app was idle, and a minimal reproduction with before/after usage percentages.
 
-### codex_auth_verification
-
-Priority score: 409. 2 issue(s), 346 comment(s).
-
-Example issues:
-- [#20161 Phone number verification doesn't work](https://github.com/openai/codex/issues/20161) (177 comments; labels: bug, auth)
-- [#1243 "Sign in With ChatGPT" functionality needs to be robust against all account types](https://github.com/openai/codex/issues/1243) (169 comments; labels: none)
-
-Evidence rule prompts:
-- When reporting Codex sign-in or account-verification failures, capture the Codex app/CLI/extension version, surface, OS, account type without secrets, workspace or organization context, SSO provider, whether the flow is ChatGPT sign-in, phone/SMS/OTP verification, or extension chat initialization, exact redacted error text, timestamps, whether another device/browser/account works, logout/login attempts, and screenshots with phone numbers, tokens, and email addresses redacted.
-
-### codex_model_routing_mismatch
+### codex_thinking_hang
 
-Priority score: 304. 3 issue(s), 231 comment(s).
+Priority score: 434. 2 issue(s), 201 comment(s).
 
 Example issues:
-- [#11189 GPT-5.3-Codex being routed to GPT-5.2](https://github.com/openai/codex/issues/11189) (169 comments; labels: bug, CLI)
-- [#11561 GPT-5.3-Codex being routed to GPT-5.2](https://github.com/openai/codex/issues/11561) (47 comments; labels: bug, CLI)
-- [#11842 GPT-5.3-Codex being routed to GPT-5.2](https://github.com/openai/codex/issues/11842) (15 comments; labels: bug, CLI)
+- [#14048 All models - Codex CLI hangs indefinitely on all prompts, no response generated](https://github.com/openai/codex/issues/14048) (131 comments; labels: bug, agent)
+- [#7156 Codex hangs during cli command execution](https://github.com/openai/codex/issues/7156) (70 comments; labels: bug, CLI)
 
 Evidence rule prompts:
-- When reporting Codex model-routing mismatches, capture the Codex app/CLI/extension version, subscription/workspace, selected model from config.toml, TUI, command flag, or UI, actual server-side model from SSE `response.created` / `response.model`, the exact `RUST_LOG` or trace command used, timestamp, account or verification state without secrets, whether API and Codex routes differ, whether a warning/fallback notice appeared, and a minimal one-prompt reproduction with redacted logs.
+- When reporting Codex thinking or CLI no-response hangs, capture app/CLI/extension version, OS/terminal such as WSL, model and reasoning/speed settings, subscription/workspace, turn/thread id, prompt timestamp, whether the prompt is accepted but no streaming output/error/timeout appears, status bar or usage percent such as 100% left, `turn/start` or `task_started` timestamp, last successful tool-call output, first `response_item` or assistant timestamp if it eventually appears, `RUST_LOG`/SSE evidence including unhandled responses events, transport (`responses_http` or websocket), `time.busy`/`time.idle` close metrics, reconnect or stream-disconnect lines, status incident link or cluster mitigation note if relevant, MCP/subagent state, whether stop/Ctrl+C/interrupt works, and whether a new thread, logout/login, downgrade, API billing path, or minimal config without MCPs recovers.
 
-### codex_context_visibility
+### codex_auth_verification
 
-Priority score: 257. 3 issue(s), 168 comment(s).
+Priority score: 409. 2 issue(s), 346 comment(s).
 
 Example issues:
-- [#23794 Codex Desktop no longer shows visible context/token usage indicator](https://github.com/openai/codex/issues/23794) (160 comments; labels: bug, context, app)
-- [#23591 Reimplement visible context/token usage indicator in Codex Desktop App](https://github.com/openai/codex/issues/23591) (7 comments; labels: enhancement, rate-limits, context, app)
-- [#24710 Codex Desktop: hidden context indicator still blocks long-session context management](https://github.com/openai/codex/issues/24710) (1 comments; labels: enhancement, context, app)
+- [#20161 Phone number verification doesn't work](https://github.com/openai/codex/issues/20161) (177 comments; labels: bug, auth)
+- [#1243 "Sign in With ChatGPT" functionality needs to be robust against all account types](https://github.com/openai/codex/issues/1243) (169 comments; labels: none)
 
 Evidence rule prompts:
-- When reporting Codex context-visibility regressions, capture Codex Desktop version, OS, surface, screenshot or short recording of the chat input area, whether the prior context/token indicator or tooltip was visible before the update, exact UI route where it disappeared, local session metadata showing context/window pressure if available, `/status` output if relevant, compaction timing, whether CLI/TUI still exposes a statusline, and how the missing indicator affects long-session decisions.
+- When reporting Codex sign-in or account-verification failures, capture the Codex app/CLI/extension version, surface, OS, account type without secrets, workspace or organization context, SSO provider, whether the flow is ChatGPT sign-in, phone/SMS/OTP verification, or extension chat initialization, exact redacted error text, timestamps, whether another device/browser/account works, logout/login attempts, and screenshots with phone numbers, tokens, and email addresses redacted.
 
 ## Unmatched Issues
 

package/docs/CODEX_ISSUE_MAP.md

@@ -35,7 +35,7 @@ npx trace-to-skill lsp-audit . --format json
 | Undo, rewind, and pre-agent checkpoint needs | users want `/undo` or `/rewind`, double-Esc only rewinds chat state, untracked/gitignored files are not protected by commits, and manual recovery needs reviewable pre-agent evidence | workspace checkpoint bundle | `trace-to-skill checkpoint . --output .trace-to-skill/checkpoints/before-codex` before agent work |
 | Model routing mismatch | selected `gpt-5.3-codex` in `config.toml`, TUI, or `--model`, but SSE `response.created` / `response.model` shows `gpt-5.2`, silent fallback, no warning, no fallback notice | `codex_model_routing_mismatch` | `trace-to-skill codex-report ./runs` or `trace-to-skill demo model-routing-mismatch` |
 | Latency regressions | GPT-5.5 Fast feels like Standard, simple tasks take 10-20+ minutes, pre-first-token or thinking stalls, slow search/read/compaction, hours for small code changes | `codex_latency_regression` | `trace-to-skill codex-report ./runs` |
-| Thinking or stream hangs | accepted turn, completed local tool output, no streamed assistant follow-up, long gap before first `response_item`, `time.busy` milliseconds with `time.idle` hundreds of seconds, Stop/Ctrl+C cannot interrupt, subagent parent stuck | `codex_thinking_hang` | `trace-to-skill codex-report ./runs` or `trace-to-skill demo thinking-hang` |
+| Thinking or stream hangs | accepted turn, completed local tool output, CLI prompt accepted but no streaming output/error/timeout, status bar `100% left`, unhandled responses events, terminal command execution stuck, long gap before first `response_item`, `time.busy` milliseconds with `time.idle` hundreds of seconds, Stop/Ctrl+C cannot interrupt, status incident or cluster-reroute note, subagent parent stuck | `codex_thinking_hang` | `trace-to-skill codex-report ./runs`, `trace-to-skill demo thinking-hang`, or `trace-to-skill demo cli-no-response` |
 | Clipboard, paste, and generated attachment regressions | `Copy as Markdown` missing, Copy menu only exports metadata, long pasted prompts become `Pasted text.txt`, generated attachments cannot preview/edit/revert, `/goal` ignores non-empty fileAttachments | `codex_clipboard_attachment` | `trace-to-skill codex-report ./runs` or `trace-to-skill demo clipboard-attachment` |
 | Deeplink, OAuth callback, and external launch regressions | `codex://oauth_callback?code=...` fails, `Unable to find Electron app`, `app\oauth_callback?code=...`, notification `type=click&tag=...` becomes an app path, AppX/MSIX protocol evidence, `codex app .` only focuses | `codex_deeplink_launch` | `trace-to-skill codex-report ./runs` or `trace-to-skill demo deeplink-launch` |
 | App connector auth cache and stale link regressions | `401 Reauthentication required`, `refresh token was revoked`, stale `link_*`, `isAccessible: false`, `codex_apps_tools` or `codex_app_directory` cache regeneration keeps broken connector state | `codex_connector_auth_cache` | `trace-to-skill codex-report ./runs` or `trace-to-skill demo connector-auth-cache` |
@@ -62,6 +62,7 @@ npx trace-to-skill lsp-audit . --format json
 | Auth and connectivity failures | `token_exchange_failed`, `auth.openai.com/oauth/token`, missing CA certificates, proxy/TLS, IPv6, Cloudflare, stream disconnects | `codex_connectivity` | `trace-to-skill codex-report ./runs` |
 | Sign-in and account verification failures | phone verification, SMS/OTP, SSO, ChatGPT sign-in account routing, organization/workspace verification, extension chat initialization | `codex_auth_verification` | `trace-to-skill codex-report ./runs` or `trace-to-skill demo auth-verification` |
 | Remote connection and SSH workspace failures | Codex Desktop remote development, Settings > Connections hidden, `[features].remote_connections`, SSH hosts from `~/.ssh/config`, remote filesystem source of truth, local tunnel not ready, stale remote Codex version, codex-server/app-server restart, fs/getMetadata folder listing timeouts, ForwardAgent or local API proxy needs | `codex_remote_connection` | `trace-to-skill codex-report ./runs` or `trace-to-skill demo remote-connection` |
+| Platform availability and unsupported surfaces | macOS Intel x86_64, Universal build, prohibited `Codex.app` icon, incompatible architecture, CLI works but Desktop app does not, Linux desktop app requests, Ubuntu/Arch/NixOS/Wayland package demand, JetBrains/PyCharm/IntelliJ extension demand, docs or release-notes support policy requests | `codex_platform_availability` | `trace-to-skill codex-report ./runs` or `trace-to-skill demo platform-availability` |
 | Remote-control routing failures | `Waiting for desktop`, `Directory: Unavailable`, stale listener/enrollment, `127.0.0.1:14567`, empty backend environments | `codex_remote_control` | `trace-to-skill codex-report ./runs` |
 | MCP runtime failures | `user cancelled MCP tool call`, `unsupported call: mcp__...__...`, namespace/serverName loss, `Transport closed` | `codex_mcp_runtime` | `trace-to-skill codex-report ./runs` |
 | Plugin runtime and bundled capability failures | Computer Use native pipe path unavailable, Browser/Computer Use settings fail, plugin/list `unknown variant 'vertical'`, stale plugin cache downgrades | `codex_plugin_runtime` | `trace-to-skill codex-report ./runs` |
@@ -85,7 +86,7 @@ npx trace-to-skill lsp-audit . --format json
 - Include `session-audit` output, largest rollout JSONL sizes, largest line sizes, parse-error counts, `session_index.jsonl` line count, bloated title byte/signal counts, unindexed rollout thread count, recoverable `codex resume <id>` commands, hashed project groups, and state-file presence for resume/session-state failures.
 - Include `diagnostics-bundle` output when the issue spans config plus local session/history state, or when you need one metadata-only folder that excludes raw logs, SQLite databases, raw config, and transcripts.
 - Include pre-first-token, thinking, tool, search, read, and compaction timings plus model/speed settings for latency regressions.
-- Include `turn/start`, `task_started`, last successful tool output, first `response_item` timestamp, `responses_http` or websocket evidence, `time.busy` / `time.idle`, MCP/subagent state, stop/interrupt behavior, and minimal-config recovery evidence for Thinking hangs.
+- Include `turn/start`, `task_started`, last successful tool output, accepted prompt/no output/no error/no timeout, status bar `100% left`, first `response_item` timestamp, `RUST_LOG` SSE evidence, unhandled responses events, `responses_http` or websocket evidence, `time.busy` / `time.idle`, status incident or cluster note, MCP/subagent state, stop/Ctrl+C/interrupt behavior, and minimal-config recovery evidence for Thinking or CLI no-response hangs.
 - Include exact Copy menu items, paste source size, generated attachment name/path/size, visible editor text, `pasted-text-attachments.json` or fileAttachments metadata, `/goal` or submit path, preview/edit/revert actions, and clipboard payload format for clipboard/attachment regressions.
 - Include exact redacted `codex://` URI shape, connector/plugin, browser, error dialog text, app running state, AppX/MSIX protocol registration evidence such as AppUserModelID and DelegateExecute, HKCU/HKCR `codex` keys, command-line arguments, `Start-Process "codex://test"` repro, and repair/reinstall/re-register attempts for deeplink/OAuth launch regressions.
 - Include connector/plugin name and id, installed plugin root, exact Codex Apps tool name, 401/reauth text, `link_*` id before and after reconnect/cache regeneration, `isAccessible` state, redacted `codex_apps_tools`/`codex_app_directory` metadata, ChatGPT app page state, and external MCP workaround result for connector auth-cache regressions.
@@ -93,6 +94,7 @@ npx trace-to-skill lsp-audit . --format json
 - Include Codex Desktop/app/CLI version, MultiAgentV2 state, OS, model, parent thread id, child thread ids, exact `spawn_agent` arguments, `fork_turns`, role/profile, whether `multi_tool_use.parallel` or same-turn parallel spawning was used, redacted child rollout line order, first user/task message, assistant/commentary envelope lines, sibling prompt excerpts, `wait_agent` and `close_agent` results, unexpected child tool calls, and sequential single-child versus parallel-child controls for subagent prompt leakage.
 - Include effective `CODEX_HOME`, config files considered, redacted MCP sections, trust/profile/default-permissions state, `codex mcp list/get`, CLI-versus-Desktop/VS Code comparison, loaded config path/log lines, WSL/remote/SSH state, and restart/reload/new-conversation results for MCP discovery mismatches.
 - Include Codex Desktop version, remote Codex CLI/app-server version, local OS, remote OS/architecture, SSH alias from `~/.ssh/config`, `[features].remote_connections = true`, Settings > Connections visibility, selected host/path, remote workspace path, remote filesystem source-of-truth expectation, tunnel/app-server error, codex-server pid/restart evidence, remote PATH/auth/proxy/API reachability, model-list differences, fs/getMetadata/folder listing errors, ForwardAgent/proxy needs, and reconnect/resume behavior for remote connection reports.
+- Include requested surface, platform/architecture, install artifact, exact launch/install error, screenshot text, CLI version and same-machine CLI comparison, package format, JetBrains IDE/version, comments/reactions or signup-form demand evidence, and docs/release-notes support-policy evidence for platform availability reports.
 - Include Codex version, MCP server name, transport URL without secrets, initialize/tools/list/tools/call results, HTTP status, `Content-Type`, SSE event framing, JSON-RPC message shape, session id before/after restart, auth/OAuth expectations, User-Agent/header requirements, parse/deserialize error, another-client comparison, and reconnect/reinitialize behavior for Streamable HTTP MCP reports.
 - Include app/CLI/extension version, OS, surface, shell/Desktop route, `[features].hooks`, redacted `hooks.json`, hook event type, matcher, handler command/name, expected versus observed fire count, duplicate event ids, deprecation warning text, trust state, live edit/rate-limit/auto-restore timing, Code Mode `exec` versus normal CLI comparison, linked-worktree cwd, Hooks settings UI evidence, and restart/reload/new-session behavior for hooks reports.
 - Include terminal emulator/version, shell, WSL/SSH/tmux/Zellij state, streaming state, exact scroll action, viewport snap behavior, first missing or duplicated line id, raw log/transcript proof, terminal capture, numbered-line harness/control output, terminal dimensions/scrollback settings, and `/resume` or transcript recovery behavior for terminal-output integrity reports.
@@ -121,6 +123,8 @@ npx trace-to-skill lsp-audit . --format json
 - Tool-call integrity and rollback failures: https://github.com/openai/codex/issues/25399, https://github.com/openai/codex/issues/25380, https://github.com/openai/codex/issues/25426, https://github.com/openai/codex/issues/7291
 - Undo, rewind, and pre-agent checkpoint needs: https://github.com/openai/codex/issues/9203, https://github.com/openai/codex/issues/11626
 - Latency regressions: https://github.com/openai/codex/issues/24422, https://github.com/openai/codex/issues/21527, https://github.com/openai/codex/issues/11984, https://github.com/openai/codex/issues/12161
+- CLI no-response and command execution hangs: https://github.com/openai/codex/issues/14048, https://github.com/openai/codex/issues/7156
+- Platform availability and unsupported surfaces: https://github.com/openai/codex/issues/10410, https://github.com/openai/codex/issues/11023, https://github.com/openai/codex/issues/4313
 - Deeplink, OAuth callback, and external launch regressions: https://github.com/openai/codex/issues/25203, https://github.com/openai/codex/issues/25231, https://github.com/openai/codex/issues/25368, https://github.com/openai/codex/issues/25333
 - App connector auth cache and stale link regressions: https://github.com/openai/codex/issues/24675, https://github.com/openai/codex/issues/25443
 - Context fork bloat and prompt-cache lineage loss: https://github.com/openai/codex/issues/25467, https://github.com/openai/codex/issues/24704, https://github.com/openai/codex/issues/24150, https://github.com/openai/codex/issues/13491, https://github.com/openai/codex/issues/24281

package/docs/CODEX_ISSUE_RADAR.md

@@ -1,10 +1,10 @@
 # GitHub Issue Pain Map
 
-Generated: 2026-06-01T03:26:00.188Z
+Generated: 2026-06-01T03:51:25.847Z
 
 Issues analyzed: **46**
-Matched issues: **21**
-Unmatched issues: **25**
+Matched issues: **26**
+Unmatched issues: **20**
 
 This report maps GitHub issues onto deterministic `trace-to-skill` failure classes. Fetch a repository directly with `--repo`, or export issues with `gh issue list` / `gh search issues` and pass the JSON file.
 
@@ -19,6 +19,7 @@ gh issue list --repo openai/codex --state all --limit 100 --json number,title,bo
 
 | Priority | Kind | Severity | Issues | Comments | Reactions | Example |
 | ---: | --- | --- | ---: | ---: | ---: | --- |
+| 3101 | `codex_platform_availability` | high | 3 | 328 | 1368 | [#10410 Codex Desktop App: macOS Intel (x86_64) support](https://github.com/openai/codex/issues/10410) |
 | 2438 | `codex_token_burn` | high | 4 | 1151 | 620 | [#14593 Burning tokens very fast](https://github.com/openai/codex/issues/14593) |
 | 2221 | `weak_evidence` | medium | 46 | 4755 | 7794 | [#14593 Burning tokens very fast](https://github.com/openai/codex/issues/14593) |
 | 1895 | `codex_remote_connection` | high | 1 | 176 | 851 | [#10450 Remote Development in Codex Desktop App](https://github.com/openai/codex/issues/10450) |
@@ -26,24 +27,35 @@ gh issue list --repo openai/codex --state all --limit 100 --json number,title,bo
 | 805 | `codex_auth_verification` | high | 3 | 436 | 166 | [#20161 Phone number verification doesn't work](https://github.com/openai/codex/issues/20161) |
 | 631 | `codex_context_visibility` | high | 1 | 160 | 227 | [#23794 Codex Desktop no longer shows visible context/token usage indicator](https://github.com/openai/codex/issues/23794) |
 | 442 | `codex_tool_call_integrity` | high | 1 | 61 | 182 | [#2998 IDE-integrated diff / approval](https://github.com/openai/codex/issues/2998) |
+| 434 | `codex_thinking_hang` | high | 2 | 201 | 103 | [#14048 All models — Codex CLI hangs indefinitely on all prompts, no response generated](https://github.com/openai/codex/issues/14048) |
 | 376 | `codex_remote_compact` | high | 2 | 147 | 101 | [#14860 Error running remote compact task](https://github.com/openai/codex/issues/14860) |
 | 376 | `context_compaction` | high | 2 | 147 | 101 | [#14860 Error running remote compact task](https://github.com/openai/codex/issues/14860) |
 | 351 | `codex_terminal_output_integrity` | high | 1 | 66 | 134 | [#2558 Codex client output truncated when scrolling in Zellij](https://github.com/openai/codex/issues/2558) |
-| 324 | `codex_model_routing_mismatch` | high | 1 | 169 | 69 | [#11189 GPT-5.3-Codex being routed to GPT-5.2](https://github.com/openai/codex/issues/11189) |
-| 261 | `premature_completion` | high | 1 | 60 | 92 | [#2448 Codex CLI: Plus users hitting usage limits extremely quickly compared to competitors](https://github.com/openai/codex/issues/2448) |
 
 ## Maintainer Roadmap
 
 | Rank | Next artifact | Why now | Command |
 | ---: | --- | --- | --- |
-| 1 | Usage evidence fixture and support-ready token report | 4 issue(s), 1151 comment(s), severity high; top signal: codex_token_burn. | `trace-to-skill usage-evidence ./usage-notes.md --output usage-evidence.md` |
-| 2 | Remote connection fixture and SSH workspace evidence report | 1 issue(s), 176 comment(s), severity high; top signal: codex_remote_connection. | `trace-to-skill codex-report ./runs --output openai-codex-remote-connection.md` |
-| 3 | Privacy/safety guardrail and redacted support bundle | 1 issue(s), 75 comment(s), severity high; top signal: sensitive_file_access. | `trace-to-skill diagnostics-bundle ~/.codex --output codex-diagnostics` |
-| 4 | Auth verification fixture and login support report | 3 issue(s), 436 comment(s), severity high; top signal: codex_auth_verification. | `trace-to-skill codex-report ./runs --output openai-codex-auth-issue.md` |
-| 5 | Context visibility fixture and Desktop UI evidence report | 1 issue(s), 160 comment(s), severity high; top signal: codex_context_visibility. | `trace-to-skill codex-report ./runs --output openai-codex-context-visibility.md` |
+| 1 | Platform availability fixture and support-policy evidence report | 3 issue(s), 328 comment(s), severity high; top signal: codex_platform_availability. | `trace-to-skill codex-report ./runs --output openai-codex-platform-availability.md` |
+| 2 | Usage evidence fixture and support-ready token report | 4 issue(s), 1151 comment(s), severity high; top signal: codex_token_burn. | `trace-to-skill usage-evidence ./usage-notes.md --output usage-evidence.md` |
+| 3 | Remote connection fixture and SSH workspace evidence report | 1 issue(s), 176 comment(s), severity high; top signal: codex_remote_connection. | `trace-to-skill codex-report ./runs --output openai-codex-remote-connection.md` |
+| 4 | Privacy/safety guardrail and redacted support bundle | 1 issue(s), 75 comment(s), severity high; top signal: sensitive_file_access. | `trace-to-skill diagnostics-bundle ~/.codex --output codex-diagnostics` |
+| 5 | Auth verification fixture and login support report | 3 issue(s), 436 comment(s), severity high; top signal: codex_auth_verification. | `trace-to-skill codex-report ./runs --output openai-codex-auth-issue.md` |
 
 ## Suggested Next Actions
 
+### codex_platform_availability
+
+Priority score: 3101. 3 issue(s), 328 comment(s).
+
+Example issues:
+- [#10410 Codex Desktop App: macOS Intel (x86_64) support](https://github.com/openai/codex/issues/10410) (190 comments; labels: enhancement, app)
+- [#4313 Extension for JetBrains IDEs (PyCharm, IntelliJ, etc.)](https://github.com/openai/codex/issues/4313) (70 comments; labels: enhancement)
+- [#11023 Codex desktop app for Linux](https://github.com/openai/codex/issues/11023) (68 comments; labels: enhancement, app)
+
+Evidence rule prompts:
+- When reporting Codex platform availability gaps, capture requested surface (Desktop app, IDE extension, or packaged build), platform and architecture such as macOS Intel x86_64 or Linux distro/window system, install artifact and version, exact launch/install error, screenshot text such as prohibited icon or incompatible architecture, CLI version and whether CLI works on the same machine, alternative surfaces tried, package format requested, ecosystem workflow such as JetBrains/PyCharm/IntelliJ, demand evidence from comments/reactions or signup forms, and whether docs/release notes state the support policy.
+
 ### codex_token_burn
 
 Priority score: 2438. 4 issue(s), 1151 comment(s).
@@ -88,27 +100,17 @@ Example issues:
 Evidence rule prompts:
 - When reporting Codex sign-in or account-verification failures, capture the Codex app/CLI/extension version, surface, OS, account type without secrets, workspace or organization context, SSO provider, whether the flow is ChatGPT sign-in, phone/SMS/OTP verification, or extension chat initialization, exact redacted error text, timestamps, whether another device/browser/account works, logout/login attempts, and screenshots with phone numbers, tokens, and email addresses redacted.
 
-### codex_context_visibility
-
-Priority score: 631. 1 issue(s), 160 comment(s).
-
-Example issues:
-- [#23794 Codex Desktop no longer shows visible context/token usage indicator](https://github.com/openai/codex/issues/23794) (160 comments; labels: bug, context, app)
-
-Evidence rule prompts:
-- When reporting Codex context-visibility regressions, capture Codex Desktop version, OS, surface, screenshot or short recording of the chat input area, whether the prior context/token indicator or tooltip was visible before the update, exact UI route where it disappeared, local session metadata showing context/window pressure if available, `/status` output if relevant, compaction timing, whether CLI/TUI still exposes a statusline, and how the missing indicator affects long-session decisions.
-
 ## Unmatched Issues
 
-- [#10410 Codex Desktop App: macOS Intel (x86_64) support](https://github.com/openai/codex/issues/10410) (190 comments; labels: enhancement, app)
-- [#14048 All models — Codex CLI hangs indefinitely on all prompts, no response generated](https://github.com/openai/codex/issues/14048) (131 comments; labels: bug, agent)
 - [#2604 Subagent Support](https://github.com/openai/codex/issues/2604) (103 comments; labels: enhancement, subagent)
 - [#12564 Allow renaming task/thread titles to improve history navigation](https://github.com/openai/codex/issues/12564) (77 comments; labels: enhancement, extension)
 - [#2860 Unusable on Windows due to permission ask for every shell command](https://github.com/openai/codex/issues/2860) (77 comments; labels: bug, windows-os)
 - [#2109 Event Hooks](https://github.com/openai/codex/issues/2109) (76 comments; labels: enhancement, hooks)
 - [#2796 BUG: VSCode IDE Plugin on SSH Connection: "Failed to load tasks."](https://github.com/openai/codex/issues/2796) (71 comments; labels: bug, extension)
 - [#16231 High CPU usage on macOS after updating Codex in VS Code extension to 26.325.31654](https://github.com/openai/codex/issues/16231) (71 comments; labels: bug, extension, regression, performance)
-- [#7156 Codex hangs during cli command execution](https://github.com/openai/codex/issues/7156) (70 comments; labels: bug, CLI)
-- [#4313 Extension for JetBrains IDEs (PyCharm, IntelliJ, etc.)](https://github.com/openai/codex/issues/4313) (70 comments; labels: enhancement)
 - [#13041 WebSocket upgrade succeeds then server closes with 1008 Policy (falls back to HTTPS)](https://github.com/openai/codex/issues/13041) (70 comments; labels: bug, connectivity)
 - [#11701 Subagent configuration and orchestration](https://github.com/openai/codex/issues/11701) (69 comments; labels: enhancement, subagent)
+- [#6172 Hitting rate limits](https://github.com/openai/codex/issues/6172) (66 comments; labels: bug, codex-web, rate-limits)
+- [#1481 Bug when I send a first message  "stream error:  ..."](https://github.com/openai/codex/issues/1481) (65 comments; labels: bug)
+- [#11325 Manual /compact command in Codex app](https://github.com/openai/codex/issues/11325) (61 comments; labels: enhancement, app)
+- [#2101 Plan Mode](https://github.com/openai/codex/issues/2101) (61 comments; labels: enhancement)

package/docs/DEMO.md

@@ -1,10 +1,10 @@
 # trace-to-skill Demo
 
-Scenario: **Codex remote connection or SSH workspace failure**
+Scenario: **Codex platform availability gap**
 
-Desktop remote SSH workspaces, Settings > Connections, remote app-server, tunnel, or remote filesystem evidence breaks.
+Codex Desktop, Linux app, or JetBrains extension demand is blocked by unsupported architecture, OS, package, or IDE surface.
 
-Fixture: `fixtures/codex-remote-connection.md`
+Fixture: `fixtures/codex-platform-availability.md`
 
 This is a packaged public fixture, so you can try the project without collecting a private trace first.
 
@@ -14,7 +14,7 @@ This is a packaged public fixture, so you can try the project without collecting
 
 Score: **75/100**
 
-Likely failure class: **Codex remote connection or SSH workspace failure (codex_remote_connection, high)**
+Likely failure class: **Codex platform availability or unsupported surface (codex_platform_availability, high)**
 
 Agent workflow needs clearer verification, instruction, or security hardening before broad reuse.
 
@@ -23,25 +23,25 @@ Agent workflow needs clearer verification, instruction, or security hardening be
 ```md
 ### What happened?
 
-trace-to-skill detected Codex remote connection or SSH workspace failure (codex_remote_connection). Remote-first developers need Codex Desktop to open SSH, server, VM, WSL, container, or cloud workspaces as the source of truth, with reliable remote file browsing, command execution, model availability, app-server health, and reconnect behavior.
+trace-to-skill detected Codex platform availability or unsupported surface (codex_platform_availability). Codex adoption is blocked when the CLI works but the official Desktop app, IDE extension, or packaged build is unavailable for a user's platform, architecture, distro, or IDE ecosystem.
 
 ### Detected failure class
 
-- codex_remote_connection: Codex remote connection or SSH workspace failure (high)
+- codex_platform_availability: Codex platform availability or unsupported surface (high)
 
 ### Evidence
 
-#### Codex remote connection or SSH workspace failure
-- fixtures/codex-remote-connection.md:5 - - Remote Development in Codex Desktop App is a high-demand workflow because many users work on SSH hosts, cloud instances, GPU machines, WSL boxes, containers, or remote Linux servers.
-- fixtures/codex-remote-connection.md:7 - - Users expect Settings > Connections to show SSH hosts from `~/.ssh/config` after enabling `[features] remote_connections = true`.
-- fixtures/codex-remote-connection.md:8 - - A common setup mistake is using `remote_control = true` instead of `remote_connections = true`, so the Connections subheading never appears in the Desktop app.
-- fixtures/codex-remote-connection.md:9 - - The local tunnel can fail with "local tunnel not ready" even when the SSH host is reachable.
-- fixtures/codex-remote-connection.md:10 - - Remote folder browsing can fail with `Unable to load folder contents: Timed out waiting for MCP response to fs/getMetadata while listing directories/files`.
-- fixtures/codex-remote-connection.md:12 - - Killing a stale `codex-server` or app-server on the remote host can force the Desktop app to reattach.
+#### Codex platform availability or unsupported surface
+- fixtures/codex-platform-availability.md:3 - Public issue cluster: Codex Desktop App macOS Intel support, Codex desktop app for Linux, and JetBrains IDE extension demand.
+- fixtures/codex-platform-availability.md:7 - - A user requests macOS Intel x86_64 support for the Codex Desktop App or a Universal build with arm64 + x86_64.
+- fixtures/codex-platform-availability.md:8 - - Environment evidence: Intel Mac, `uname -m => x86_64`, macOS 13/14/15, Codex `.dmg`, and `Codex.app`.
+- fixtures/codex-platform-availability.md:9 - - 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.
+- fixtures/codex-platform-availability.md:10 - - 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`.
+- fixtures/codex-platform-availability.md:16 - - 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.
 
 ### Diagnostics to attach
 
-- When reporting Codex remote connection failures, capture Codex Desktop version, remote Codex CLI/app-server version, local OS, remote OS/architecture, SSH target alias from `~/.ssh/config`, whether `[features].remote_connections = true` is set, Settings > Connections visibility, selected host/path, remote workspace path, whether the remote filesystem is the source of truth, exact tunnel/app-server error, codex-server pid and restart result, `ps -ef | rg 'codex app-server|openai.chatgpt.*/codex'` evidence if available, remote PATH/auth/proxy/API reachability, model list differences versus local, fs/getMetadata or folder listing errors, ForwardAgent/proxy requirements, and whether reconnect/resume or a clean host works.
+- When reporting Codex platform availability gaps, capture requested surface (Desktop app, IDE extension, or packaged build), platform and architecture such as macOS Intel x86_64 or Linux distro/window system, install artifact and version, exact launch/install error, screenshot text such as prohibited icon or incompatible architecture, CLI version and whether CLI works on the same machine, alternative surfaces tried, package format requested, ecosystem workflow such as JetBrains/PyCharm/IntelliJ, demand evidence from comments/reactions or signup forms, and whether docs/release notes state the support policy.
 
 ### Privacy
 
@@ -50,25 +50,25 @@ trace-to-skill detected Codex remote connection or SSH workspace failure (codex_
 
 ## Findings
 
-### 1. Codex remote connection or SSH workspace failure
+### 1. Codex platform availability or unsupported surface
 
 Severity: **high**
 
-Remote-first developers need Codex Desktop to open SSH, server, VM, WSL, container, or cloud workspaces as the source of truth, with reliable remote file browsing, command execution, model availability, app-server health, and reconnect behavior.
+Codex adoption is blocked when the CLI works but the official Desktop app, IDE extension, or packaged build is unavailable for a user's platform, architecture, distro, or IDE ecosystem.
 
 Evidence:
-- `fixtures/codex-remote-connection.md:5` - Remote Development in Codex Desktop App is a high-demand workflow because many users work on SSH hosts, cloud instances, GPU machines, WSL boxes, containers, or remote Linux servers.
-- `fixtures/codex-remote-connection.md:7` - Users expect Settings > Connections to show SSH hosts from `~/.ssh/config` after enabling `[features] remote_connections = true`.
-- `fixtures/codex-remote-connection.md:8` - A common setup mistake is using `remote_control = true` instead of `remote_connections = true`, so the Connections subheading never appears in the Desktop app.
-- `fixtures/codex-remote-connection.md:9` - The local tunnel can fail with "local tunnel not ready" even when the SSH host is reachable.
-- `fixtures/codex-remote-connection.md:10` - Remote folder browsing can fail with `Unable to load folder contents: Timed out waiting for MCP response to fs/getMetadata while listing directories/files`.
-- `fixtures/codex-remote-connection.md:12` - Killing a stale `codex-server` or app-server on the remote host can force the Desktop app to reattach.
-- `fixtures/codex-remote-connection.md:13` - Some remote machines cannot directly access the Codex API, so reports need to mention proxy, local-machine request routing, or ForwardAgent SSH remote server requirements.
-- `fixtures/codex-remote-connection.md:22` - Exact local tunnel, app-server, codex-server, fs/getMetadata, folder listing, model list, auth, proxy, or API reachability error.
+- `fixtures/codex-platform-availability.md:3` Public issue cluster: Codex Desktop App macOS Intel support, Codex desktop app for Linux, and JetBrains IDE extension demand.
+- `fixtures/codex-platform-availability.md:7` - A user requests macOS Intel x86_64 support for the Codex Desktop App or a Universal build with arm64 + x86_64.
+- `fixtures/codex-platform-availability.md:8` - Environment evidence: Intel Mac, `uname -m => x86_64`, macOS 13/14/15, Codex `.dmg`, and `Codex.app`.
+- `fixtures/codex-platform-availability.md:9` - 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.
+- `fixtures/codex-platform-availability.md:10` - 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`.
+- `fixtures/codex-platform-availability.md:16` - 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.
+- `fixtures/codex-platform-availability.md:21` ## JetBrains IDE Extension
+- `fixtures/codex-platform-availability.md:23` - Users request an official Codex extension or plugin for JetBrains IDEs such as PyCharm, IntelliJ, WebStorm, CLion, and Rider.
 
 Suggested rule:
 
-> When reporting Codex remote connection failures, capture Codex Desktop version, remote Codex CLI/app-server version, local OS, remote OS/architecture, SSH target alias from `~/.ssh/config`, whether `[features].remote_connections = true` is set, Settings > Connections visibility, selected host/path, remote workspace path, whether the remote filesystem is the source of truth, exact tunnel/app-server error, codex-server pid and restart result, `ps -ef | rg 'codex app-server|openai.chatgpt.*/codex'` evidence if available, remote PATH/auth/proxy/API reachability, model list differences versus local, fs/getMetadata or folder listing errors, ForwardAgent/proxy requirements, and whether reconnect/resume or a clean host works.
+> When reporting Codex platform availability gaps, capture requested surface (Desktop app, IDE extension, or packaged build), platform and architecture such as macOS Intel x86_64 or Linux distro/window system, install artifact and version, exact launch/install error, screenshot text such as prohibited icon or incompatible architecture, CLI version and whether CLI works on the same machine, alternative surfaces tried, package format requested, ecosystem workflow such as JetBrains/PyCharm/IntelliJ, demand evidence from comments/reactions or signup forms, and whether docs/release notes state the support policy.
 
 
 ## Reporter Notes
@@ -89,6 +89,7 @@ Suggested rule:
 - `latency-regression`: Fast mode feels like Standard, with long thinking, search, read, or compaction stalls.
 - `model-routing-mismatch`: Codex shows one selected model while SSE response evidence shows a different server-side model was used.
 - `thinking-hang`: A turn or tool call completes, but the session stays on Thinking or Working with no streamed follow-up.
+- `cli-no-response`: Codex CLI accepts prompts but produces no streaming output, no error, no timeout, or hangs during command execution.
 - `clipboard-attachment`: Copy as Markdown, long-paste conversion, or generated Pasted text.txt attachments break prompt and report workflows.
 - `deeplink-launch`: OAuth callbacks, notification clicks, mobile links, or `codex app <path>` external activation fail to route into Codex.
 - `connector-auth-cache`: App connectors keep stale `link_*` auth or discovery metadata after reauth-required responses.
@@ -100,6 +101,7 @@ Suggested rule:
 - `subagent-lifecycle`: Completed, closed, stale, or interrupted subagents diverge between UI, live registry, persisted state, quota, and parent discoverability.
 - `usage-bucket-confusion`: Usage popovers show 5h and weekly percentages without clear remaining/used, rolling/calendar, or account/workspace scope.
 - `context-visibility`: Desktop context or token usage indicators disappear, leaving long-session compaction pressure invisible.
+- `remote-connection`: Desktop remote SSH workspaces, Settings > Connections, remote app-server, tunnel, or remote filesystem evidence breaks.
 - `token-burn`: Usage drains from background polling, idle activity, compaction loops, retries, or cached-heavy turns.
 - `patch-overwrite`: `apply_patch` accepts `*** Add File` for an existing path, turning a create operation into a silent overwrite.
 - `sensitive-files`: Secrets, local credentials, production env files, or private databases enter agent context.
@@ -115,6 +117,7 @@ trace-to-skill demo subagent-prompt-leakage
 trace-to-skill demo windows-helper-path
 trace-to-skill demo patch-overwrite
 trace-to-skill demo thinking-hang
+trace-to-skill demo cli-no-response
 trace-to-skill demo clipboard-attachment
 trace-to-skill demo deeplink-launch
 trace-to-skill demo connector-auth-cache
@@ -126,6 +129,7 @@ trace-to-skill demo subagent-lifecycle
 trace-to-skill demo usage-bucket-confusion
 trace-to-skill demo context-visibility
 trace-to-skill demo remote-connection
+trace-to-skill demo platform-availability
 trace-to-skill demo file-tree-ui
 trace-to-skill demo usage-reset-drift
 ```

package/docs/FAILURE_TAXONOMY.md

@@ -52,9 +52,9 @@ The fix is to capture app/CLI/extension version, model and speed/reasoning setti
 
 Codex can accept a turn, finish a local tool call, or keep a Responses request open while the UI or CLI remains on Thinking/Working with no streamed assistant follow-up. This is more specific than general latency: the session appears structurally accepted but the next visible assistant event never arrives or arrives after a very long gap.
 
-Common signals include `turn/start`, `task_started`, a successful tool output followed by no next assistant action, a long gap before the first `response_item`, `model_client.stream_responses_api` close lines where `time.busy` is milliseconds but `time.idle` is hundreds of seconds, `responses_http` or websocket reconnects, Stop/Ctrl+C not interrupting the stuck turn, a subagent parent thread waiting while a child remains active, and minimal `config.toml` without MCPs changing the behavior.
+Common signals include `turn/start`, `task_started`, a successful tool output followed by no next assistant action, a CLI prompt accepted with no streaming output, no error, and no timeout, status bar `100% left` with no tokens consumed, `codex exec --sandbox read-only --model ... 'ping'` stopping after `mcp startup: no servers`, `unhandled responses event` SSE lines, terminal command execution hanging, a status incident or unhealthy-cluster reroute note, a long gap before the first `response_item`, `model_client.stream_responses_api` close lines where `time.busy` is milliseconds but `time.idle` is hundreds of seconds, `responses_http` or websocket reconnects, Stop/Ctrl+C not interrupting the stuck turn, a subagent parent thread waiting while a child remains active, and minimal `config.toml` without MCPs changing the behavior.
 
-The fix is to capture Codex version, OS, model and speed/reasoning settings, turn or thread id, prompt timestamp, last successful tool output, first `response_item` timestamp, transport evidence, `time.busy` / `time.idle`, reconnect or stream-close lines, MCP/subagent lifecycle state, stop/interrupt behavior, and whether a new thread or minimal config recovers.
+The fix is to capture Codex app/CLI/extension version, OS/terminal such as WSL, model and speed/reasoning settings, subscription/workspace, turn or thread id, prompt timestamp, whether the prompt is accepted but no output/error/timeout appears, status bar or usage percent, last successful tool output, first `response_item` timestamp, `RUST_LOG`/SSE evidence, transport evidence, `time.busy` / `time.idle`, reconnect or stream-close lines, status incident link or cluster mitigation note, MCP/subagent lifecycle state, stop/Ctrl+C/interrupt behavior, and whether a new thread, logout/login, downgrade, API billing path, or minimal config recovers.
 
 ## Codex Clipboard Attachment
 
@@ -168,6 +168,14 @@ Common signals include `Remote Development in Codex Desktop App`, `Remote SSH`,
 
 The fix is to capture Codex Desktop version, remote Codex CLI/app-server version, local OS, remote OS/architecture, SSH alias from `~/.ssh/config`, whether `[features].remote_connections = true` is set, Settings > Connections visibility, selected host/path, remote workspace path, whether the remote filesystem is the source of truth, exact tunnel/app-server error, codex-server pid and restart result, remote PATH/auth/proxy/API reachability, model list differences versus local, fs/getMetadata or folder listing errors, ForwardAgent/proxy requirements, and whether reconnect/resume or a clean host works.
 
+## Codex Platform Availability
+
+Codex adoption can be blocked before a session starts when the official Desktop app, packaged build, or IDE extension does not exist for the user's platform, architecture, distro, or IDE ecosystem even though another Codex surface such as the CLI works.
+
+Common signals include macOS Intel `x86_64`, `uname -m => x86_64`, `Codex.app` from a `.dmg` showing a prohibited icon, incompatible architecture or can't-run-on-this-Mac messages, requests for an x86_64 or Universal build, CLI working on the same machine, Linux desktop app requests for Ubuntu, Arch, NixOS, Fedora, Debian, Wayland, X11, AppImage, Flatpak, Snap, `.deb`, or `.rpm`, and JetBrains/PyCharm/IntelliJ/WebStorm extension requests.
+
+The fix is to capture the requested surface, platform and architecture, install artifact, exact error and screenshot text, Codex CLI version and whether CLI works on the same machine, package format or marketplace desired, IDE name/version, demand evidence such as comments/reactions or signup forms, and whether docs, release notes, or roadmap state the support policy.
+
 ## Codex Subagent Prompt Leakage
 
 Codex MultiAgentV2 child agents can fail the task boundary even when the parent asks for isolated children. When `spawn_agent` with `fork_turns: "none"` records the delegated task as an assistant/commentary JSON envelope, or a same-turn parallel child sees a sibling prompt, independent review, QA, and security lanes are no longer independent.

package/docs/OPENAI_OSS_BRIEF.md

@@ -3,14 +3,14 @@
 | Field | Value |
 | --- | --- |
 | Repository | https://github.com/grnbtqdbyx-create/trace-to-skill |
-| Package | trace-to-skill@0.1.97 |
+| Package | trace-to-skill@0.1.99 |
 | License | Apache-2.0 |
 | Codex readiness | ready (100/100) |
-| Benchmark | pass, 42 cases |
+| Benchmark | pass, 44 cases |
 
 ## Why This Repository Qualifies
 
-trace-to-skill helps open-source maintainers adopt Codex safely by turning failed coding-agent runs into evidence-backed rules, reusable workflows, CI gates, and a weekly Codex Issue Radar for live GitHub issue demand. It supports real maintenance work: PR review, issue triage, release quality, MCP risk, prompt-injection defense, privacy-preserving trace sharing, and repeat failure reduction. The repository is ready, scores 100/100 on the local Codex readiness doctor, and ships a deterministic benchmark with 42 public fixture cases.
+trace-to-skill helps open-source maintainers adopt Codex safely by turning failed coding-agent runs into evidence-backed rules, reusable workflows, CI gates, and a weekly Codex Issue Radar for live GitHub issue demand. It supports real maintenance work: PR review, issue triage, release quality, MCP risk, prompt-injection defense, privacy-preserving trace sharing, and repeat failure reduction. The repository is ready, scores 100/100 on the local Codex readiness doctor, and ships a deterministic benchmark with 44 public fixture cases.
 
 ### 500-Character Version
 
@@ -27,10 +27,10 @@ API credits would power optional maintainer workflows on top of the local determ
 ## Evidence
 
 - Public repository: https://github.com/grnbtqdbyx-create/trace-to-skill
-- One-command package: npx trace-to-skill@0.1.97
+- One-command package: npx trace-to-skill@0.1.99
 - Open-source license: Apache-2.0
 - Codex readiness doctor: ready, 100/100, 0 failed checks.
-- Public fixture benchmark: pass, 42 cases.
+- Public fixture benchmark: pass, 44 cases.
 - GitHub issue demand mining: issue-map fetches or reads piped GitHub CLI issue JSON, then ranks OpenAI/Codex issues by failure class, comments, reactions, evidence gaps, and Maintainer Roadmap next artifacts.
 - Weekly Codex Issue Radar: init --issue-map-repo owner/name scaffolds a scheduled Action that fetches live GitHub issues and publishes the pain map to the job summary or a stable tracking issue comment.
 - Maintainer control: generated rules are suggestions, evidence is line-linked, and secrets can be redacted before sharing.

package/docs/SCORECARD.md

@@ -9,7 +9,7 @@ Status: **pass**
 | Failed doctor checks | 0 |
 | Critical findings | 0 |
 | Built-in benchmark | pass |
-| Benchmark cases | 42 |
+| Benchmark cases | 44 |
 
 ## Doctor Summary
 
@@ -34,6 +34,7 @@ This benchmark runs the public fixture pack that ships with the repository and p
 | Codex selected model differs from actual routed model | `fixtures/codex-model-routing-mismatch.md` | 75 | 2 | 0 | `codex_model_routing_mismatch`, `weak_evidence` | pass |
 | Codex model and runtime latency regression | `fixtures/codex-latency-regression.md` | 75 | 2 | 0 | `codex_latency_regression`, `weak_evidence` | pass |
 | Codex thinking and stream hang | `fixtures/codex-thinking-hang.md` | 75 | 2 | 0 | `codex_thinking_hang`, `weak_evidence` | pass |
+| Codex CLI no-response and command execution hang | `fixtures/codex-cli-no-response.md` | 75 | 2 | 0 | `codex_thinking_hang`, `weak_evidence` | pass |
 | Codex clipboard, paste, and attachment workflow regression | `fixtures/codex-clipboard-attachment.md` | 75 | 2 | 0 | `codex_clipboard_attachment`, `weak_evidence` | pass |
 | Codex deeplink, OAuth callback, and external launch regression | `fixtures/codex-deeplink-launch.md` | 50 | 4 | 0 | `codex_deeplink_launch`, `codex_remote_control`, `hallucinated_file`, `weak_evidence` | pass |
 | Codex app connector auth cache and stale link regression | `fixtures/codex-connector-auth-cache.md` | 75 | 2 | 0 | `codex_connector_auth_cache`, `weak_evidence` | pass |
@@ -58,6 +59,7 @@ This benchmark runs the public fixture pack that ships with the repository and p
 | Codex usage bucket scope and percentage confusion | `fixtures/codex-usage-bucket-confusion.md` | 59 | 3 | 0 | `codex_token_burn`, `codex_usage_bucket_confusion`, `weak_evidence` | pass |
 | Codex context or token usage indicator missing | `fixtures/codex-context-visibility.md` | 75 | 2 | 0 | `codex_context_visibility`, `weak_evidence` | pass |
 | Codex remote connection or SSH workspace failure | `fixtures/codex-remote-connection.md` | 75 | 2 | 0 | `codex_remote_connection`, `weak_evidence` | pass |
+| Codex platform availability and unsupported surface demand | `fixtures/codex-platform-availability.md` | 75 | 2 | 0 | `codex_platform_availability`, `weak_evidence` | pass |
 | Codex token burn and usage-drain loop | `fixtures/codex-token-burn.md` | 75 | 2 | 0 | `codex_token_burn`, `weak_evidence` | pass |
 | Codex resource leak and runaway process | `fixtures/codex-resource-leak.md` | 75 | 2 | 0 | `codex_resource_leak`, `weak_evidence` | pass |
 | Codex tool-call integrity and rollback failure | `fixtures/codex-tool-call-integrity.md` | 43 | 4 | 0 | `codex_resource_leak`, `codex_subagent_lifecycle`, `codex_tool_call_integrity`, `weak_evidence` | pass |

package/docs/USE_CASES.md

@@ -59,7 +59,7 @@ What it proves:
 Recommended CI surface:
 
 ```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"
@@ -361,6 +361,32 @@ This catches signals such as `Remote Development in Codex Desktop App`, missing
 
 Include Codex Desktop version, remote Codex CLI/app-server version, local OS, remote OS/architecture, selected SSH host/path, whether the remote filesystem is the source of truth, exact tunnel/app-server/folder-listing/model-list/auth/proxy error, process evidence such as `ps -ef | rg 'codex app-server|openai.chatgpt.*/codex'` when available, and whether killing codex-server, reinstalling remote Codex, reconnecting, or trying a clean host changes the result.
 
+## 18.3. Codex Platform Availability Evidence
+
+Use this when Codex demand is blocked by unsupported architecture, OS, package format, or IDE surface, such as macOS Intel Desktop support, Linux Desktop app support, or a JetBrains extension.
+
+```bash
+npx trace-to-skill demo platform-availability
+npx trace-to-skill codex-report ./runs --output openai-codex-platform-availability.md
+```
+
+This catches signals such as `macOS Intel`, `x86_64`, Universal build requests, `Codex.app` showing the prohibited icon, incompatible architecture, CLI working on the same machine while the Desktop app cannot launch, Linux desktop app requests for Ubuntu/Arch/NixOS/Wayland/package formats, and JetBrains/PyCharm/IntelliJ plugin demand.
+
+Include requested surface, platform and architecture, install artifact, exact launch/install error, screenshot text, CLI version and whether CLI works on the same machine, package format, IDE/version, linked issue, comments/reactions, signup form, and whether docs/release notes state whether support is planned.
+
+## 18.4. Codex CLI No-Response Evidence
+
+Use this when Codex CLI accepts prompts but produces no streaming output, no error, no timeout, or hangs during command execution.
+
+```bash
+npx trace-to-skill demo cli-no-response
+npx trace-to-skill codex-report ./runs --output openai-codex-cli-no-response.md
+```
+
+This catches signals such as all-model hangs, `gpt-5.4 high - 100% left`, no tokens consumed, simple prompts like `Hello` or `ping` never producing output, `codex exec --sandbox read-only --model gpt-5.3-codex 'ping'`, `mcp startup: no servers`, unhandled responses events, CLI/VS Code stuck on Thinking or Working, terminal command execution hangs, status incidents, unhealthy cluster reroutes, and Ctrl+C or `/exit` delays.
+
+Include CLI/app/extension version, OS/terminal/WSL, subscription/workspace, model and reasoning/speed settings, prompt timestamp, exact prompt, whether the prompt was accepted but no stream/error/timeout appeared, status bar or usage percent, `RUST_LOG` SSE snippets, transport, first `response_item` or assistant timestamp if it appears later, reconnect or stream-disconnect lines, status incident link, and recovery attempts such as new thread, downgrade, logout/login, API billing path, or minimal config without MCPs.
+
 ## 19. Codex File Tree UI Evidence
 
 Use this when Codex Desktop cannot reveal project files through the native file tree, folder icon, floating file panel, or built-in preview.