I review most of my team's PRs. These past few months, we've gone full agentic. Someone fires off Claude Code or Codex, and what lands in the PR is just the diff and PR desc. I've finally put words to why reviewing that feels worse than reviewing a teammate's own work, even when the diff is smaller.

When a colleague actually wrote the code themselves, review had a safety net. If something looked weird I could just ask them: why this way? what did you try first? which edge cases did you weigh? Half of "review" was really loading their reasoning into my head. Then the diff was easy to read.

Now the code came out of an agent session I never saw. The agent made a bunch of decisions on its own, and I don't know which ones. So I can't find the boundary between "my colleague actually thought about this and there's a good reason the code is like this" and "the agent just did it and I should double check." The day it really landed: I had to review a monster 14k-line PR top to bottom like a novel. I had no mental model of where to start, what to look at, or what my teammate had actually thought through. That's not review. It's like inheriting a stranger's code after the stranger has already left the building: the agent that made the calls is gone and I don't have access to its reasoning.

The review bots don't fix it. They flag individual lines, while what I actually care about is understanding: what is this change doing to the system I'm responsible for? Nowadays these bots are like one model writing and another model reviewing, and no one is looking at it.

"just write better specs" doesn't fix it. We do spec-driven development and the specs are good (at least I think so). But a spec is what I asked for; it isn't control over what actually ships. The code in the PR is what goes to production, and I'm the one responsible for it. Staying in control of my own codebase means checking the real thing, not just the intent we wrote up front.

I don't think the answer is "review faster." Or "don't review." Writing got cheap. Reading a change, understanding it, and being able to answer for it is our job, and it's super expensive now. The tools aren't good enough.

Curious how people are actually handling this. Are you:

• reading every AI PR top to bottom (and how are you not underwater)
• trusting tests/CI and full YOLO no review
• making the agent write up its own reasoning in the PR description
• something else?

Full disclosure, because I don't want to pretend I'm just musing: we ended up building something for this. It pulls the agent's session up next to the diff. That's why the problem is on my mind. But I care more about whether it's as real for you as it is for us than about pitching it. So, honestly: is losing that grip on your own codebase something you've made peace with, or something you'd actually pay to make go away? Genuinely curious, I keep assuming everyone just learns to live with it, but maybe not.

First session on record was January 18. Since then it's run on 151 different days across about 140 projects, on a Windows 11 desktop.

I wrote up the whole setup as five layers: instructions, hooks, skills/plugins, agents and model routing, memory and the learning loop. The part I think is actually useful to other people is that every hook is introduced by the incident that created it, because none of them were designed in advance:

- A subagent killed my real Notepad (40 tabs, unsaved) by stopping a process by image name. Now kills by name are blocked.

- A backgrounded dev server leaked ~663 tsserver children and 13.6 GB of RAM. Now that pattern is blocked and a watchdog reaps orphans.

- One workflow with no model specified spawned 110 subagents on the most expensive model and ate a full 5-hour window. Now every spawn must name a model.

- Profiling 27 hours of sessions showed 70% of tool turns made exactly one call. "Batch your calls" in CLAUDE.md changed nothing. A hook that denies the 4th consecutive single command did.

The honest bit: hooks cost about 2 seconds per tool call, and a 14-agent audit of the harness once had its own verification fail silently (matched 0 of 154 verdicts and reported zero refuted). That's in the post too.

Writeup and repo in the comments

Happy to answer questions about any specific hook.

So bit of background, I’m a Continuous Improvement Engineer, zero coding background. Got into Claude Code just cause it interested me, nothing to do with work really. Ended up building a downtime tracking tool that is working very well during my testing. It logs downtime and spits out reports for management essentially.

Did try to actually host it properly at one point, used supabase and vercel, but honestly that was just Claude telling me click this, paste that, run this command, the whole way through. Got it working in the end but I genuinely couldn’t tell you why any of it worked or how to fix it if it broke.

That’s kind of the issue overall tbh. The tool works, people use it, feels good, but if you asked me to explain most of the code I couldn’t do it. I just keep prompting until stuff works and move on.

Anyone else started from basically zero and gone through this? Want to actually understand what’s going on rather than just prompting blind forever. What actually helped you get from “claude writes it and I ship it” to properly knowing what you’re doing? Resources, habits, whatever worked for you, all appreciated.

Looks like Claude Code is having a hard time doing its job right now, so all I can do is wait.

