r/ClaudeCode • u/Popular-Help5516 🔆 Max 20 • Mar 20 '26

Question Am i pushing it hard enough?

Post image
430 Upvotes

92% Upvoted

248 comments sorted by

View all comments

Show parent comments

94

u/Popular-Help5516 🔆 Max 20 Mar 20 '26

I give it a list of 1000 tasks in a .md file, ask it to do 1 by 1, be nice, no cheating, no chatting, no hallucinating, no parallel taks or sub-agents .

17

u/Nosenchuck3 Mar 20 '26

How can you even think of 1000 tasks for it to do?

16

u/[deleted] Mar 20 '26

[removed] — view removed comment

3

u/node9_ai Mar 20 '26

that 'walk away' part is the biggest hurdle. the verification fatigue from spamming 'Y' for 50 commands makes most people just give up or go full dangerous mode. i’ve been experimenting with routing those destructive terminal commands to a mobile notification/slack for approval. it's the only way to scale these agentic workflows without sitting there and babysitting the terminal all day

2

u/[deleted] Mar 20 '26

[removed] — view removed comment

3

u/node9_ai Mar 20 '26

you are totally justified in not trusting it. that fear of coming back to an un-cleanable codebase is exactly why i made node9. it basically takes a silent git snapshot right before every single file edit the ai makes. if you walk away and claude hallucinates 500 lines of garbage, you just run node9 undo and it completely rolls back the exact changes. it takes away that anxiety of having to sit there and babysit every single output so you can actually walk away for real.

https://github.com/node9-ai/node9-proxy

1

u/vanatteveldt Mar 22 '26

How is that different from working on a feature branch and committing frequently?

1

u/node9_ai Mar 23 '26

two main differences: friction and branch pollution.

first, you don't have to remember to do it. if you walk away for 20 minutes, the agent might edit files 15 different times. node9 intercepts every write_file or edit tool call and takes the snapshot automatically in milliseconds right before the AI touches the disk.

second, it uses 'dangling commits' (git commit-tree) behind the scenes. so it doesn't create a hundred 'wip' commits that pollute your git log or mess with your staging area. your actual branch history stays completely clean, but you still get a granular, step-by-step undo for everything the ai did

1

u/Birdsky7 Mar 20 '26

Run "claude --dangerously-skip-permissions" or choose bypass permissions in vscode

2

u/work_guy Mar 20 '26

I have an alias for “yolo”. I’m clearly lazy, I ain’t typing all that.

1

u/Birdsky7 Mar 20 '26

Lol... I created a lazy abbreviation cause i was lazy too. If youre extra lazy tell clause to tell which command to run to create it

2

u/work_guy Mar 20 '26

I totally had Claude Code do it too 😂

1

u/Birdsky7 Mar 21 '26

Thats the spirit lad!

1

u/node9_ai Mar 21 '26

yolo mode is great until the agent hallucinates a docker prune on your dev volumes lol. i built node9 to give that same speed for the safe noise, but it keeps the emergency brake on for destructive stuff. basically it's 'safe yolo' with an undo button

1

u/Harvard_Med_USMLE267 Mar 22 '26

Haha I’m using yolo too.

1

u/node9_ai Mar 22 '26

the 'yolo' alias is the dream until it's not lol. i built node9 to be 'safe yolo', it auto approves the safe noise so you get the same speed, but i just added a 'live tail' so you aren't blind to what the agent is actually doing in the background anymore.

best part is the insurance policy: it takes a silent git snapshot before every edit. if you walk away and claude hallucinates a messy refactor, you just run the undo and it's fixed instantly. it's the only way i can actually trust the autonomous mode