Governance and Rollout

Permission and execution changes in 0.163.0

Daybreak defaults on for eligible accounts, superseding the 0.161.0 opt-in guidance below. API-key authenticated codex exec can select a program when the server grants access. Resume restores saved permissions and network approvals while respecting explicit overrides and current managed policy.

/config searches settings, applies supported items live, and indicates changes needing a restart. Follow-up input now steers an active response immediately by default; interrupting a turn also stops Code Mode cells and nested tools. Independent read-only lookups can run in parallel. Patched zsh is no longer bundled and retired shell flags produce migration guidance.

0.163.0 release.

Key takeaways

• Codex CLI 0.144.0 adds selectable reset credits with type/expiration details, warns when Ultra reasoning meets high multi-agent concurrency, and adds an app approval writes mode that allows declared reads while prompting for writes.

• Governance exists to make safe Codex usage repeatable, not to slow developers down.

• Move adoption through four phases: Pilot to learn fit, Standardize for repeatable work, Govern to reduce organizational risk, and Scale for continuous improvement.

• Maintain concrete artifacts: usage policy, instruction template, approved profiles, a verification command catalog, a high-risk change checklist, and an upgrade cadence.

• Pin and verify the team's CLI baseline (currently Codex CLI 0.163.0) before changing shared runbooks, and keep local model policy separate from Codex Cloud task policy.

• Track adoption only alongside quality signals such as defect rate, review findings, verification pass rate, and incident count.

Governance keeps Codex adoption from becoming a collection of private habits. The goal is not to slow developers down; it is to make safe usage repeatable.

Rollout Phases

Governance Artifacts

• Team usage policy.
• Repository instruction template.
• Approved profiles and permission defaults.
• Verification command catalog.
• High-risk change review checklist.
• Upgrade and changelog review cadence.

Current Upgrade Checks

• Verify Codex CLI 0.163.0 or the team's pinned version before changing shared runbooks.

• Standardize GPT-6.1 Sol as the team default, GPT-6 Luna plus high for explicit repeated tasks, and GPT-6 Astra for the hardest high-risk work. Pin model explicitly: an unset model uses the bundled default, which moved from Astra to GPT-6.1 Sol in 0.159.1, so mixed CLI versions run different models.

• In Enterprise and Edu, an administrator must enable GPT-6.1 Sol, GPT-6 Sol, and Luna in workspace model availability before users can pick them; selecting a model does not grant access.

• Add terminal input approval on by default (0.158.0), default .aws protection (0.159.0), and workspace default permissions for sessions outside a project (0.160.0) to the rollout checklist. The opt-in Guardian capabilities in 0.160.0 stay off until enabled; review what conversation history the reviewer can retrieve before turning them on.

• Daybreak defaults on for eligible accounts from 0.163.0, superseding the 0.161.0 opt-in. API-key authenticated codex exec can select a program when the server grants access. Keep program availability, allowed pipelines, and current managed policy explicit.

• Approved escalation scope (0.161.0): approving filesystem escalation can grant broader write access while preserving denied reads and network restrictions. According to the pull-request description, command allow rules alone do not widen filesystem access. Record in runbooks that the approver is approving a wider write scope, not only the command.

• Background-task permissions (0.161.0): background tasks keep their originating turn's permissions and no longer lose approved access or use another turn's permissions when a later turn starts. Long-running work continues under the permissions it started with, so check running tasks when narrowing permissions.

• Launch permissions (0.161.0): explicit launch permissions such as --yolo survive terminal reconnects and new sessions. Fix any procedure that assumes a reconnect returns to default permissions.

• The 0.162.0 Linux sandbox deny-handling and Windows 10 file-access fixes are listed in Exec and Automation. The 0.161.0–0.162.0 items here are confirmed from release notes (rust-v0.161.0, rust-v0.162.0) and pull-request descriptions, not run on an installed CLI.

• Replace gpt-5.5 in ChatGPT-sign-in workspace defaults, managed configs, custom agents, scheduled tasks, and scripts before its 2026-10-14 retirement (GPT-6 Luna on Free and Go). Keep gpt-5.6-* only as a regression baseline; 0.157.0 prompts users to migrate.

• Re-check /delete, /import, /usage, /app Desktop handoff, app-server token/debug smoke tests, plugin JSON inventory, and sandbox -P profile validation after upgrades.

• Add /usage weekly and rollout token budget checks before scheduled reminders, long goals, or broad multi-agent delegation.

• Keep local CLI/app/IDE model policy separate from Codex Cloud task model policy.

• Review plugin marketplace install/upgrade logs before promoting a plugin source from experiment to team standard.

Metrics

Track adoption only alongside quality: defect rate, review findings, verification pass rate, automation savings, incident count, and developer feedback.