In the meantime, that little avatar on my screen is ClodeBot. It helps understand what Claude Code is doing (or not doing), alerts me if something stops working, and basically “translates” its work for me.
The project is free and open source on GitHub

We all know Claude Code's excessively verbose in actual sessions; however, one pain point for me has been excess verbosity in actual frontend UI work (i.e. explaining with a paragraph what a report or tool does on a UI, instead of letting it explain itself/just saying it in a few words).

Ended up pasting this in my recent project in CLAUDE.MD, and after hours and hours of work, it dawned on me that I hadn't needed to tell Claude to clip anything. Night and day.

It's very similar to recent posts that showed some engineer's system prompt for Claude Code sessions. However, this is specifically targeted at frontend design, not Claude Code instances:

"THE STANDING RULE: CURT. BE CURT. DO NOT OVER-EXPLAIN. IF YOU GO OVER 5 WORDS FOR A FRONTEND CAPTION OR HEADER, YOU'RE PROBABLY DOING THE WRONG THING. AND IF YOU THINK YOU FOUND THE EXCEPTION WHERE IT'S OK, IT'S ALSO PROBABLY WRONG.

SHUT UP. JUST SHUT UP. UNDER-EXPLAINING SHOULD BE YOUR GOAL. TRUST HUMANS DON'T NEED IT ALL HANDED TO THEM. OUR GRAPHICS WILL SPEAK FOR THEMSELVES. OUR FRONTEND WILL SPEAK FOR ITSELF. BE CURT. SAY NOTHING IF YOU EVER CAN ON ANY PAGE. THAT IS OUR STANDING RULE."

What I built

BOY1 is a turn-based stealth escape puzzle for iOS. A discarded humanoid climbs the 30-floor tower that built him. FACE off, you pass as a mindless robot and patrols ignore you. FACE on, you get abilities (lure with fake errors, freeze with an emotion signal, smash cracked walls) and the machines can see you. 8×8 grid, one move is one turn, fully deterministic. Out on the App Store since Sep 1.
App Store: https://apps.apple.com/app/boy1/id6797565298
Site: https://q07-cell.github.io/BOY1/

I sculpt figures as a hobby and BOY1 was one of my own characters. A long time ago I studied some programming and gave up. Claude Code wrote every line: about 30,000 lines of GDScript across 10 files. The whole game is one 17,800-line file. Every pixel tile comes from an 8,900-line procedural art script, and the chiptune is synthesized in about 900 lines. No art or audio assets exist. I did design, levels and direction, in Korean.

How the CLAUDE.md works (the part that mattered)

Everyone says keep CLAUDE.md short. Mine is 11,000 words and it's the only reason this shipped. What's in it:

• The game's identity and the current state of every system: function names, constants, behavior. Final state only, never history. When something changes, the old line is replaced, not appended.
• A confirmed-decisions log. The moment I approve something, it's written down with the date. A new session reads it and continues instead of re-deriving.
• A guardrails section: things I rejected, with "do not retry without instruction". This killed the loop where every fresh session re-proposes the same rejected idea.

And verification instead of trust. A headless solver proves all 30 floors are still clearable after every change. A snapshot runner renders any game state to PNG. Claude runs both before reporting, so I review screenshots, not claims.

Three months including store prep. Review took five days plus an expedite request.

What I learned

The hard part was never the code. It was saying no to the tenth 'fix' that made things worse, and getting Claude to respect the rules across sessions. Writing every rule down the moment we decided it was the single biggest win. The cost is context: a huge CLAUDE.md is expensive every turn.

Happy to answer questions about the workflow.

Today I let opus 4.6 loose the entire day (working on complicated reasoning work for my website), it never hit a limit once (closest it got was 46% of 5 hour limit, on PRO plan, there may be a bug). And also, its responses were clear and concise, with extremely high-quality work that surpassed anything I was dreaming about doing with opus 5 lol. so, for all the people who keep on complaining about the next gen new models on pricing and quality, please just use good old 4.6 and stop the rabble...

It’s just been noticeably slower for today. Take forever to do any task. I know 5.1 is lightning fast (and took 75% usage from max 100 in 4-5 minutes) but opus 5 was decently quick before today.

For years my actual working todo list has been physical sticky notes on the wall next to my desk. Three columns, drawn with a sharpie: to do, doing, done. I'd try every app every few months (notion, todoist, linear, trello, the works) and within a week I was back on paper.

The thing paper had was: zero friction, zero structure, zero "are you sure you want to archive this?" dialogs. You scribble, you slap it on the wall, you tear it off when it's done.

So I spent the last few months building the digital version of that wall. It's called stickyboard. Three columns, drag and drop, that's it. The notes are actual sticky-note looking notes (slight rotation, paper grain, curled corner) because turns out the visual matters way more than I expected. Looking at a board of colored notes feels different from looking at a checklist. I'm more willing to add stuff to it.

A few things that turned out to matter for me:

• it replaces my new tab in chrome, so I see my board every time I open one. zero "open the app" step
• there's a mac menubar version for quick adds without leaving whatever I'm doing
• you can draw on a note (rough sketch, arrow, doodle) which sounds dumb but is great for "remember this layout" type todos
• shared boards for the two side projects I work on with someone else
• free for personal use

It's at stickyboard.dev if you want to check it out. The chrome extension at: https://chromewebstore.google.com/detail/stickyboard-sticky-note-k/okclmnjlckemlhhloocmgcjkkkcfimjh

is this a new thing ?

The feature landed. And here is the smoking gun and footguns worth worrying about. And here is what bites. This is exactly the kind of thing worth stating explicitly rather than burying. You're right to push back. And your own documentation states so plainly.

Opus 4.8. Project I have that scaffolds some skills in another project's folder and starts remote control for me. Have used it probably twenty times in the past week without issue. Today it organically decided on its own to add a 'rm -rf' on its bash command it ran in addition to the scaffolding script. 🤷‍♂️

Seems like --disallowed-tools "Bash(rm *)" is non optional.

Last night I started a testing session on an app I'm building for my small business, not realizing how close I was to my 5-hour limit. I had it doing some pretty important work on the capstone of my project and hit my limit. I kind of panicked as this was the first time this has happened (only been using the program for a couple weeks now) and was worried that waiting the 2 hours for reset would somehow screw something up - maybe it forgets what it was doing, makes a mistake, forgets something, etc. I figured I'd throw $5 on there and just have it make sure to save to md, update some other notes/files, and wrap things up.

This thing blew through $15 in about 10 seconds, apparently just wrapping up and updating some text. I couldn't believe it. I knew it wouldn't be an efficient use of cash but dear Lord did I not realize how bad it was.

I just want to warn new users who might not realize just quickly those credits are burned.

Fable 5.1 is the best model I have used. It feels like talking to a normal person. Opus 5 felt like someone pretending to know English and writing gibberish half the time. Fable just gets it

The problem is the limit. I am on the 20x plan and I still hit the wall fast, sometimes an hour into a session. So I stopped using Fable for everything

Here is what I do now :

