OpenAI Codex 0.142 Adds Rollout Token Budgets, Multi-Agent Delegation, Indexed Web Search, and a Reorganized Plugin Marketplace

OpenAI Codex 0.142 Adds Rollout Token Budgets, Multi-Agent Delegation, Indexed Web Search, and a Reorganized Plugin Marketplace

lschvn

The OpenAI Codex 0.142 line shipped across the week of June 22 to June 26, 2026: 0.142.0 on June 22, 0.142.1 and 0.142.2 on June 25, and 0.142.3 on June 26. It lands one week after the 0.141 Noise relay and cross-OS exec release, and the contrast between the two is telling. Where 0.141 was a security release whose headline was a default end-to-end encrypted transport between the orchestrator and remote executors, 0.142 is a governance and orchestration release. The question it answers is no longer "is the wire safe" but "can a team run many of these agents and stay in control of cost, delegation, and tool sprawl."

Rollout token budgets: cost control at the agent layer

The most consequential feature is the rollout token budget, implemented across #28746, #28494, #28707, and #29423. A rollout is a single agent run. The budget is a configurable token cap that Codex tracks across threads as the rollout progresses. At a configurable threshold it emits a remaining-budget reminder, and when the budget is exhausted it aborts the turn cleanly instead of letting a runaway task keep sampling. Turn-scoped context contributions (#28911) keep the accounting honest, and the budget window context is wrapped separately (#29494) so the model sees what it has left.

This is the first built-in cost-control primitive at the Codex agent layer. Before 0.142, bounding what a background task or a delegation could spend meant an external wrapper script or a hard model-side limit. Now a team can hand an agent a budget and trust that a stuck loop will stop on its own. For anyone running Codex against paid models, or running it unattended inside a CI or a multi-agent orchestration setup, that is the difference between an agent that is safe to leave running and one that is not.

