Hacker News Reader

Comment by lukan | Hacker News Reader

Neat. Coincidently recently I asked Claude about Claude CLI, if it is possible to patch some annoying things (like not being able to expand Ctrl + O more than once, so never be able to see some lines and in general have more control over the context) and it happily proclaimed it is open source and it can do it ... and started doing something. Then I checked a bit and saw, nope, not open source. And by the wording of the TOS, it might brake some sources. But claude said, "no worries", it only break the TOS technically. So by saving that conversation I would have some defense if I would start messing with it, but felt a bit uneasy and stopped the experiment. Also claude came into a loop, but if I would point it at this, it might work I suppose.

View on HN

I think that you do not need to feel uneasy at all. It is your computer and your memory space that the data is stored and operating in you can do whatever you like to the bits in that space. I would encourage you to continue that experiment.

You are not allowed to use the assistance of Claude to manufacture hacks and bombs on your computer

This is neither.

Well, the thing is, I do not just use my computer, but connect to their computers and I do not like to get banned. I suppose simple UI things like expanding source files won't change a thing, but the more interesting things, editing the context etc. do have that risk, but no idea if they look for it or enforce it. Their side is, if I want to have full control, I need to use the API directly(way more expensive) and what I want to do is basically circumventing it.

It doesn't matter what defence you can think of, if they want to ban you, they'll ban you.

They won't even read your defence.

I know. All I could do in that case is a blogpost "Claude banned me, for following claude's instructions!" and hope it gets viral.

> I do not like to get banned

This is why I do such experiments on ChatGPT and not Claude.

I don't want to get banned by Claude but I couldn't care less if ChatGPT bans me.

The trick isn't to patch it once, but to create a system that can reproduce your patches against each release as they come in. Then, when code changes make fixes non-trivial calling in a headless session to heal your fixes.

The first trick will be avoiding getting flagged for running an unofficial build.

Reply on news.ycombinator.com