Paste an error to match it against the wiki. / 粘贴报错后自动匹配。
Error text / 报错原文
Codex desktop unresponsiveMCP auto-start duplicatesnon-Git workspace warnings
What it means
The desktop app becomes slow or unresponsive during large agent sessions, often with long histories, broad workspaces, or repeated MCP startup.
Most common causes
- Very long resumed threads
- Workspace opened at a broad drive root instead of a Git repo
- MCP servers auto-starting more than once
- Limited RAM during parallel agent work
Fastest fix
- Archive or start a fresh thread for the current task
- Open the specific project folder instead of a whole drive
- Disable unused MCP auto-start entries
- Restart the app after long sessions
Safe fix
- Keep one Git-backed workspace per task
- Limit MCP servers to the project need
- Split large refactors into smaller sessions
- Monitor memory before launching parallel agents
What not to do
- Do not point an agent at a full personal drive
- Do not keep stale MCP servers enabled globally
- Do not force-close during file writes unless the app is stuck
How to confirm the fix
Run the smallest reproducible command first, then retry the agent task only after authentication, quota, and tool discovery are stable.
git status --short --branch
codex mcp list
Get-Process | Where-Object {$_.ProcessName -match "Codex"}Related errors
- code=3221225477 - Codex Windows desktop crashes on launch →
- CreateProcessWithLogonW failed: 5 - Codex Windows sandbox →
- SetNamedSecurityInfoW failed: 5 - Codex WindowsApps ACL sandbox failure →
- MCP auth session does not refresh - Codex OAuth →
- You've hit your session limit / weekly limit - Claude Code →
- Prompt is too long - Claude Code context window →