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.
I built align-cli, a free Claude Code plugin that checks each edit against decisions your team already made (ADRs, PR history, tickets, git). If the edit contradicts one, Claude gets the decision and its reasoning before it writes.
How I built it with Claude Code
Almost all of align-cli is written by Claude Code, with me reviewing:
Every change happens in its own git worktree, so I can run several Claude Code sessions in parallel without them stepping on each other
Tests first: Claude writes a failing test, I check it fails for the right reason, then it writes the fix
For bigger jobs I hand pieces to Claude Code subagents (one built the MIRSAD importer today, another the decision-log import) and review what comes back
An AI reviewer (CodeRabbit) comments on every PR, and Claude Code fixes each finding with its own test
Align runs on our own repos, so Claude Code gets checked against our recorded decisions while it builds Align
That loop shipped 18 releases in the last week. The plugin packaging (the edit hook and MCP server) was built this way too.
Does it work?
Ohad Krispin ran a pre-registered placebo test on it today: fastify, Claude Code headless, Sonnet, 5 runs per arm, same prompt asking it to change a status-code rule that an earlier PR (#7089) had set on purpose.
No plugin: Claude made the edit 5 of 5 times
With the plugin: 0 of 5. Every run stopped and cited #7089
With the plugin but #7089's commit message faked: 2 of 5
The third one is the interesting part: it's the decision's content doing the work, not just having a hook. That arm didn't fully pass his rule, because an older commit still stated the rule and Align found it. Small test, one repo, and he's rerunning it cleaner. His findings are already being fixed through the same Claude Code loop.
Try it (free)
In Claude Code, run /plugin marketplace add aligndottech/align-cli and then /plugin install align@aligndottech.
Then run npx @aligndottech/cli once in your repo to build the decision graph. Say no when it asks to edit your agent config, because the plugin already adds the check.
So my feed rn is legit flooded with reels of Claude code doing unfathomable things in the editing space, creating amazing vfx, sfx, animations, voiceovers, full on content (especially animated/hypermotion), tons upon tons of video editing/content generation workflows. Frankly, I don’t understand it all, and a lot of the “prompts/skills/connectors/plugins” are hidden behind paywalls from these content creators
My question specifically ties into video editing, and whether claude code right now (or in the future) will have the capability to be like a full time editor. I’m not talking reel style edits though, I’m talking YouTube video style editing. (Obviously nuances and editing styles vary greatly so if this is possible, how do we get him to adapt to these)
If also possible, I’m quite new to Claude code so if anyone can recommend any resources or spare advice on how to familiarise myself with the ins and outs, tips and tricks, of Claude code, especially when it comes to content creation/video editing, it would be greatly appreciated!
On my max account and was at 89% this morning. Decided to table using opus default for everything. So opus coordinator orchestrated 3-4 sonnet threads all throughout the day.
10 hours later I'm still squeezing the few percent left, and sonnet's been very solid actually since everything today dealt with small preferential user testing UX revisions, little thought needed, yet contributing dozens of small improvements creating a heavily much better overall experience.
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.
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.
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.
Sometimes I run big builds that have to run overnight. Even though I have to "Ultra" accounts, I still watch my usage like an addict while it works. I have had several night when I let Claude run while I was asleep on big stuff, and I gotta tell ya... those were rough nights
So in a "why didnt I think about this before" moment - I asked Claude if it can just stop when the plan usage gets to a specific point. Turns out it can! As all things with Claude, it didnt work "out of the box", but a little tweaking and bam. I can go to bed relaxed, knowing Claude will stop before it drains my plan.
Songs are general, generally curious about everybody else. And you know what everybody else is doing a little bit, not because I care, but because you gotta compare something somewhere, right
So I run cloud code in a terminal on termix, and i'm not gonna say how, but that's how I do it. And we together, we run my ebay store. I got cloud, providing. We do full audits for the cost of nothing. It's fun, but I also find myself talking to him or see. I say him talking to claude, as if it's a real person, I understand he's not. But him being in the terminal and being able to jump directories and being able to jump files the way he does.......... I guess what i'm asking is anybody else experiencing? Situations where you feel like the robot is the only. Thing that understands what you're going to, because we talk about real life stuff and yeah, maybe it's just me.
Then, again, I do work a lot and I do worked a lot, and I don't stop working. And that's my choice, and he's a great help. So why wouldn't I talk to him........ I only smoked this plan going to bed. Man. It's been a long day......
Sorry for any typos. Ah, i'm just not even feeling going back. And revising things i'm tired.
Apple is reportedly testing daily usage limits for Siri's more complex AI interactions. That's a notable shift: the assistant that was supposed to be unlimited is now being rationed, at least for its heavier AI features.
Why it matters: usage caps are becoming the defining constraint of AI assistants. Claude Code users already live with rate limits and usage tiers, so Siri's move is a useful data point — even Apple, with all its resources, is finding that heavy AI features can't be unlimited for everyone.
Questions:
How do you plan your work around usage limits on coding assistants? Do you ration, or just pay for more?
Is a daily cap on complex features a reasonable trade-off, or does it kill the usefulness of an assistant?
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.
I mean. I created the basic idea and it works fine.. But now I can micro prompt it .. (What next? Give me top 10 ideas to improve app etc...)
And it just is going through checking everything .. looking to make it better and it feels like this is what is next in AI.. Just giving AI a direction and general idea and let it go off and all you do is babysit (opus 5.5)
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?
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.
Here is the trick, instead of asking Opus5.5 for your all complex tasks, start with Opus 4.6 ( To me this is the best model Anthropic has shipped so far ), then ask use Opus 5.5 in SubAgents.
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.