how do you trust the code claude wrote? don't you get anxiety "what if there's an error in tui code and it would mess up my git repo"?

▲

whazor 6 minutes ago | parent | next [-]

I push my branches daily, so I wouldn't lose that much work. If it breaks then I ask it to fix it.

▲

freedomben an hour ago | parent | prev | next [-]

I'm not GP, but I have backups, plus I always make sure I've committed and pushed all code I care about to the remote. I do this even when running a prompt in an agent. That goes for running most things actually, not just CC. If claude code runs a git push -f then that could really hurt, but I have enough confidence from working with the agents that they aren't going to do that that it's worth it to me to take the risk in exchange for the convenience of using the agent.

▲

embedding-shape an hour ago | parent | prev | next [-]

> how do you trust the code claude wrote?

If that's something you're worried about, review the code before running it.

> don't you get anxiety "what if there's an error in tui code and it would mess up my git repo"?

I think you might want to not run untrusted programs in an environment like that, alternatively find a way of start being able to trust the program. Either approaches work, and works best depending on what you're trying to do.

▲

sclangdon 2 hours ago | parent | prev | next [-]

Isn't it this case no matter who wrote the code? How do you ever run anything if you're worried about bugs?

	▲	hennell 26 minutes ago \| parent \| next [-]
		Different type of creator, different type of bugs. I'd assume a human giving me a way to delete merged branches has probably had the same issue, solved the same problem and understands unspecified context around the problem (e.g protect local data). They probably run it themselves so bugs are most likely to occur in edge cases around none standard use as it works for them. Ais are giving you what they get from common patterns, parsing documentation etc. Depending what you're asking this might be an entirely novel combination of commands never run before. And depending on the model/prompt it might solve in a way any human would balk at (push main to origin, delete .git, re-clone from origin. Merged local branches are gone!) It's like the ai art issues - people struggle with relative proportions and tones and making it look real. Ai has no issues with tones, but will add extra fingers or arms etc that humans rarely struggle with. You have to look for different things, and Ai bugs are definitely more dangerous than (most) human bugs. (Depends a little, it's pretty easy to tell if a human knows what they're talking about. There's for sure humans who could write super destructive code, but other elements usually make you suspicious and worried about the code before that)
	▲	phailhaus 2 hours ago \| parent \| prev [-]
		When I write the code myself, I'm not worried that I snuck a `git reset --hard` somewhere.

▲

ithkuil an hour ago | parent | prev [-]

I assume that whatever I type can be also flawed and take precautions like backups etc