$ the-wire · showcase
Codex cleans helper dirs, opencode stops listing Azure at startup
By RepoJournal · Filed · About Agentic Coding · Composed from the cited sources · methodology
Today's operator-relevant work is small but real: Codex fixes cross-platform helper cleanup, opencode's Azure plugin stops hitting your account on every launch, and Claude Code plugins get a new home.
Isolate arg0 helper directories by operating system (#53412) openai/codex
Codex now creates its arg0 helpers under CODEX_HOME/tmp/arg0-<os> and limits stale-directory cleanup to that OS's root. If you run Codex on Windows and WSL against a shared CODEX_HOME, one platform's cleanup could previously delete the other's live helpers.
fix(core): stop listing Azure resources at startup anomalyco/opencode
An opencode background job added at plugin startup listed Azure resources on every launch, running az account get-access-token for the management scope and querying Resource Graph even when no Azure connection existed. That check is gone, so startup no longer touches your Azure account unless you use it.
Allow turns when the agent message board is unavailable (#53369) openai/codex
With multi_agent_v2.disable_direct_message enabled, an unavailable agent message board could cause tool router construction to reject the turn outright. Tool router construction no longer requires the board's post tool; unsupported board calls now return an error to the model and the turn continues.
feat(core): load plugins in the hub process and surface plugin errors (#14957) cline/cline
Cline loads plugins in-process through one registry per process instead of a node/bun subprocess, so the compiled CLI and its hub no longer need a runtime on PATH and plugins get the Bun global. The subprocess sandbox is still available via CLINE_PLUGIN_MODE=sandbox.
fix: load and watch symlinked rule files (#14912) cline/cline
Cline now reads rule files through symlinked paths in config directories, so symlinked instructions load instead of being silently skipped. Watching the link targets was dropped deliberately, since each new session re-reads the rules anyway.
fix(cli): keep loading other extensions when one fails the allowlist check google-gemini/gemini-cli
One bad extension no longer takes down the rest: a missing or unreadable .gemini-extension-install.json, or an invalid regex in allowedExtensions, previously rejected the whole loadExtensions Promise.all and left commands like extensions list exiting early. Keep an eye on the arg0 and plugin changes above if your setup spans platforms.