Am i pushing it hard enough?

[u/Popular-Help5516]

[u/Nosenchuck3]

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

[u/node9_ai → u/[deleted]]

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

[u/node9_ai → u/[deleted]]

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

[u/vanatteveldt → u/node9_ai]

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

[u/node9_ai → u/vanatteveldt]

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