BlockedPath retweetledi
BlockedPath
7.6K posts

BlockedPath
@BlockedPaths
Building personal AI infrastructure. Local LLMs, coding agents, open-source models. Real hardware, real constraints. Learning in public.
Maryland Katılım Nisan 2009
542 Takip Edilen886 Takipçiler

I think I've found a cure. And it's simple, really.
In my setup, Codex Desktop is using MultiAgent V2. I'm not sure whether that's the default for everyone or something in my config.
Sol and Terra are marked as V2-compatible, while Luna, for some reason, is still marked as V1.
So `spawn_agent` simply filters it out.
If your CLI or Desktop App also uses MultiAgent V2 and Luna is missing from `spawn_agent`, you might be running into the same mismatch.
You don't need to switch the whole app back to V1, btw. You can just patch Luna's catalog entry yourself, actually.
1. Copy:
`~/.codex/models_cache.json`
to:
`~/.codex/model-catalogs/desktop-multi-agent.json`
2. In the copied file, find `gpt-5.6-luna` and change:
`"multi_agent_version": "v1"`
to:
`"multi_agent_version": "v2"`
3. Add this at the top level of `~/.codex/config.toml`:
`model_catalog_json = 'C:\Users\YOUR_USERNAME\.codex\model-catalogs\desktop-multi-agent.json'`
Use the absolute path, obviously.
4. Fully restart Codex Desktop.
I've checked the actual child rollout, not just whatever the model claimed in its reply: GPT-5.6 Luna, Max effort, MultiAgent V2, real subagent, non-empty parent thread.
It works in my setup.
One annoying catch, though:
`model_catalog_json` replaces the entire bundled model catalog. It's not an overlay. Which means your copied catalog can become stale after a Codex update.
So don't forget you've changed this.
After every update, try spawning Luna without the override first.
If the mismatch has been fixed, remove the `model_catalog_json` line from `config.toml`, delete the copied JSON and restart Codex.
If it hasn't, rebuild the copy from the fresh `models_cache.json`, change only Luna's V1 → V2 flag and restart again.
Eidzoku@evi77ain
Did I get this right? We have GPT-5.6 Luna. We can select it as the main agent. But spawn_agent literally can't use it for a subagent? The fastest model is unavailable for the exact role where speed matters most. This feels like a bad joke, @OpenAIDevs @thsottiaux @reach_vb 🥹
English

@Daniel_Farinax @WOwenWebb Im really thinking of taking this over codex 100 plan right now.
English

this guy just wired kimi k3 directly into codex.
the model is insanely good, but the app isn’t.
so instead of using the kimi app, he connected his kimi subscription to codex through oauth.
now kimi k3 shows up right inside the model picker alongside sol 5.6.
no api key needed.
no extra subscription either.
just sign in with oauth through kimi code, and it’s ready to use.
simple guides in the video and links below 👇
MIKE@mikenevermiss
English

For a great workflow setup I personally love using @pidotdev , @herdrdev , and matts skills @mattpocockuk . Simple, clean, and effective.

English

Maybe I was a bit harsh and biased with this, as I am only human. There are edge cases where its appropriate to use it, as well Hermes. I just wish the opensource community wasn't so divided at times. I'm hypocritical. @pidotdev will make you learn how to do things
BlockedPath@BlockedPaths
If you’re using omp, stop and take a second to realize it’s pure slop and a terrible harness wrapped in bandaids.
English

OMPbrrrrt v2 - sound on
I added a distinct tone for tool calls
wolfie@wolfie_
initial attempt lmao - turn on sound
English

I made a little add-on that lets omp search X for you. It pulls actual X posts with links, then gives you a straight answer. No API keys, but it needs your existing xAI (Grok) login (can work on X Premium, dont need supergrok)
github.com/bnivanov/omp-x…
Install is one line, instructions are in the README. Once it's in, just ask your agent to search X. It might be slop-y so looking forward for fixes if needed.
Thanks @BlockedPaths for the inspiration and guidance with the pi plugin
@usr_bin_roygbiv @oleksoleksoleks
English

@LexnLin Been having better luck using pi and Claude with 5.6
English

@jturntdev I also noticed this a few days ago. Went from being nice and steady to gone in a blink of an eye
English

Cant just be who’s noticing this but GPT 5.6 sol in general drains your quota extremely fast.
How is it more efficient?
On 20x plan, you now get 1-2 days of usage. If you’re being conservative.
We’ve had alot of resets, this is just to stop everyone complaining.
When they all go, i see the beginning of the end.
They also reset limits 3hrs after we had to use our banked reset, due to expire.

English

@bradshannon @miniii_codes Nice write up and valid points across the board
English

@samsaffron @grok I don’t think so, every harness has it at this point. Just limited, I made this 3 months ago-ish
English

@BlockedPaths But does @grok bless using its oauth dedicated creds in third party apps?
English

pi-xai-oauth v1.3.6 is ready 🚀
- Its better than the native xai auth, which doesnt have native tools.
✅ Account-specific Grok model discovery
✅ Browser + device OAuth
✅ Encrypted reasoning replay
✅ Grok-native coding tools
✅ Image editing + usage tracking
✅ Hardened routing, security & entitlements
✅ Pi 0.80.1–0.80.10 support
pi.dev/packages/pi-xa…
English

@maxedapps It’s a good deal, and 4.6 is about to come out. 4.5 is such an amazing model for its speed and power.
English
















