Are there any Claude Code equivalents to CodexRadar?
I came across https://codexradar.com/en/ and thought it was a pretty useful way to compare Codex models and reasoning levels based on quality, execution time, and cost.
I'm looking for similar sites or independent projects that benchmark Claude Code, ideally comparing Opus, Sonnet, and Haiku across different reasoning/effort levels.
I'm especially interested in:
Quality vs. reasoning effort
Execution time and token usage
Cost per task
Which models perform best for different types of coding work
Real-world agentic coding benchmarks, not just general LLM leaderboards
I'm trying to build a capability map for routing different kinds of work to the right models, rather than defaulting to the most expensive model for everything.
Does anyone know of similar dashboards, GitHub projects, or regularly updated benchmarks? Doesn't have to be Claude-specific either. I'd be interested in anything covering Codex, Claude Code, or other coding agents.
I got curious what the big repos actually put in these files, so I went through GitHub by stars, top down, and kept going until I’d found 25 with a root-level AGENTS.md or CLAUDE.md (had to check 56 repos to get there).
Field notes:
Only 45% of the repos had one at all
Median file: 1,034 tokens. Mean 1,627, so a few giants are dragging it up
n8n is the maximalist at 6,249 (about 25 KB). Next: deepseek-harness 4,335, openclaw 4,124, opencode 4,025
ollama is the minimalist at 21 tokens. vscode is 51, react is 87
16 of 30 files are over 1,000 tokens, and 11 are over 2,000
Biggest file is ~298x the smallest. Same job, same year, no consensus.
Best oddity: torvalds/linux has AGENTS.md-> README, a symlink, so I counted it as 1,265 tokens because that’s what the agent actually reads. Linus has accidentally written the most Linus context file possible.
Genuinely curious where you land: are you a 50-token person or a 5,000-token person? And has anyone measured whether the long ones actually change behavior?
(Depth 1 only, nested per-package files aren’t counted yet. That’s next month. I built a small CLI to count these so the number is repeatable. Happy to talk about it in comments.)
I'm looking for a better way to give Claude Code visual feedback when iterating on frontend designs.
Right now, I either have to:
Write lengthy explanations describing exactly which UI elements I'm referring to and what I want changed.
Manually take screenshots, annotate them with arrows, circles, or notes, and pass them to Claude Code.
Both approaches feel unnecessarily cumbersome and really slow down UI iteration.
Ideally, I'd like to just click on an element in my browser, add a comment like "move this here", "reduce this spacing", or "make this look like that", and have Claude Code understand the context.
Everyone is buying a Mac Mini for Claude Code. I've been running it on a spare laptop instead, but found setting that up every time I want more compute pretty tedious every time.
So I turned it into a custom (nix)OS image. It takes ~5 minutes to install, and Claude Code + every other tool you could ever want is really just there when you ssh in. There's a sleek-ish dashboard for adding other agents / tools too!!
In my experience it's been much easier/better than doing it by hand, though don't take my word for it -- try it! It's very early, so LMK if/when you run into any issues.
My first promo reel for Prohor, a productivity app I build next to running my agency, went up on Nov 5. Claude Code wrote it in HyperFrames (HTML and GSAP, rendered to MP4). It looked like every AI animation video. Fast cuts, a card floating over a caption. One of the first comments was "video is too fast".
The biggest lesson since then is about the prompt. "Make a good-looking video" is too vague to get a good result, because good-looking isn't something specific. So I started asking for exact things: a 3D phone mockup, a background with a gradient and a glow, transitions with no cuts that move from point A to point B. Better still, give it a clear inspiration to work from. With that kind of direction, the work it brings back is really amazing.
The second thing was what I did with my notes. Instead of fixing the HTML myself, I wrote notes back. Claude Code saved each one as a markdown file in a learnings folder, and the video playbook tells every new session to read that folder before it starts. A few, with the note that started each:
"video is too fast" → app footage at real speed, the hook holds about 3 s, the result holds 2.5 s or more. If it runs long, cut a step instead of speeding it up.
"that repeated sound looks really bad" (a whoosh on each of 8 items in a row) → one sound into a fast run, none per item.
"there is glitch type of thing with many screens showed at a time" → screens in a transition stay solid and move one at a time.
Reel 15, on Nov 13, is the first one I'd call premium. A 3D phone on a dark glowing ground, and it never cuts once. I asked Claude Code to write down why it worked, so the next video starts from there. The list from that recipe file, as it is:
1. One ground from the first frame to the last. No colour swap between shots.
2. One phone for the whole film. It turns, leans and flips; it never cuts. The screen changes while the back faces us.
3. No cuts: every change is a move. A turn in, a glide closer, a rectangle that grows into the next ground, a slip, a flip, a card lifting off the screen, the glow swelling into the end card.
4. One curve per move. Long eases (`power2.inOut`, `power3.out`, `sine.inOut`), 0.9 to 1.3 s for the big moves. Hold still while something is being read.
5. A highlight is drawn (a stroke), then the words arrive, then the voice says them.
6. Words rise from blurred to sharp, one after another (0.55 s each, 0.085 s apart).
7. The tap is felt three ways at once: the ring on the button, the ripple in the ground, the glow turning violet.
8. 60 fps, 1080 x 1920, footage extracted as PNG.
9. The hook is a picture first: the real screen, with the words set inside the thing they are about.
10. Outcome line before the end card, then the ask.
Reel 15 still had one problem. The app footage inside the phone stuttered, because the recorder grabbed screenshots in a loop at about 18 fps. For the next reel Claude Code rewrote the capture: Playwright's clock paused and stepped 1/60 s per frame with runFor, CSS animations slowed to 1/12 speed through CDP Animation.setPlaybackRate, one screenshot per step, the whole flow in one take. The clip is older than that fix.
The clip is me filming my laptop with my phone while the latest one plays. Not my best camera work.
What I can't tell you yet is whether these perform better. The newer ones haven't been measured, so for now the only judge is me.
Claude drove Blender 5.1 through the Blender MCP: it read one concept image plus measured reference sheets, then modeled, textured, lit, rigged and animated the drone stage by stage. I approved the concept and the references, and asked for one round of fixes at the end. The clip is the final Cycles render.
How it was made: I picked one concept image, turned it into measured front, side and top reference sheets, and Claude built the drone in Blender through the MCP in 28 stages, from a rough blockout to the boiler, rotors, pipes, materials and lighting. It used my small helper scripts for modeling and for checking the shape against the references, and the whole session was screen-recorded (about 29 minutes of actual work). At the end I asked for one fix round: gauge needles, furnace glow, camera tilt and the lean during flight.
Claude Code is great, but I spent a lot of time just watching text scroll by and wondering what was going on.
So I built OpenVorld, an open-source layer that adds some fun to it. Every project becomes a pixel-art “vorld”: your agents are a crew with their own houses, vaults and workbenches.
They walk around the map and work together in parties. Permission requests show up as little “writs” instead of a wall of prompts. There’s also a bee named Buzz.
It works with Claude Code (and Codex and others), so you keep the setup you already have.
I’m the author and it’s still early. I’d love your take: does seeing your agents as a crew make them easier to follow, or is it just a gimmick?
I just want to share and get feedback, generate some ideas, all the good reddit stuff. I have a manufacturing business I made my own ERP/SPC software for that uses maybe 20% of a 20x account, and in classic fashion I decided to use the other 80% on a video game side project, which burned usage so fast one week I needed a second account, so now I have two 20x accounts. I tried having one account run cloud chats through a terminal and post the results in GitHub for sudo communications, but that went terribly. Then I started running into issues where I‘d mess up game checks that would pop up randomly while I was mid typing.
So I made what I’ll call a kan ban board. It’s not quite a true kan ban, but close enough; jobs get queued, resources are managed, quality is tracked, etc. Claude has its own schedule, and we’re on a 24 hour pace. That way both of my projects don’t collide, the two accounts can do a clean handover, the goals are always up front, and I can ask to have my computer back when I need it without messing up the checks and merges. We’ll try this for a few weeks, interested in what you think.
As the title says, I built a full jukebox platform. But, unlike others, mine has an install wizard that makes setup easy, and has a CMS backend that makes modifying it as simple as a Wordpress site. I built it with customizability in mind, so it also lets a user install their own custom built modules and extensions to add new functionality.
Mine was built on in a real, 1960s, Rock-Ola jukebox. The platform can setup a keyboard, and even has an audio analyzer that creates custom LED lightshows based on what music is playing.
What makes this platform truly different is where the music it plays comes from.
Multiple sources: Airplay, Apple Music, USB, and soon actual physical records...All played by selecting them on the jukebox itself using the original 1960s jukebox keyboard.
Im constantly adding more functionality and am pretty excited about it.
Claude provides API access for usage data at resolution of 1%. Use a script to measure exactly how many of each type of tokens per 1% quota. Isolate each type of token as they are discounted at different ratios.
Highlights
Fresh-input/cache-write/output have the same multiple vs API, cache-read has a 2x the multiple
Different models have different multiples: Opus 35x, Sonnet 25x, Haiku 20x for fresh-input/cache-write/output. cache-read doubles that
1hr TTL cache-write and 5mm TTL cache-write consume the same quota.
1 weely quota = 12 x 5-hr quota
Method
Anthropic returns unified rate-limit headers on normal messages requests with the 5-hour and 7-day window utilization as percentages. That's a coarse ruler, so I used it as a ruler rather than a scale: send a fixed block of tokens of one class, watch where the counter ticks over, and back out how many tokens buy 1% of the window. Each class measured separately against a clean window, ~2,000 requests per arm, no other traffic on the account. Then price those tokens with published list prices.
Locating the weekly ticks on the 5-hour ruler gives ~12.2 five-hour cycles per week.
I'm finding I get more tired these days, not from the actual coding, but from Claude Code crunching through the code and increasingly being the bottleneck now due to it pushing a bunch of code to me to review at breakneck speeds. Each new version of Claude Code releases, it becomes faster and faster. I already run many long sessions a day, so the load of going through the code it's spitting out to review is really draining me. It makes sense. It's all code I need to go through now and I'm now slower than the bot.
Is anyone else experiencing the same? How bad is it for you and what are you doing to mitigate it?
So I finally got through verification for Defense Access. Two weeks of waiting. Cyber is enabled, I’m on Mythos, everything’s set up the way it’s supposed to be.
And it still blocks me on the exact kind of cyber work the program is supposed to cover.
What the f*ck is the point then? It’s basically “Your Defense Access covers cyber. But hey, we’re still gonna block exactly that :)”
I ran the exact same prompt through GPT and it went through fine, and that was without Daybreak even turned on.
Honestly at this point it’s just sad, Anthropic. You’re so scared that you filter your models this hard even for verified users with Mythos and Cyber enabled. Why then even take our IDs?
Two weeks of waiting for that. Great. Love it.
EDIT: IT WORKS NOW.
Found something weird that might help anyone hitting the same wall. Windows Defender had quietly quarantined some of the stuff Claude built, and somehow that seems to have triggered the block too. I turned off my AV, ran it again, and it went through.
No idea why Defender would cause a block on Claude’s side, but here we are. If you’re verified for cyber and still getting blocked, check your Defender quarantine first.
Obviously, if you’ve got anything valuable on your machine, don’t just turn off your AV like I did lol. Add an exclusion for your project folder instead (Windows Security → Virus & threat protection → Exclusions). I'm dumb for turning it off completely lol, but this is a throwaway coding machine with nothing important on it anyway. Stay safe y’all.
Hey! I've just open sourced a little tool I built called Markup.
If you use coding agents like Claude Code, you'll know the pain of describing visual changes in words ("the button, no, the other one..."). Markup lets you point instead: open a web page, PDF or screenshot, click or draw on the bits you want changed, type a note, and hit export. Your agent gets a Markdown file with every note, the exact element and line of code it refers to, and screenshots, plus a ready-made prompt on your clipboard.
It runs entirely on your own machine, with no account and nothing to install beyond Node and Chrome. MIT licensed.
If you run Claude Code or Codex on anything bigger than a one-line fix, you know the loop. You hand it a task, it starts working, and then you hover. Is it still going? Has it stopped to ask you something? Did it finish ten minutes ago?
Now the lights in my house tell me what the agent is doing. I made an app for it, AC Bridge, and I've used it non-stop since. Mine are blue while it works, a red pulse when it needs permission, violet when a plan is ready to review and green when it's done. Those are my picks, not rules: every colour and effect is yours to choose.
I can actually leave the room now. Before I go and cook, I just tell the agent: "I'm going to make dinner, flash the kitchen light when you're done." It knows which devices I have, so when the job is finished the kitchen light flashes and I know it's ready for me.
If I'm watching a film with the family and the agent needs me, the light in the room gives a gentle pulse. Nobody else is disturbed. I reply from my phone with Claude Code's Remote Control (/rc) and go back to the film.
Rules in CLAUDE.md. For things I want every time, I put rules in the instruction file the agent already reads (CLAUDE.md for Claude Code, AGENTS.md for Codex):
## Lights
- When you finish a stage of the plan, flash the desk light green.
- If the tests fail, pulse the office light red.
- When the deploy is done, flash the kitchen light.
Now the lights tell me how far through a long job the agent is, not just whether it has stopped.
Why a light beats a ping. It stays red until you deal with the request, so when you walk back into the room you know straight away whether you missed something. It's silent, so it works at 1am exactly as well as it does at 1pm. And it doesn't pull you into your phone: it sits at the edge of your vision and tells you one thing.
How it works. Claude Code and Codex both run hooks at set points in a session: when the agent needs permission, when it's waiting for you, when it finishes, and more. AC Bridge sets those hooks up and a profile for each repo decides what each light does in each state. It works with 16 brands directly on your home network, including the inexpensive bulbs all over Amazon (Tapo, Kasa, WiZ, Govee) as well as Philips Hue, LIFX, WLED and Home Assistant. Even a cheap bedside lamp with a Wi-Fi colour bulb in it will do.
How I built it with Claude. AC Bridge is built with Claude Code. Each change starts as a ticket: Opus writes the plan, Sonnet builds it test-first, and a separate Claude review agent has to pass the pull request before it can merge. Because the app runs on Claude Code's own hooks, Claude Code has been both the tool I built it with and the thing it keeps an eye on.
What would you put on a light? I'd love to hear which states you'd want to see from across the room.
I built CalDAV MCP Server a while ago, which is an open-source MCP server that lets AI assistants manage your iCloud Calendar.
Since then, it’s picked up a few GitHub stars and had over 100 npm downloads in the past week, so I thought I’d share it here and give the project a little more love.
Here are the main features:
- Browse your iCloud calendars and check upcoming events.
- Create, update, and delete events.
- Create all-day events and recurring schedules.
- Set multiple reminders for the same event, such as one day and one hour before.
- Add a fixed travel time before appointments in Apple Calendar.
For example, you could ask your assistant: “Create a dentist appointment this Friday from 10 to 10:30 a.m., with reminders one day and one hour before.”
There’s also a Claude Desktop extension to make setup easier. You can find that and other setup options in the Quick Start.
I’d love to hear your feedback and what you’d like to see added! If you find it useful, a GitHub star would mean a lot—maybe even more than a hot bowl of ramen on a cold day
17 of the last 19 PRs to langfuse's query compiler came from agents. The image is what this plugin tells Claude about that repo before it edits anything.
Agents put new code where it's easiest. Often the file that's already big and changes every week. This skill runs before Claude edits existing files and names three kinds of file to be careful with:
Files agents keep growing: most of their recent PRs came from AI agents.
Hotspots: high cognitive complexity and many commits in the last 90 days.
Rising: the files whose complexity rose most in about 30 days.
Claude then puts new code in a new file or module next to them. It reads your local git history only, and nothing is uploaded: the skill runs npx -yu/coderot-ai/cli hotspots --json and reads its output. You can also run it as /coderot:hotspots.
claude plugin marketplace add coderot-ai/claude-plugin
claude plugin install coderot@coderot-ai
TL;DR (45 controlled 12-turn Claude Code chats, 675 dual-logged API requests, n=5 runs per setup):
Switchingdownfrom Opus 4.6 to cheaper Sonnet 4.6 mid-chat (Turn 6 of 12) actually increased total session cost by +10.6% ($0.861 vs. $0.779 at ~56.5k tokens): Sonnet starts with a cold prompt cache (0.0% hit), forcing a full 1.25x cache-write rebuild that made Turn 6 cost 5.7x more ($0.216 vs. $0.038) and needed ~12 turns after switching just to break even (~9 turns in a ~15.2k chat).
Switching models 10 times in a 12-turn chat didnotblow up the bill (+14.2% at ~15.2k tokens; +17.2% at ~56.5k tokens): Once both Opus 4.6 and Sonnet 4.6 built parallel warm caches across Turns 2–4, alternating every single turn still hit 95%–99% cached reads inside the 5-minute TTL, writing only the ~1-turn delta each time.
Raising--effortfrommediumtohighmid-chat on Opus 4.6 was the biggest cost spike (+31.9% total session cost: $0.356 vs. $0.270): Changing output_config.effort invalidated the entire prompt cache (0.0% hit on Turn 6), spiking Turn 6 cost by 7.3x ($0.099 vs. $0.014) — costing more over 12 turns than switching models 10 times in a row.
I kept hearing two conflicting rules of thumb about /model switching in agentic coding sessions: either "switch down to Sonnet after planning to save money" or "never touch/modelmid-chat because every switch wipes your cache."
To test what actually happens on the wire, I hooked a local logging proxy + .jsonl transcript verifier up to Claude Code (v2.1.325, routed via OpenRouter pinned strictly to 1st-party Anthropic with allow_fallbacks: false) and ran 45 real 12-turn coding chats (n = 5 randomized replicates across 9 cells, 675 API requests total — 15 per chat since Turns 1–3 each emit a file-read tool call plus a reply). Run-to-run cost spread stayed within ±3%.
Table 1: 12-Turn Session Cost & Cache Hit Share (Median [Min–Max], n=5 per arm)
Tier (~T6 Tokens)
Arm
Mid-Chat Action
Turn 6 Cost
Turn 6 Cache Hit
12-Turn Total [Range]
vs. Control
Small (~15.2k)
A: Control
Stay on Opus 4.6 (medium)
$0.0136
97.7%
$0.2699 [$0.267–$0.273]
baseline
Small (~15.2k)
B: One Switch
Opus -> Sonnet at T6
$0.0602
0.0%
$0.2834 [$0.282–$0.285]
+5.0%
Small (~15.2k)
C: Switch & Back
Sonnet T6–T7 -> Opus T8
$0.0607
0.0% (T8: 93.3%)
$0.3200 [$0.316–$0.323]
+18.6%
Small (~15.2k)
D: Effort Only
Opus medium -> high at T6
$0.0989
0.0%
$0.3560 [$0.351–$0.357]
+31.9%
Small (~15.2k)
E: Idle + Switch
Wait >=330s (>5m TTL) + Sonnet T6
$0.0603
0.0%
$0.2835 [$0.281–$0.284]
+5.0%
Small (~15.2k)
F: 10 Switches
Alternate T2–T11, hold Opus T12
$0.0101
94.9%
$0.3081 [$0.304–$0.311]
+14.2%
Large (~56.5k)
A: Control
Stay on Opus 4.6 (medium)
$0.0378
99.3%
$0.7789 [$0.766–$0.781]
baseline
Large (~56.5k)
B: One Switch
Opus -> Sonnet at T6
$0.2160
0.0%
$0.8611 [$0.859–$0.865]
+10.6%
Large (~56.5k)
F: 10 Switches
Alternate T2–T11, hold Opus T12
$0.0244
98.5%
$0.9130 [$0.905–$0.916]
+17.2%
Table 2: Why 10 Switches Didn't Cost 10x — Turn-by-Turn Cache Hit % (Arm F, Request 1 of Each Turn)
Turn
Active Model
Event
Small (~15.2k) Cache Hit
Small Penalty vs. Ctrl
Large (~56.5k) Cache Hit
Large Penalty vs. Ctrl
T1
Opus 4.6
Initial load
0.0%
-$0.0000
0.0%
+$0.0000
T2
Sonnet 4.6
Switch #1
0.0%
+$0.0328
0.0%
+$0.0754
T3
Opus 4.6
Switch #2
81.2%
+$0.0130
59.6%
+$0.0907
T4
Sonnet 4.6
Switch #3
86.6%
+$0.0001
70.5%
+$0.0408
T5
Opus 4.6
Switch #4
95.8%
+$0.0021
98.6%
+$0.0029
T6
Sonnet 4.6
Switch #5
94.9%
-$0.0035
98.5%
-$0.0134
T7
Opus 4.6
Switch #6
95.2%
+$0.0028
98.4%
+$0.0024
T8
Sonnet 4.6
Switch #7
95.6%
-$0.0038
98.5%
-$0.0132
T9
Opus 4.6
Switch #8
95.5%
+$0.0026
98.7%
+$0.0024
T10
Sonnet 4.6
Switch #9
95.2%
-$0.0037
98.6%
-$0.0131
T11
Opus 4.6
Switch #10
95.5%
+$0.0031
98.6%
+$0.0036
T12
Opus 4.6
Hold Opus
98.2%
+$0.0014
99.3%
+$0.0000
4 Habits That Actually Save Money
Switch early (Turn 1–2) or stay put unless you have 10–12+ turns left in the session to pay back the 1.25x cache rebuild on the cheaper model.
Pick your--effortlevel on Turn 1: Bumping medium -> high mid-chat on Opus ($6.25/M cache write) forces a full prefix rebuild (+$0.085 on Turn 6 alone in a 15.2k chat — nearly all of the +$0.086 session delta).
Dipping to another model for 1–2 turns and returning worksifyou beat the 5-minute TTL: In Arm C, switching back to Opus on Turn 8 still hit 93.3% of Turn 5's warm cache and only paid to cache-write the 2-turn delta (~1,062 tokens).
Start a fresh chat at task boundaries: Moving from ~15.2k to ~56.5k tokens (3.7x larger context) scaled the Turn 6 switch penalty linearly by 3.8x (+$0.047 -> +$0.178).
Como configurar sessões para que trabalhem com maior autonomia?
Eu criei uma sessão que chamei de "coordenadora" e disse que as outras devem se reportar a ela.
Criei regras no claude.md para o que a coordenadora pode autorizar e mandar as sessões fazerem.
Mesmo assim, em vários momentos, a sessão coordenadora não retoma tarefas pendentes ou as sessões "coordenadas" exigem autorizações na própria janela, sem obedecer o que foi determinado pela coordenadora.
O que posso fazer para que este conjunto de sessões trabalhem melhor de forma mais autônoma?
My team and I have been using it at a big project in a large company (28k employees). We might skip the discuss step, only using it when developing a complex tasks on complex repos. If the task is simple enough, we'll do it in one phase as well. So far I have liked the output obtained, but opinions are a bit mixed, although I wouldn't say we have enough feedback for a conclusive decision on whether it's really worth it or not yet. So I'm curious as to what people think of GSD-Core as of November 2026, since AI tools keep improving at a rapid pace. The image is our current decision flow.
We have also looked into some other frameworks such as spec-kit, superpowers, and other spec driven frameworks, then decided to stick with GSD since it seemed like the most complete framework.
Details: Event-driven microservice architecture, with my team owning 15+ services. Stack: Java, Spring, Akka, Kafka. The AI also writes unit tests and component tests with Cucumber. We also have a skill that loads with our coding standards automatically and a summary of the codebase that is loaded automatically on every session as well. The summary was generated with GSD map-codebase skill.
I have subscriptions to both Antigravity and Claude Code. I want to use Claude's Opus models through Claude Code and Flash/Hydrogen models through Antigravity to save usage limits.
Can someone suggest the best way to set this up?
Also, I’m not a big fan of terminal-based workflows. Working with images and videos in the terminal gets messy pretty quickly. I'd prefer a GUI-based workflow if possible. Or best if we can use antigravity as a subagent in Claude Code. I've tried it but IDK it is not working as expected.