Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix macOS 桌面版今天明显卡顿，并伴随 unknown conversation / Not a git repository / MCP cleanup 异常 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19108•Fetched 2026-04-24 06:00:48
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Author
jianzhanggjianzhangg
Participants
github-actions[bot]github-actions[bot]jianzhanggjianzhangg
Timeline (top)
labeled ×4cross-referenced ×2closed ×1commented ×1

Error Message

error [electron-message-handler] Received turn/started for unknown conversation conversationId=... Failed to terminate MCP process group ... No such process (os error 3)

Code Example

warning [electron-message-handler] worker_rpc_response_error errorMessage="Not a git repository" method=stable-metadata workerId=git

---

error [electron-message-handler] Received turn/started for unknown conversation conversationId=...

---

Failed to terminate MCP process group ... No such process (os error 3)

---

unsupported feature enablement `realtime_conversation`
RAW_BUFFERClick to expand / collapse

问题概述

今天 Codex Desktop 在 macOS 上明显变得很卡，整体交互发涩，已经影响正常使用。

这个现象和现有的一些性能 issue 可能有关，但我这边今天抓到的本机信号里，除了“长会话越来越卡”之外，还夹杂了大量 unknown conversation、Not a git repository 和 MCP 进程回收异常，所以单独提一个 issue 方便归档这组症状。

可能相关的已有 issue：

  • #18693
  • #12709
  • #11984

环境

  • Codex Desktop（日志里今天多次出现 Current reported app-server version: 0.122.0-alpha.13）
  • Runtime bundle：26.416.11627
  • macOS：15.7.4

现象

  • 今天整体体感明显比平时卡
  • 桌面端在使用过程中会持续出现性能下降
  • 这不是单个线程偶发慢一下，而是整个 Codex Desktop 在今天这轮使用里都偏卡

期望行为

  • Codex Desktop 在正常日常使用中保持流畅
  • 即使后台有 MCP、线程恢复、工作区扫描等动作，也不应该让前台交互明显发涩

实际行为

  • 桌面端今天整体明显卡顿
  • 日志里反复出现一些可能和卡顿相关的异常/噪音信号

今天抓到的本机信号

  • 今天（2026-04-23）桌面日志目录里一共生成了 29 个 codex-desktop-*.log
  • ~/.codex/logs_2.sqlite 当前大小约 753 MB
  • ~/.codex/logs_2.sqlite 当前共有约 151,652 条日志
  • ~/.codex/state_5.sqlite 当前约 5.4 MB
  • 本地线程数约 391，其中未归档约 370

今天日志里的几组重复信号：

  • Not a git repository：约 6,718 次
  • Received turn/started for unknown conversation：约 159 次
  • unsupported feature enablement 'realtime_conversation'：约 138 次
  • Failed to terminate MCP process group ... No such process：约 8 次

示例日志片段

  1. 反复出现 git worker 相关报错：
warning [electron-message-handler] worker_rpc_response_error errorMessage="Not a git repository" method=stable-metadata workerId=git
  1. 今天也持续出现 unknown conversation：
error [electron-message-handler] Received turn/started for unknown conversation conversationId=...
  1. MCP 进程清理也出现过异常：
Failed to terminate MCP process group ... No such process (os error 3)
  1. 还反复出现 feature enablement 同步失败：
unsupported feature enablement `realtime_conversation`

额外说明

  • 这次反馈的核心不是单条错误日志本身，而是“今天整体明显卡”与这些后台异常信号同时出现
  • 如果维护者需要，我可以再补更精确的时间段、更多原始日志片段，或进一步做一次最小复现

extent analysis

TL;DR

The most likely fix is to investigate and address the root cause of the repeated errors and warnings in the logs, such as "Not a git repository", "unknown conversation", and MCP process termination failures.

Guidance

  • Review the logs to identify the patterns and frequencies of the errors and warnings, and prioritize the most critical ones to investigate first.
  • Check the git repository configuration and permissions to resolve the "Not a git repository" errors.
  • Investigate the cause of the "unknown conversation" errors and ensure that conversation IDs are properly handled and validated.
  • Verify the MCP process termination logic to prevent "No such process" errors.

Example

No specific code snippet can be provided without more context, but the error messages suggest that the issues may be related to the electron-message-handler and git worker implementations.

Notes

The issue seems to be related to a combination of factors, including git repository issues, conversation ID handling, and MCP process management. It is essential to investigate each of these areas to identify the root cause of the problem.

Recommendation

Apply a workaround by temporarily disabling or reconfiguring the git worker and MCP processes to see if it improves the performance and reduces the errors. This can help to isolate the root cause and provide more information for further debugging.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#dependency error#configuration error#environment variable#network issue#logging issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING