CODEX LANDS ON WINDOWS WITH NATIVE AGENT SANDBOX AND V0.110 PLUGIN UPGRADES
OpenAI's Codex desktop app now runs natively on Windows with a hardened agent sandbox, and the latest v0.110 update brings a plugin system, richer multi-agent f...
OpenAI's Codex desktop app now runs natively on Windows with a hardened agent sandbox, and the latest v0.110 update brings a plugin system, richer multi-agent flows, and service tier controls.
The Windows release delivers a “first Windows-native agent sandbox” with restricted tokens, filesystem ACLs and dedicated sandbox users, plus native PowerShell support, multi‑agent orchestration, centralized code diff review, and broad IDE/editor integration including Visual Studio, Rider/PhpStorm, Git Bash, GitHub Desktop, Cmder, WSL, and Sublime Text (TechRadar, OpenAI community post). For teams standardizing on Windows dev environments, this removes the WSL/VM dependency while keeping strong OS‑level isolation.
Release v0.110.0 adds a plugin system for loading skills, MCP entries, and app connectors (with install endpoints), expands multi‑agent TUI flows (approval prompts, /agent enablement, clearer prompts, role‑labeled handoffs), introduces persisted /fast toggles with app‑server “fast/flex” tiers, improves memories with workspace‑scoped writes and guardrails, and ships a direct Windows installer script; it also fixes Windows state DB paths and stability issues. Early community feedback flags an Automations (Beta) test‑run issue that can hang IN_PROGRESS without output community bug report.
Windows-first engineering orgs can adopt agentic coding with native isolation and broad IDE coverage.
The new plugin system enables internal skills and connectors, making Codex more extensible for enterprise workflows.
-
terminal
Prototype plugins (skills/MCP connectors) against staging repos and service accounts, and validate install/enable flows end to end.
-
terminal
Benchmark fast vs flex tiers and multi-agent approval flows on large repo diffs in PowerShell-driven pipelines.
Legacy codebase integration strategies...
- 01.
Assess the Windows sandbox’s restricted tokens/ACLs against endpoint protection, proxy, and existing Git/CI hooks.
- 02.
Pilot with a subset of Visual Studio/Rider users and verify Codex memories/workspace scoping don’t conflict with current tooling.
Fresh architecture paradigms...
- 01.
Design an agents-first workflow and package domain capabilities as plugins with clear ownership, logging, and audit trails.
- 02.
Standardize PowerShell environments and choose a default fast/flex tier aligned to latency/cost SLOs.