noto

[noto @noto_ff]

Found a memory leak in the Codex Computer Use helper on macOS (SkyComputerUseService, https://t.co/g8lnQb7fts.CUAService 26.708.1000366 / https://t.co/w5ZDviwMtv 26.707.41301 / macOS 26.5.2). Agent sessions were launched headlessly via the official Codex plugin for Claude Code - the desktop helper serves their Computer Use calls, and it's the helper that leaks.

After ~6h uptime (~3h of actual automation against one allow-listed app) it reached a 67.5 GB physical footprint and kept growing ~8 GB/h even fully idle, hitting 70 GB with no active session turns. Swap climbed to 27.5/28 GB on a 32 GB machine.

vmmap rules out retained screen frames (IOSurface + CG image < 1 MB total). It's 82.3M small MALLOC_SMALL allocations (~875 B avg), 96% swapped out and never touched again an append-only structure that never prunes. A thread sample shows why it grows while idle: the helper continuously re-walks accessibility trees (AXUIElementCopyActionNames hot in stacks), and it still has 5+ AXNotificationObserver threads registered to a target PID that's been dead for hours - observers are registered per session and never torn down.

Full read-only diag bundle available (vmmap summary, footprint breakdown, 3s thread sample, fd/thread state). Happy to share - the helper writes nothing to the unified log, so external tooling ends there.

@OpenAIDevs @thsottiaux @reach_vb @Dimillian

[noto @noto_ff]

@thsottiaux - Allow the use of 5.5 Pro for planning/reviewing plans
- Make a memory project scoped, not global. Because it grows too fast with unrelated memories to project
- Hooks config in App
- Config whitelist/deny list of bash cmds in App

[noto @noto_ff]

@jetbrains Main issue for me with this is that it does not utilize native Codex harness. It lacks fast mode, installed skills, subagents, codex config.toml is not applied, etc. I would love to use it, but with all the features of Codex

[noto @noto_ff]

@jetbrains Does Air use the same harness as the Codex CLI? I mean the same configuration, system prompt, subagents, etc, so we get the same results as in CLI or the Codex app, but in the Air app? I want to ensure all Codex functionalities are available