You can now orchestrate Fable 5, Sol, and any model inside Codex with one plugin.
It's called Codex-Orchestration.
Assign Fable 5 as the advisor, Sol as the executor, or any model to any role. Then define the order they work in. Codex handles the routing.
I ran Fable 5 High as planner with GPT-5.6 Sol Extra High as executor on a set of issues Opus and GPT-5.5 always struggled with. Done in 30 minutes. 40% fewer limit hits. 2x faster implementation.
Install it by pasting this into Codex:
"Install Codex Orchestration:
codex plugin marketplace add Cjbuilds/Codex-Orchestration codex plugin add
codex-orchestration@codex-orchestration
Verify the installation, then tell me to start a new task."
Then assign your models:
@ codex-orchestration advisor:
Claude Fable 5 High, Executor: GPT-5.6 Sol High
Open source. Tweak the routing however you want.
You don’t have to be a domain expert to drive great efficiency in that domain.
You just need to be an expert at understanding pain points, identifying optimal implementation, executing, and repeat.
Agentic AI adoption is on fire at @Uber, and it's changing the way we build, not just in engineering, but across the entire company.
Today, 99% of our engineers use AI tools. More than 70% of pull requests are attributed to local or cloud agents. And our engineers have built 2,500+ agent skills across the software development lifecycle.
Those numbers are exciting, but they led us to a much bigger question:
How do we bring agentic AI beyond engineering?
Finance. Legal. Operations. Marketing. Customer Support. HR. Procurement.
These functions run on complex workflows that are often manual, highly nuanced, and spread across dozens of systems. You can't automate them effectively by looking at process diagrams or documentation. You have to understand how the work actually gets done.
So we created something called Agentic Pods.
The idea is simple.
We handpicked ~30 of our most AI-proficient engineers (people with deep knowledge of Uber's systems) and paired each of them with a domain expert from a business function.
Then we gave every pod just two weeks.
• Days 1 – 2: Shadow the expert. Observe every step. Document workflows. Ask questions. Build intuition.
• Day 3: Prioritize opportunities based on scale, repetition, business impact, and data availability.
• Days 4 – 5: Build a working agent alongside the person doing the job.
• Days 6 – 9: Validate with several others performing the same work. Does it generalize? Does it actually make their job better?
• Day 10: Ship.
In just the past two months, we've run 16 Agentic Pods across 16 different business functions.
• Capital allocation across 150 cities: 15 hours → 30 minutes.
• Financial pacing reports: 2 days → 10 minutes.
• Marketing web quality assurance: 2 weeks → 50 minutes.
• Support workflow creation: 9,000 manual workflows → self-service automation.
The productivity gains are impressive, but what surprised us most wasn't the speed.
• It was how quickly engineers embedded in unfamiliar domains uncovered opportunities that had been hiding in plain sight.
• The biggest wins rarely come from automating one task. They come from rethinking an entire workflow. Once you redesign the workflow around AI, you often eliminate handoffs, remove unnecessary approvals, replace legacy tooling, reduce vendor spend, and dramatically accelerate decision-making.
• The workflow becomes the unit of automation - not the individual task.
• The most impactful agent skills cut across teams, orgs, functions, tools, and systems.
The biggest lesson? The best AI opportunities are rarely visible from the outside.
You discover them by sitting next to the people doing the work, understanding every friction point, and building with them, not for them.
We're now forming a dedicated team to scale this further and go deeper. They'll deeply understand the work, redesign it from the ground up, and use AI to fundamentally change how the business operates.
It's exciting times!
You can now vibe code a language model.
From a single prompt, GPT‑5.6 built the entire training pipeline and trained a model from scratch on my iMessage history. Locally on my Mac.
It now generates replies in my writing style.
You have no experience.
You’ve never started a company.
You’ve never had a full time job.
Nike is going to kill you.
You’re a kid.
You don’t have technical skills.
You shouldn’t build hardware.
Apple is going to kill you.
You can’t build hardware.
You can’t measure heart rate non-invasively.
Athletes don’t care about recovery.
Under Armour is going to kill you.
It won’t be accurate.
You don’t listen.
You’re an ineffective leader.
You can’t recruit great talent.
You’re going to have to pay every athlete.
You can’t measure sleep non-invasively.
It’s too expensive to research.
Athletes are a small market.
The product costs too much to make.
The product costs too much to sell.
Your valuation is too high.
Consumers aren’t going to want it.
Hardware is too hard.
You should measure steps.
Fitbit is going to kill you.
You can’t build a marketing engine.
You can’t raise enough money.
You need a real CEO.
Google is going to kill you.
You can’t be a subscription.
You can’t build a brand.
You can’t do consumer in Boston.
Your valuation is too high.
You shouldn’t make accessories.
You shouldn’t make apparel.
Lululemon is going to kill you.
You can’t predict Covid.
Stay in your niche.
You are going to run out of money.
You can’t build a health platform.
Amazon is going to kill you.
You can’t measure blood pressure.
You can’t get medical approvals.
The market is too small.
You don’t understand AI.
The market is too competitive.
It won’t work internationally.
The supply chain is too complicated.
You can’t build an AI.
You can’t raise enough money.
It’s too competitive.
Healthcare isn’t going to want it.
…
Just keep going ✌️
@leerob A way to compact the history yourself. There’s often times I want a clean slate token usage wise to boost performance, but don’t want to restate all the context again.
What if API errors returned a link to docs with a proper implementation?
Then Agents could curl the solution and implement a hotfix
Seems like a no brainer for a devtools startup that needs adoption
Snow & frigid cold (down to - 2) is starting on Tue. afternoon, so Burrow in & stay warm. The roads will deteriorate, so drive slow, use snow tires, charge the battery & check fluids. It’ll be cold enough to where the snow won’t melt, unlike the #Chiefs in the second half. #cowx
This is as powerful an argument as I’ve heard about the stakes of this election. Watch it. Share it. And get everyone you know to vote for @JoeBiden. https://t.co/XdZz4dh82T
IMPORTANT: In coming weeks, as #COVID19 numbers stay high (or rise) in many states, @realdonaldtrump may try to blame it on #BlackLivesMatter protests. As an ER doc, I can tell you it’s a stunt designed to evade accountability & should be refuted ASAP. Here are the facts: 1/8
Saturday, we flew over hospitals, medical facilities and major metropolitan areas in Colorado to honor the frontline medical personnel combatting #COVID19.
#AirForceSalutes