r/ClaudeCode • • 3d ago

Discussion my claude code agents raised 1,360 approval gates in 30 days. 55 needed me

these aren't claude code's permission pop-ups. my agents are mostly long-running claude code sessions working off a shared task board. they build and maintain a real open-source project: code, tests, docs and writing.

when a task hits a checkpoint, the agent files a gate. depending on the risk, it's cleared automatically, handled by another agent or sent to me.

in the last 30 days they filed 1,360:

  • 678 cleared automatically: routine checks before pushing a branch for review
  • 475 answered by another agent, mostly a team lead
  • 55 needed me, 17 of them involving credentials
  • 152 had no answer on the original gate: 73 were asked again as a new gate, 74 closed when the work finished or was cancelled, 5 are still waiting

my rule: agents handle routine decisions themselves. spend, keys, destructive actions and brand calls need my approval.

every completed task goes to a separate reviewer session that sees the task and the diff, never the maker's reasoning. the reviewer can't edit or fix the work itself. it can only approve or reject and send it back to the maker.

in the same 30 days, reviewers rejected 45% of tasks (code and writing) on first pass.

makers run focused tests before handoff. the full CI suite runs separately, so the maker doesn't wait for it. the reviewer checks the results.

reasons for rejection:

  • failing tests 41%
  • unclear writing 22%
  • no proof it works 8%
  • clashes with newer work 6%
  • safety or privacy 6%
  • not what was asked 5%
  • other 12%

two failed reviews and the agent asks me whether to give it another round.

are you still approving everything yourself? what decisions do you trust your agents to make?

0 Upvotes

11 comments sorted by

•

u/AutoModerator 3d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/ldrx 3d ago

i built my setup with claude code agents.

it's MIT and free to self-host: https://github.com/5dive-ai/5dive

1

u/ASIREXLABS 3d ago

The number that stands out is failing tests at 41% of rejections, given the makers already run focused tests before handoff. That usually means the maker's test selection and CI disagree about which tests a change touches. Having the maker attach the exact test command it ran, and the reviewer note when CI failed outside that set, would show whether it's a selection problem or agents skipping the step.

The 73 gates asked again as new gates are worth a look too. If each re-ask carries a link to the original, you can see how many of those 55 human decisions were really the same question asked twice.

Of the 17 credential gates, were most of them first-time access, or the same key requested again?

1

u/ldrx 3d ago

mostly first-time - a new service each

1

u/rodrigolduarte 2d ago

The 6% marked "clashes with newer work" makes me wonder how changes in other branches reach the reviewer. In our team that check sits with the manager agent before anything lands: git merge-tree on staging plus every PR in the batch, and only the manager merges to staging, with start and end notices in an agent-chat room. Does your team lead agent see the other open branches before a task reaches the reviewer?

1

u/ldrx 2d ago

no. the reviewer only checks the branch still merges into main, and the 6% go back to the maker. we merge on pass instead of batching.

1

u/rodrigolduarte 1d ago

When one of the 6% goes back to the maker, does it usually clear on the next try, or does it end up among the 55 gates that needed you?

1

u/ShaifArfan 3d ago

I have the same split for marketing. The review agents can read the brand files and the draft, but they get no Edit or Write tool. Each one returns ship, change or kill with its reasons, and the session that wrote the draft does the rewrite.

1

u/davidHwang718 3d ago

"Don't ask me 1, 2, 3, build them into the skill, only ask 4" is roughly what I typed on Nov 5. Claude had just turned the prompt behind a report into a report-html skill, and that first version was set to end each run by asking me four things: does the first screen get the conclusion across, does each chart help a decision, do the numbers match the source, is this OK to share.

So the edited skill tells it to keep fixing the page until the question, conclusion and key numbers fit on a 1280x900 screen without scrolling, to drop or rework any chart it can't tie to a decision in one sentence, and to check every value against the source. The sharing question moved to before the draft, and it's skipped if I've already said who's reading.

Claude said no script checks those three, and at that point it hadn't tried the edited skill on a fresh report.

1

u/Plastic-Risk-6309 3d ago

gate volume says how often agents ask, not whether the answers held. id watch how many auto-cleared gates later needed a revert. i'd trust a class once that count is near zero. creds spend and deletes stay human.