dotsfeed
← Updates

Codexv0.163.0

Resuming an old Codex thread? On 0.163.0 it keeps that thread's permissions and approved hosts

Verified· Oct 16, 2026Published Oct 16, 2026

Codex CLI 0.163.0 restores a saved thread's own permissions and network approvals when you resume it, instead of swapping in today's defaults. A read-only thread stays read-only even if your default is now full access. Explicit overrides and managed policy still win.

What changed

The Codex CLI 0.163.0 release, announced by @CodexReleases on X, changes what happens when you come back to a saved thread. Before, a cold resume could quietly pick up whatever permission defaults your config had at that moment. Now Codex restores the permission profile that belonged to the thread itself, along with the network hosts you already approved in it.

The GitHub release notes and the linked pull requests spell out the practical edge: if you started a thread read-only and later changed your default to full access, resuming that thread keeps it read-only. Network approvals carry over too, so a host you approved earlier is reused without another prompt, while a new host still asks first. Permissions you pass explicitly when resuming, and any managed policy from your admin, still take priority over the saved profile.

Who is affected

Anyone using the Codex CLI who resumes saved threads, especially people who switch between read-only and full-access setups across projects, or who work behind the network proxy with per-host approvals. Teams with managed Codex policy keep their restrictions; the saved thread cannot loosen them.

What to do now

  • Update to Codex CLI 0.163.0 or later before resuming long-running threads.
  • If you want a resumed thread to run with different access than it had, pass that permission explicitly when you resume rather than relying on a changed default.
  • Treat a resumed thread's earlier host approvals as still live. Review them if the thread is old or the task has changed.
  • If your org manages Codex policy, expect admin restrictions to keep overriding whatever the thread saved.

What is not confirmed

This is based on the official release notes and merged pull requests; DotsFeed has not run its own resume test. The notes describe the CLI; whether the Codex app and IDE extension behave identically on resume is not stated in the release.

Sources

Sources

Get updates like this every morning

  1. ① Email
  2. ② Card on Stripe
  3. ③ 7 days free

Then $2/month · cancel anytime in one click