Michał Czyż retweeted
Day 25/
We are doubling all usage limits for all Pro 100/200/500 tiers and Business Premium, effective today.
We heard your kind feedback and won’t be reducing usage limits for Pro 200, so your Work and Codex usage will stay the same. We’re also going to continue offering extended limits for dots for now, and usage of your dot will still continue to be separate from your default usage.
And we'll of course also keep shipping better models and other efficiency improvements that increase your effective usage over time.
Two weeks into our Spinel AOT pilot and we got to delete ~520 lines of shims 😄
Dir.glob, optparse and timeout now work natively. The compiled CLI still matches CRuby byte for byte in all 19 conformance cases.
nitter.cf/cs3b/status/2104983721…
Thanks @yukihiro_matz ❤️ and contributors
Michał Czyż retweeted
My harness tier based on my own usage. Every single one I have used bar anti-gravity
Tried compiling one of our Ruby CLIs with Spinel.
~33× faster startup
~8.5× less RAM
1.27 MB native binary (no Ruby runtime)
Still experimental, but… pretty fun 👀
🤖 Made with AI
PR with the benchmarks + notes:
github.com/cs3b/ace/pull/350
What’s missing for wider use is mostly on the Spinel side: more stdlib support, better handling of dynamic Ruby, fewer codegen edge cases.
The closer this gets to “just compile it”, the more interesting it gets.
Big thanks to @yukihiro_matz ❤️
Michał Czyż retweeted
oh no - codex $200 subscription's dollar value is being cut in half
in their defense, openai's models are indeed quite efficient. but anthropic has caught up too
and the big cut is only the first order effect
the second order effect is that this will give anthropic enough room to cut their subscription value as well
the third order effect is that the labs have found a way to gradually end the subsidization for consumers subscriptions. just do this a few more times, and we'll see the subscriptions charging the same as API pricing
i predict that in about a year, we'll refer to what we had as the good old days
Hi,
Tomorrow we are re-opening the Pro $200 subscriptions to new subscribers, but together with it we are also changing how we calculate the usage for it. In effect, if you do the math, it will net out at half the dollar in API spend compared to the old Pro $200 plan.
Now that it's said, let me explain why this is happening and why you will still get more work done than if you were on the Pro $200 subscription one month ago.
(a) We didn't want to compromise in other ways and are committing to not reintroducing the 5h limit, so that you can fully use the weekly usage when you want.
(b) On the subscription, we guarantee that over time you always get more work done and with an increasing level of quality. This means that you will continue to get more value per dollar spent as a result of models getting more efficient and us passing down the improvements in the form of API price reductions.
(c) We don't want to put an incentive on ourselves to artificially inflate the API list prices to make it look like you are getting a lot (and workaround it through discounts, etc). Instead we want to continue to both rapidly reduce prices and increase capabilities of models on the API. This week we introduced GPT-6 Sol and GPT-6 Luna at 50% of their previous price. Over time, we see prices go low enough that it makes sense for most to buy usage as needed without there being a significant gap between what you get in a subscription and what you get in the API for a dollar spent.
(d) Tomorrow, we are adding more things to the subscription that won't draw on the usage, I won't reveal what that is yet.
I wanted to be transparent before all the big announcements tomorrow. Lots of new exciting things are coming to the subscriptions that will make it super compelling, but I wanted to make sure to share this change ahead of time so you can all understand it before we shower you with good news.
Codexingly,
Tibo
Michał Czyż retweeted
Prediction time.
@dhh just asked over a thousand attendees at #railsworld how many people still write code by hand on a regular basis. Less than 10 people raised their hand.
Let that sink in.
Next year the question will be how many people are still doing manual PR code reviews or directly looking at code on any regular basis. Result will be similar.
Third time today an agent has cracked me up. I really need to start keeping receipts.
It reads like: “Bro… I made a baby. Here’s what it looks like.” 😂
What’s the funniest thing your agent has said today?
Michał Czyż retweeted
Top Agentic Development Environments for 2026
#1 - Zed
- Open Source
- ACP support - Claude without their god awful harness
- Project tabs
- Performant
- SSH tabs
- Beautiful
#2 - T3Code
- Open Source
- Good, consistent team
- Claude without the god awful harness
- Performant
- Looks Fine
#3 - CMUX
- Ghostty terminal works amazing w all agents
- Nice browser feature altho I don't like webkit
- MORE PANES BRO MORE PANES
- Tabbed projects
#4 - Ghostty
- Bare bones
- Most performant
#5 - Codex App
- Feels nice I use this the most of all the "apps"
- I love automations and plugins
- Needs to be open sourced
What’s your go-to #ADE (Agentic Development Environment) setup?
I'm still dailing in ...
AI Engineering with #DarkFactory one week in and it’s starting to feel real. Not there yet, but its getting better.
Whats your experience with Dark Factory - did you already switch the lights off? 😉
Michał Czyż retweeted
It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow.
Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes.
As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now.
It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.
Michał Czyż retweeted
I’m joining OpenAI Codex to work on the future of agentic development!
At Cursor, I got to see the shift from autocomplete to agents. The next step isn’t a better IDE. It’s an Agent Development Environment (ADE): systems and tools for orchestrating agents, reasoning over their outputs, and making them autonomous enough to reliably complete ambitious work.
After chatting with @embirico and @thsottiaux, it was clear that Codex is the best place to realize this vision. The team has consistently shipped SOTA models for agentic coding (check out gpt-5.3-codex) and I’m pumped for the future that the new Codex App points to.
What I’m most excited about is the broader mission: accelerating the knowledge work economy. All agents are coding agents, and we’re already seeing Codex used across every job function within organizations.
I’m extremely grateful for my time at Cursor, working with the incredible team, and I’m proud of what we built together. I’m excited to take an even bigger swing with Codex.
If you’re curious to get a glimpse of where we are headed, download the Codex App! If you want to work on this mission, please apply or reach out - we are hiring across all functions!
You can just build things.
Codex (app) is the first user interface that actually fits agentic engineering.
The editor isn't treated as the centerpiece; diffs finally have a clear, readable home, and the terminal sits exactly where it should.
Early days, but this is a strong start. Kudos to @openai and the Codex team - @OpenAIDevs
Agentic coding forces better architecture - systems that are easy to verify.
Without a closed verification loop, it’s just vibe coding.
With it, it becomes scalable engineering.
Highly recommend watching the full interview with @steipete
youtube.com/watch?v=8lF7HmQ_…
