<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0">
  <channel>
    <description>Rambling Rows</description>
    <image>
      <url>https://rrows.net/uploads/2026/rrows-icon-sq-144px.png</url>
      <title>Rambling Rows</title>
      <link>https://rrows.net/</link>
    </image>
    <title>codex on Rambling Rows</title>
    <link>https://rrows.net/categories/codex/</link>
    
    <language>en</language>
    
    <lastBuildDate>Fri, 10 Jul 2026 11:01:29 +1000</lastBuildDate>
    <item>
      <title>Fuming - ChatGPT just dropped the ball</title>
      <link>https://rrows.net/2026/07/10/fuming-chatgpt-just-dropped-the.html?utm_source=rss&amp;utm_medium=feed&amp;utm_campaign=rrows</link>
      <pubDate>Fri, 10 Jul 2026 11:01:29 +1000</pubDate>
      
      <guid isPermaLink="false">http://rrows.micro.blog/2026/07/10/fuming-chatgpt-just-dropped-the.html</guid>
      <description>&lt;p&gt;OpenAI just broke something that was working fine, in the name of progress. Software developer&amp;rsquo;s first rule, like doctors, should be &amp;ldquo;first do no harm.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m a paying subscriber. I&amp;rsquo;ve been running &lt;strong&gt;Codex&lt;/strong&gt; hard lately - finance modelling work, not so much straight coding - and my estimation of GPT&amp;rsquo;s capabilities had genuinely grown over recent weeks. Good performer. I was impressed. But not any more.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/202171/2026/codex-fail.jpg&#34; width=&#34;600&#34; height=&#34;201&#34; alt=&#34;&#34;&gt;
&lt;p&gt;This morning I heard rumours of GPT 5.6 dropping, so I updated both the ChatGPT desktop and the Codex desktop app. Codex then refused to deliver a working application. After some fossicking, I found the release note:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;On July 9, the Codex app merges into the new ChatGPT desktop app for macOS and Windows. Codex keeps its dedicated coding experience alongside Chat and Work, with inline editing in diffs, pull request review in the side panel, faster Computer Use powered by GPT-5.6, and multi-repository projects.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;What a clumsy, abrupt change. They killed a familiar workflow with no warning, and the replacement isn&amp;rsquo;t even live yet.&lt;/p&gt;
&lt;p&gt;Yes, they&amp;rsquo;ll argue it&amp;rsquo;s a staged global rollout. That argument doesn&amp;rsquo;t hold. It is simply not acceptable for a commercial application to go dark mid-transition and leave users waiting hours - or days - for restoration. &amp;ldquo;We&amp;rsquo;re rolling it out progressively&amp;rdquo; is not a service level.&lt;/p&gt;
&lt;p&gt;And the timing argument is worse. The cutover happened &amp;ldquo;at night&amp;rdquo; - nighttime in the USA. It&amp;rsquo;s primetime here in Australia, and I cannot do the work I had planned this morning. That&amp;rsquo;s not a minor inconvenience; that&amp;rsquo;s a broken service contract.&lt;/p&gt;
&lt;p&gt;If OpenAI expects business users to stake their workflows on their platform, this is appalling. Full stop, no hedging.&lt;/p&gt;
&lt;p&gt;Fortunately I have &lt;strong&gt;Claude&lt;/strong&gt; as a fallback today. And honestly, this whole episode is just accelerating my thinking about building more of my own AI stack - one that doesn&amp;rsquo;t leave me at the mercy of unreliable mega-corps doing surprise surgery on production tools.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s not just me who&amp;rsquo;s appalled and damaged by this cavalier treatment of paying customers.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/202171/2026/codex-fail-on-twitter-x.jpg&#34;&gt;</description>
    </item>
    
  </channel>
</rss>