Two orchestration capabilities build on the new budget. Multi-agent delegation lets a parent thread hand work to a subagent, and 0.142 makes the behavior configurable at both the thread and the turn level as disabled, explicit-request-only, or proactive (#28685, #28792, #29324). The "explicit-request-only" mode is the conservative default a team wants when it is evaluating delegation: the parent has to ask before spawning a child. Proactive mode hands the parent the discretion to delegate when it judges a subagent fits the work. A companion fix (#28375) surfaces terminal subagent errors back to the parent, so a child that crashed no longer reports as an empty successful completion and leaves the parent continuing on a false premise.

The indexed web-search mode (#28489) gives the agent live web access without unrestricted browsing. Codex can run live searches, but direct page retrieval is restricted to server-approved URLs. The model gathers fresh information from the web but cannot follow arbitrary links off the approved set. Codex distinguishes cached and live web-access terminology in the config (#29095), and the mode sits alongside the existing filesystem and network approval scopes rather than replacing them. The shape is deliberate: trust the search aggregation, do not trust the open browser.

MCP tool search by default, and a reorganized plugin marketplace

MCP tooling gets two changes that matter for installs that have grown past a handful of servers. MCP tools now use tool search by default when the provider supports it (#29486). Instead of dumping every tool from every connected MCP server into the model's context up front, Codex searches for the relevant tool on demand. That preserves compatibility with older models and providers that do not advertise tool search, but for a mature install it is the difference between a tool list that fits the context window and one that does not.

The /plugins view reorganizes remote plugins into three sections, OpenAI Curated, Workspace, and Shared with me (#26703), and a turn can now recommend and install a relevant plugin mid-run (#28399, #28400, #27704, #28403). 0.142.2 adds dedicated dark-mode logos for plugins (#29488) and curated featured-plugin rankings from remote catalogs (#29485). The reorganization turns the plugin browser from a flat list into something a team can actually navigate, and the in-turn recommendation closes the loop between "I have a plugin for that" and the agent actually using it.

System proxy, time awareness, and remote-executor reliability

The remaining work is the kind that does not make a headline but decides whether Codex runs on a given network. 0.142.1 adds opt-in Windows system proxy support for authentication, including PAC, WPAD, static proxies, and bypass rules (#26708). 0.142.2 adds the macOS equivalent: authentication clients honor system proxy, PAC, and WPAD when respect_system_proxy is enabled (#26709). 0.142.0 also honors startup custom CA bundles with the managed MITM path (#29014), which matters on corporate networks that intercept TLS. Together these cover the proxy-and-CA matrix that previously broke the auth handshake for a large class of enterprise users.

Codex also gains real time awareness: scheduled UTC time reminders and the ability to query the current time directly, including through client-provided app-server clocks (#28822, #28824, #28835, #29011). The /usage command can now show and redeem earned usage-limit reset credits (#28154, #28793).

The reliability fixes target the remote-executor path that 0.141 made the default. Exec-server processes and stdio MCP sessions now survive transient disconnects, with signed-URL refresh on reconnect and retry-safe stdin writes (#28512, #28374, #28546, #28895). The Linux TUI no longer breaks after a Ctrl+Z suspend and fg resume (#28342). Remote environments now preserve executor-native paths, shells, AGENTS.md discovery, and sandbox behavior across operating systems, which is the payoff from the PathUri layer 0.141 introduced.

Security hardening and what to watch

0.142.2 hardens a few spots worth noting. PowerShell commands containing executable AST regions the safety classifier cannot inspect now require approval (#24092). Remote HTTP(S) image inputs return clear, model-visible validation errors instead of failing silently, while inline data URLs and local images keep working (#29417, #29419). Expired Amazon Bedrock credentials now produce actionable recovery guidance instead of a generic authorization error (#28992). The release also refreshes the bundled OpenSSL to 3.6.3 (#29487) and esbuild to 0.28.1, the latter being the same version that shipped the Deno RCE and Windows path-traversal fixes we covered earlier this month.

Read alongside the 0.141 Noise relay release and the broader move of runtimes into Anthropic's AI coding infrastructure, the 0.142 cycle is the moment Codex stops being a single-agent coding tool and starts being an agent platform you can govern: budgets to bound cost, delegation modes to control who spawns whom, a web-search mode that trades reach for safety, and tool search that scales to a real MCP estate. The full changelog between 0.141 and 0.142.0 is on the compare view, and the 0.143.0 alpha line is already on its twenty-sixth pre-release at time of writing, which is the signal that the cadence is not slowing down.

Frequently Asked Questions

Deno 2.9 Ships 1.98x Faster Cold Start, 2.2-3.1x Less RSS Under Load, Default-On npm Minimum Release Age, No-Downgrade Trust Policy, and Built-In Snapshot Testing

Deno 2.9 (Bartek Iwańczuk, published 2026-06-25 on deno.com/blog/v2.9) is the largest Deno release of the cycle. Cold start drops from 34.2 ms to 17.3 ms (1.98x), peak RSS on the Deno.serve realworld workload drops 2.2x (142 MB → 64 MB) and 3.1x on 1 MiB bodies (197 MB → 63 MB), and Deno.serve throughput climbs 1.27x realworld (56.8k → 72.4k req/s), 1.11x plaintext, and 1.18x on 1 MiB bodies. Supply chain hardening: npm minimum-release-age is enabled by default with a 24h window (PR #35458), and a new opt-in no-downgrade trust policy (PR #34927) refuses to resolve any version whose trust evidence (staged publish, trusted publishing, provenance attestation) is weaker than the strongest evidence on any earlier-published version of the same package. Test runner parity: built-in t.assertSnapshot() (#35139), Deno.test.each (#34938), --shard for CI fan-out (#35057), retry and repeats (#35053), change-aware --changed and --related (#35199), and coverage thresholds (#35056). Lockfile interop: deno install seeds deno.lock from package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock (#34296, #35330, #35346, #35350, #35394), pnpm-workspace.yaml auto-migrates to deno.json / package.json (#34993), and git merge conflict markers in deno.lock auto-resolve (#34726). Plus: deno desktop graduates from experimental (the June 16 PR #33441), deno link / deno unlink / deno list / deno watch subcommands, stable --unsafe-proto (#34738), Web Locks API (#31166), Happy Eyeballs v2 (RFC 8305) (#31726), navigator.userAgentData (#34743), the WebCrypto Modern Algorithms proposal (ML-KEM, ML-DSA, SLH-DSA, ChaCha20-Poly1305, SHA-3 family, KMAC, Argon2) (#34447, #34448, #34914, #35223), Node 26.3.0 compat (#34746, #34747), Node-API v10 (#35270), and CSS module imports under --unstable-raw-imports (#35093). 165+ PRs land in this cycle.

Related articles

More coverage with overlapping topics and tags.

Astro 7.0.0 Stable Ships Vite 8, Makes the Rust Compiler Default, Adds a Background Dev Server for AI Coding Agents, and Promotes Route Caching, Advanced Routing, and Sätteri to First-Class
ai

Astro 7.0.0 Stable Ships Vite 8, Makes the Rust Compiler Default, Adds a Background Dev Server for AI Coding Agents, and Promotes Route Caching, Advanced Routing, and Sätteri to First-Class

Astro 7.0.0, published on 2026-06-22, lands the 7.0 stable branch after ten weeks of beta. The headline changes: a Vite 8 upgrade, the Rust-based Astro compiler as the default (the Go compiler is removed), the Sätteri Markdown pipeline as the default (remark/rehype moves out of the default install), advanced routing promoted from experimental (with src/fetch.ts as the new default entrypoint), route caching promoted from experimental (top-level cache and routeRules, with cacheNetlify() and cacheVercel() providers landing in the same release), a background dev server mode designed for AI coding agents (astro dev --background, .astro/dev.json lockfile, astro dev stop|status|logs), compressHTML: 'jsx' as the new default, the @astrojs/db package removed, and every official integration bumped a major version (vue 7, react 6, svelte 9, preact 6, solid-js 7, vercel 11, netlify 8, node 11). create-astro@5.1.0, shipped in the same release wave, now writes an AGENTS.md file into every new project with a CLAUDE.md symlink pointing at it.
OpenAI Codex 0.141 Adds Noise-Encrypted Remote Executors, Cross-OS `PathUri`, a Plugin Marketplace, and a SQLite WAL-Reset Pin
ai

OpenAI Codex 0.141 Adds Noise-Encrypted Remote Executors, Cross-OS `PathUri`, a Plugin Marketplace, and a SQLite WAL-Reset Pin

Codex 0.141.0 (June 18, 2026) makes Noise IK the default transport between orchestrator and exec-server, ships a PathUri / NativePathString layer that round-trips POSIX, Windows-drive, and UNC paths without leaking the URI encoding, opens a `created-by-me-remote` plugin marketplace, raises the MCP tool timeout to 300 seconds, and pins the bundled SQLite to 3.51.3 to keep the WAL-reset corruption fix in place after dependency refreshes.
Google Cloud's Open Knowledge Format Is a Standard, Not a Product: A Deep Dive Into OKF v0.1
ai

Google Cloud's Open Knowledge Format Is a Standard, Not a Product: A Deep Dive Into OKF v0.1

On June 12, 2026, Google Cloud published the Open Knowledge Format (OKF), an open specification that formalizes the LLM-wiki pattern into a portable, interoperable format: a directory of markdown files with YAML frontmatter, one required field (type), five recommended ones, and zero required tooling. The tweet from Google Cloud Tech on June 16 drove 117,000 views in 24 hours and made the spec the most-discussed knowledge-format launch of the year. This long read walks through the v0.1 spec section by section, the design choices that make it deliberately minimal, what Google is shipping alongside it (an enrichment agent for BigQuery, a static HTML visualizer, three sample bundles, and a native BigQuery Knowledge Catalog integration), and the open question every AI agent builder and data platform team should be tracking over the next six months.

Comments

Log in Log in to join the conversation.

No comments yet. Be the first to share your thoughts.