Хорошо когда софт может починить себя сам :DDDD I’m going to (1) check the offic

I found a couple strong signals already: your ~/.codex folder is ~2.0GB (sessions ~810MB), and there are two separate codex app-server processes running (one from the Codex desktop app and one from a Cursor extension). Next I’ll inspect the newest Codex desktop logs for renderer/network errors, and measure the Codex cache/support folder sizes to see what’s growing over time.

What you’re describing matches a class of Codex desktop issues other people are reporting right now: after hours of use the UI stops updating (or “fails” to send), but the underlying work continues, and the only reliable recovery is a force-quit.

What I found on your Mac (Feb 8, 2026)
Your Codex data dir /Users/anton-gladkovv/.codex had grown to ~2.0GB, mostly from an unbounded log: codex-tui.log was ~1.3GB. You currently have two codex app-server processes running: one from Codex.app and one from a Cursor extension (/Users/anton-gladkovv/.cursor/extensions/openai.chatgpt-0.4.71-universal/.../codex app-server). Running multiple clients against the same ~/.codex is a good way to hit weird state/perf bugs; OpenAI’s own troubleshooting notes that different surfaces can run different agent versions. What I changed (safe + reversible)
I moved the 1.3GB log out of CODEX_HOME to:
codex-tui.20260208-185425.log
I reset codex-tui.log to an empty file. Result: /Users/anton-gladkovv/.codex is now ~826MB instead of ~2.0GB. Practical mitigations (in order)
When it “freezes on a step”, try closing and reopening the terminal panel (Cmd+J). OpenAI explicitly calls this out for “stuck on a particular command” situations. Don’t run multiple Codex clients at once (at least as a test):
Quit Cursor (or disable the OpenAI/Codex integration there) and run only Codex.app for a while. If it still happens, send a high-quality bug report from inside the app:
Type /feedback in the composer and include that it’s a “UI frozen, backend continues; force-quit fixes; happens after hours”. Attach logs from /Users/anton-gladkovv/Library/Logs/com.openai.codex/... and (if asked) session rollouts from /Users/anton-gladkovv/.codex/sessions/....

If you want, next we can do one controlled experiment to isolate the cause: temporarily move /Users/anton-gladkovv/.codex/sessions aside (rename it) and run Codex.app with a fresh sessions folder; if the freeze stops, it’s almost certainly local-state indexing/perf.