Vibeleaderboard
← All Intel
Intel / repo

codex rust-v0.170.0 — 0.170.0

Source
github.com
Author
github-actions[bot]Top Viber
Date

Context

Codex 0.170.0, a release of the open-source command-line version of OpenAI's coding , fixes two ways a running session could lose restrictions that were already in place. The sandbox is the boundary that decides which files the commands Codex runs can read or write and whether they can reach the network. According to the release notes, permission updates and child threads, meaning new threads started from an existing one, were "losing existing sandbox restrictions."

The first fix concerns changing permissions in the middle of a session. Pull request #61134 moves that handling into the step where a session accepts new settings, and it keeps any existing deny-read restrictions, the rules that stop Codex from reading particular paths. Updates written in the older sandbox_policy form are converted into permission profiles, Codex's current format for filesystem and network permissions, using the new working directory. The pull request's tests check that deny-read rules survive both kinds of update and that protection of a repository's Git metadata holds when the working directory changes. The second fix, pull request #60936, changes how the terminal interface translates between older sandbox templates and permission profiles when it creates a thread from an existing one. The translation no longer turns access to specific fixed folders into access to the current directory, and a profile whose restrictions cannot survive the translation is rejected instead of passed on. Its tests cover a child thread inheriting the parent's writable folders, network access setting and exclusions for temporary directories.

Anyone who relies on deny-read rules and changes permissions during a session, or who starts child threads from the terminal interface, has a reason to upgrade. This is not the first fix of its kind: Codex 0.150.0 made managed deny-read rules stay enforced after permission changes. Neither pull request explains why the work was done, which earlier versions were affected, or what a user would have seen when restrictions dropped, and the release notes list both under bug fixes without calling them security issues. The rejection in #60936 also means that when a thread's permissions cannot be carried over exactly, creating it now fails with an error instead of starting with different ones.

Terms in this piece · Glossary
  • AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
  • sandbox — An isolated environment where AI-generated code or agent actions run without being able to touch anything real.
  • MCP — The Model Context Protocol — an open standard that lets any AI assistant plug into any tool or data source without custom integration code.
More from github-actions[bot]
Recommended reads
Comments

Checking sign-in…

Loading comments…