<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Openai on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/openai/</link>
    <description>Recent content in Openai on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 24 May 2026 08:10:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/openai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Do Not Waste Your Codex Quota Before the Reset: Meet Codex Reset Radar</title>
      <link>https://blog.margrop.net/en/post/codex-reset-radar-quota-reset-guide/</link>
      <pubDate>Sun, 24 May 2026 08:10:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/codex-reset-radar-quota-reset-guide/</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;Codex resets have recently become more important to watch. Sometimes the reset is part of the normal usage cycle. Sometimes it is a compensation reset after an incident. Sometimes it follows a fix for abnormal limit consumption. For heavy Codex users, the painful part is not that the quota resets. The painful part is discovering that you still had useful weekly quota left, but you did not use it before the reset overwrote the old window.&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;Codex Reset Radar&lt;/code&gt; is a small public dashboard that turns scattered public signals into a practical warning: if a Codex quota reset window is likely or already open, it tells you to use your remaining weekly quota on valuable work before it expires.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;This article discusses only public pages, public status signals, and public references. It does not include private accounts, tokens, internal systems, private network details, or personal usage data. Any discussion of quota, reset windows, and early warnings is a user-side workflow analysis, not an official statement about OpenAI billing, subscription policy, or service guarantees.&lt;/p&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>
    <item>
      <title>OpenAI GPT-5.4 Explained: Positioning, Capabilities, Cost, and Practical Adoption (As of 2026-03-06)</title>
      <link>https://blog.margrop.net/en/post/openai-gpt-5-4-introduction-2026/</link>
      <pubDate>Fri, 06 Mar 2026 08:20:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/openai-gpt-5-4-introduction-2026/</guid>
      <description>&lt;p&gt;On March 5, 2026, OpenAI officially released GPT-5.4. The first question many people asked was simple: is this just another small point release, or is it a real shift in how much productive work the model can finish?&lt;/p&gt;&#xA;&lt;p&gt;If you only look at the version number, 5.4 looks like the next iteration after 5.2 and 5.3. But once you line up the official launch notes, model docs, API capability matrix, and the ChatGPT-side product updates, the core value of GPT-5.4 is not &amp;ldquo;how many more parameters it has.&amp;rdquo; The real change is that it pulls three lines of capability into a much more usable center point:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Reasoning&lt;/li&gt;&#xA;&lt;li&gt;Coding and engineering execution&lt;/li&gt;&#xA;&lt;li&gt;Tool ecosystem coordination, including computer use&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
    </item>
  </channel>
</rss>
