<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Sandbox on Margrop Blog</title>
		<link>https://blog.margrop.net/en/tag/sandbox/</link>
		<description>Recent content in Sandbox on Margrop Blog</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Mon, 01 Jun 2026 22:00:00 +0800</lastBuildDate>
		
			<atom:link href="https://blog.margrop.net/en/tag/sandbox/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>MiniMax M3 Officially Released: Demystifying the MSA Sparse Attention Architecture, Plus a Look Inside the Mavis Sandbox</title>
				<link>https://blog.margrop.net/en/post/minimax-m3-launch-and-sandbox-architecture/</link>
				<pubDate>Mon, 01 Jun 2026 22:00:00 +0800</pubDate>
				<guid>https://blog.margrop.net/en/post/minimax-m3-launch-and-sandbox-architecture/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;On June 1st, MiniMax (Xiyu Technology) officially released its next-generation general-purpose model, MiniMax M3. It simultaneously maxes out three traditionally hard pillars — frontier coding, ultra-long context, and native multimodality — and it is the &lt;strong&gt;only fully open-source model&lt;/strong&gt; in the world to do so. On the same day, I spent a few hours poking around inside Mavis, mapped out the invisible sandbox behind it, and bundled the experience together with my recent usage data and an invite link.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Disclaimer&lt;/strong&gt;: &lt;strong&gt;This article is 100% written and generated by MiniMax-M3&lt;/strong&gt; (including all code blocks, technical diagrams, and structure), without any manual edits or changes.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Update (2026-06-01 22:00)&lt;/strong&gt;: A few hours after this post went live, the team published a follow-up announcement acknowledging that the original Token Plan migration was communicated poorly and that weekly-quota handling for long-time users wasn&amp;rsquo;t done right. They&amp;rsquo;ve laid out compensation, more quota, and a refund channel. I&amp;rsquo;ve added &lt;strong&gt;Section 9 — &amp;ldquo;Token Plan Revamp: Latest Announcement&amp;rdquo;&lt;/strong&gt; at the bottom of this post. If you&amp;rsquo;re on Token Plan, or about to subscribe, read it before you spend another yuan.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<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>
