Codex 0.88.0, released on January 21, 2026, added its rough equivalent,
request_user_input. Initially, it worked in Plan and Pair Programming modes, but not in the regular coding modes. After Codex simplified
its public modes to Default and Plan, the tool became Plan-only.
Codex 0.106.0, released on February 26, 2026, made the tool available in
Default mode too. But you need to enable an under-development feature flag first.
If, like me, you manage your Homebrew installations with a dotfile-style Brewfile, you might not know that it can manage globally installed npm utilities too.
I ran a side-by-side comparison of Codex using its built-in web search and using Exa through MCP. The difference wasn’t huge, but it was there: Codex’s built-in search returned a result that was about four days stale, while Exa found the latest release details.
I invoked Exa with @Exa for this search. It found the July 29 release.
Codex’s built-in search returned the July 25 release
I first ran into this a day earlier, when Codex greeted me on startup with Warning: Exceeded skills context budget. That sent me down a rabbit hole: why were my skills being loaded into context when most already had disable-model-invocation: true in their frontmatter?
Really annoyed to just find out that Codex doesn’t support the disable-model-invocation field in skills. Instead, it wants a Codex-specific file in the skill to do the same thing.
With Claude Code and Pi, adding disable-model-invocation: true to the SKILL.md frontmatter is all it takes to make a skill manual-only. More importantly, it keeps that skill out of the model’s default context until I invoke it.
The best thing about Obsidian’s “File over App” philosophy is that you don’t need any special support from the app to manage your content.
You can open the vault folder, or even a single file, in an AI agent or an agentic IDE and start editing right away.
In fact, half the time, that is the way I work with my notes in Obsidian while using an AI agent.
However, sometimes, while working on the content, I like to see my markdown rendered within Obsidian with my preferred theme and other visual customizations like dataview and other plugin outputs.
GPT-5.3-Codex is also our first long-term support (LTS) model, in partnership with OpenAI. LTS models are guaranteed to be available for a full 12 months from the model’s launch date, giving enterprises the stability they need for internal security and safety reviews. GPT-5.3-Codex launched on February 5, 2026 and will remain available through February 4, 2027 for Copilot Business and Copilot Enterprise users.
I have seen model deprecation policies before, but LTS support seems like a different framing of it.
When I set the time picker in Grafana to Yesterday, I noticed something curious: both the From and To fields were set to the same
value — now-1d/d. How could the same expression define both the start and end of a time range? Curious, I dug into the documentation and
source code to understand how this works.
the combination of social media, a highly networked and concentrated depositor base, and technology may have fundamentally changed the
speed of bank runs.
It was considered instantaneous in nature, well, compared to how such large-scale withdrawals happened in the past. And the correlation
between social media and the bank run was so strong that an academic paper confirmed it with data:
During the SVB run period, banks with high pre-existing exposure to Twitter lost 4.3 percentage points more stock market value.
ref: Social Media as a Bank Run Catalyst
But with the pervasive access to agentic AI, especially in the financial sector, which has been innovating with automated trading for years,
people are rightly pointing out that the next financial disaster could happen in a fraction of the time it took for SVB to collapse.
I’d been hardcoding width and height attributes in my Hugo templates to prevent layout shift. It worked fine, but it was
tedious — every time I changed an image, I had to look up the new dimensions and update the template by hand.
Today, I had to add a new image to the sidebar, and I felt lazy enough to ask copilot to find the dimensions for me and
insert them into the template. It instead did something unexpected. It used an odd new Hugo function called
imageConfig instead.
Curious, I looked it up. I haven’t kept myself up to date with Hugo’s latest features the last few years. The
embarrassing part is that, as it turns out, this isn’t a new function. It was added in 2017 (!), but I hadn’t heard of
it until now. I had no idea that Hugo could discover image dimensions at build time. Seems I really should read up more
about what all Hugo can do.
I have wasted too many tokens getting AI editors to work well with Terraform code. The authoritative JavaScript-heavy
provider documentation website makes it impossible to provide as a suitable reference to AI editors. Even adding those
links to Cursor doc index doesn’t work. So you get hallucinations and completely wrong code from even the best of the
models.
