<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Permissions on Margrop Blog</title>
		<link>https://blog.margrop.net/en/tag/permissions/</link>
		<description>Recent content in Permissions on Margrop Blog</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Tue, 12 May 2026 18:50:00 +0800</lastBuildDate>
		
			<atom:link href="https://blog.margrop.net/en/tag/permissions/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Codex 0.130 Removed /approvals? The Fix Is to Move Permissions to Startup Flags</title>
				<link>https://blog.margrop.net/en/post/codex-130-approval-flags/</link>
				<pubDate>Tue, 12 May 2026 18:50:00 +0800</pubDate>
				<guid>https://blog.margrop.net/en/post/codex-130-approval-flags/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;The short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;If you upgraded to Codex 0.130.0 and noticed that the old &lt;code&gt;/approvals&lt;/code&gt; habit no longer works, the practical fix is not to downgrade. Move the permission policy to launch time. Use &lt;code&gt;--ask-for-approval&lt;/code&gt; to control when Codex asks, &lt;code&gt;--sandbox&lt;/code&gt; to control what commands can touch, and reserve &lt;code&gt;--dangerously-bypass-approvals-and-sandbox&lt;/code&gt; for environments that are already isolated outside Codex. The long flag can also be written directly as &lt;code&gt;--yolo&lt;/code&gt;, which is easier to remember, easier to type, and more consistent with command habits from tools such as Gemini.&lt;/p&gt;&#xA;&lt;p&gt;In other words, stop treating approval mode as an in-session toggle. Treat it as part of the way you start the agent.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;This article only discusses public Codex CLI flags and generic workflows. It does not include real hostnames, internal addresses, usernames, tokens, private paths, or project names. Commands use placeholders such as &lt;code&gt;&amp;lt;PROJECT&amp;gt;&lt;/code&gt; and &lt;code&gt;&amp;lt;TASK&amp;gt;&lt;/code&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