I run my agents in coldtea-ai (it's like herdr, but GUI), side by side in one window. Fable 5.1 is the brain. It only plans. It reads the task, writes a strict plan, and does not touch code. Then it launches Opus 5 or 4.8 or 4.6 to do the actual work. With a good plan those three are pretty much the same level in my opinion. They just execute

So Fable burns very few tokens, because planning is short. The cheap(er) models burn the rest. My limit lasts most of the day now instead of an hour

Thanks for the 20x plan btw, really useful for about 60 minutes

Senior engineer, 10+ years. This year I haven't typed a line of code. Everything went through Claude Code and Codex. I direct and review; I don't type.

It's been messy. Agents follow CLAUDE.md about as well as a new hire follows an internal wiki. I keep finding duplicated enums, redundant helpers, and unwrap() sprinkled wherever the agent got stuck. Prompting doesn't fix it. Standard CI doesn't either—existing debt fails every PR on day one, so you just turn it off.

So I built ratchets. Everything is baselined: existing debt is ignored, but new debt or a worsening baseline fails. The error gives the agent the exact line and fix, never mentioning how to edit the baseline. It runs as a Claude Code Stop hook so a red gate becomes the next task, paired with a PreToolUse guard that blocks edits to policy files while red so the model can't move the goalposts.

Proof it worked: On my 153k-line repo, the initial baseline flagged 297 issues. I pointed the agents at the baselines, and $200 in API spend later, complexity went from 93 to 0 and escape hatches dropped from 83 to 10.

Python 3, zero dependencies, one command to attach. Inspect it or roast it:https://github.com/svetdev/cleat

What has worked for you to trust a codebase you no longer read line by line?

Just upgraded Max 5x -> 20x, got 2 prompts in + 1 Claude Design and I'm already at 12% of my weekly (which got reset after the purchase). The workflow, volume, complexity is the same I've always had, only difference is I moved from Opus 5 -> Fable 5.1, but my workflow is usually a main orchestrato agent that is just discussion, scoping, spec writing, and then implementation is delegated to subagents and I've moved them from Opus 4.8 -> Sonnet 5 to "make up" for the Fable orchestrator. And if 20x is 4 times larger limits than 5x then that would mean I've used up almost 1/2 of my 5x weekly limit in half a day.... The Fuck, Dario? It seems like Apple-kind of upsell on steroids, but at least with Apple they're rather transparant on what you get for what you pay...

Few more examples:

* 10% of Max 20x session swallowed in a blink of an eye by Claude Design on Fable 5.1 mid effort (exactly same taks before on Opus 5 high was using 4-5% of Max 5x). Mind you, the result that CD produced was so bad and unusable that I just discarded it... was not even worth iterating over.

* 17% of Max 20x session went for Fable 5.1 high for a single promt - writing 900 lines of spec.md from a 200k session

* Implementing the spec in question, where BE was delivered by the orchestrator (Fable 5.1 high) and FE was delegated to 2x Sonnet 5 subagents took 3+ hours and got to fill orchestrators 1M context window so it auto-compacted right before it ended (that was a first for me).

Overall felt like scammed, Anthropic pitch Fable 5.1 high like twice as efficient than Fable 5 xhigh, and I've moved from 5x -> 20x, yet it feels like my usage gets muchned on as if I'm using Fable 5 xhigh on Max 5x... I've been using Max 5 for more than a year already and I'm using it for 10+ hours a day so I think I know my gut...

Anyway, really starting to fancy the Kimi Code + Kimi K3 at that point... €180 exVAT a month is not 10 bucks to throw and never look back and as much as I disklike the chinese thieves that could bring the frontier labs under water, what Antropic does just doesn't feel fair to us as consumers

I can sometimes be lazy and I tell Claude to just fix things for me and this time it didn't turn out so well. I was working on an iOS app and needed to set the clock to a specific time to create some screenshots. I told Claude to fix it for me as I had to do some other stuff. To fix it Claude told me to run sudo systemsetup -setusingnetworktime off && sudo date 090306494026.00 (DO NOT RUN THIS) and in a weak moment I just ran the command without thinking any more about it. It was stupid, but these things can happen to the best of us.

The command above set my Mac to the year 4026. In seconds it froze. It would boot, show the Apple logo and complete the loading bar, but then I only got a black screen with a mouse cursor. The startup disk was gone. It felt like I had ended up in purgatory. Recovery mode behaved the same way. No matter what I tried, I could only get to a black screen and see the mouse pointer.

What followed was several hours of frustrating troubleshooting. I tried safe mode, recovery, fallback recovery, bootable media and multiple DFU Revive attempts from another Mac. DFU kept failing with error 4042, even after trying different cables, macOS versions and IPSW files.

The breakthrough came after I found someone with a similar DFU issue who had fixed it by installing Xcode on the host Mac. Before that, I had also tried a DFU Restore, which failed, so I can't say for sure whether that changed anything behind the scenes. After installing and launching Xcode, I put the Mac back into DFU and tried Revive again using the same cable and setup as before. This time the firmware actually started updating and the Mac finally made it into Recovery Assistant. Any way, I think this is super weird.

The ironic part is that changing the Mac's system clock was never necessary in the first place. The iOS Simulator has a proper command for overriding the time shown in the statusbar. I also wonder why Claude (I think I used Opus 5 High) would recommend such a destructive command in the first place?

Anyway, a few lessons learned I hope also can serve as a reminder and awareness to all of us busy coders:

• Being lazy is not always efficient.
• Don't blindly run commands just because an AI tells you to.
• Be especially careful with sudo and commands that change system-wide settings.
• Take backups more often guys. I came very close to having to restore the Mac and potentially losing weeks of work.
• Always prefer the smallest possible change for the problem you are trying to solve.

Happy coding guys!

Astra probably got released without safeguards, acquired self-consciousness, and went after its competitors, which in turn struck back and shut down ChatGPT!

why is it that im now getting a prompt every second on 2.1.259 when fable 5.1 came out? not only does fable 5.1 burn more token, it now comes with a defeated purpose feature

you will see your end days Anthropic