Live data from Hacker News

Show HN: Claude Composer

github.com

61–70 of 99 posts

Re: Show HN: Claude Composer

#61

Am I the only person who just runs claude code in yolo mode? Curious about these tools for fine-grained permission, did you get burned in a bad way? I think I'm going to trigger half of hacker news with this, but honestly nothing claude does on my machine seems particularly scary, and it's way too far from AGI for me to worry about hostile takeover right now =P

If you add mcp tooling you can quickly go off local.

I’m less worried about hostile behaviors than stupid ones.

Re: Show HN: Claude Composer

#62
post #57

Am I the only person who just runs claude code in yolo mode? Curious about these tools for fine-grained permission, did you get burned in a bad way? I think I'm going to trigger half of hacker news with this, but honestly nothing claude does on my machine seems particularly scary, and it's way too far from AGI for me to worry about hostile takeover right now =P

Honest question: What could it do to your machine if it went crazy? I've not used Claude Code yet.

Anything you can think of, but IIRC it asks you if it can perform a particular command (you can tell it to remember that it can or something like that).

Re: Show HN: Claude Composer

#63

Am I the only person who just runs claude code in yolo mode? Curious about these tools for fine-grained permission, did you get burned in a bad way? I think I'm going to trigger half of hacker news with this, but honestly nothing claude does on my machine seems particularly scary, and it's way too far from AGI for me to worry about hostile takeover right now =P

"Scary" doesn't need to mean Skynet taking over, it could just mean that Claude decides to yolo install a library with malware in it.

Re: Show HN: Claude Composer

#64
post #57

Am I the only person who just runs claude code in yolo mode? Curious about these tools for fine-grained permission, did you get burned in a bad way? I think I'm going to trigger half of hacker news with this, but honestly nothing claude does on my machine seems particularly scary, and it's way too far from AGI for me to worry about hostile takeover right now =P

Honest question: What could it do to your machine if it went crazy? I've not used Claude Code yet.

Literally anything a terminal command can do to your machine. Delete things, install malware, send your data to the FBI, start a fire by overheating (ok, now I'm just kidding... or not)

Re: Show HN: Claude Composer

#65
post #24

You’re going to be hearing from Anthropic’s legal department very, very soon if you use this name.

We'll see. Happy to change it up if need be. I'd rather beg for forgiveness than permission. <3

TBH I think it's misleading, as I assumed it was an Anthropic product until seeing the repo owner. For ethical reasons, I think you should change it.

Re: Show HN: Claude Composer

#66
post #13

Add a 5 hour timer so that us with MAX subs can know when to come back to our Opus work. I like it. thanks for the effort.

I was thinking that on this, folks need a cron task to run a trivial prompt at 5-6am and get that 5hr timer running so that it the majority of the quota is available in the working day morning, and then a new 5hr block starts around lunch time. This should maximise use of included tokens by a standard work day spanning 3 blocks rather than 2

Also useful for paid APIs like DeepSeek's, where they have cheaper inference price (50%/75% off) for UTC 16:30-00:30, so being able to schedule some stuff you know would take a ton of tokens for that time period would make sense.

Re: Show HN: Claude Composer

#67

Earlier quoted context omitted.

We'll see. Happy to change it up if need be. I'd rather beg for forgiveness than permission. <3

TBH I think it's misleading, as I assumed it was an Anthropic product until seeing the repo owner. For ethical reasons, I think you should change it.

Yeah I mean ignoring the legal risks, naming something "$Company-name $Tool" is begging to have it confused with an official product from $Company-name. Even if you don't care about the legal risks, at least care about your users not being confused about who made the thing.

Re: Show HN: Claude Composer

#68

I suggest a video on the README and breaking up that entire README into docs because it's too much content, then writing a much shorter README that gives people the answer they want coming into the page

As a heavy Claude user, I’ve seen many examples of what it will produce as a README, and they all look exactly like this. It definitely could use some editing!

I love Claude Code but I am extremely sick of slop readmes. Every time I notice I'm reading LLM output as a readme I feel punched in the gut. I didn't notice it with this project though.

Re: Show HN: Claude Composer

#69

Am I the only person who just runs claude code in yolo mode? Curious about these tools for fine-grained permission, did you get burned in a bad way? I think I'm going to trigger half of hacker news with this, but honestly nothing claude does on my machine seems particularly scary, and it's way too far from AGI for me to worry about hostile takeover right now =P

Personally yes I do run it in yolo mode. And I think, to the extent anyone will use this project, people mostly won't be using the fine grained control. For me toolsets and full yolo are what is useful in this project.

I think the real use cases are something like:

1. Try cautious mode, gain confidence, switch to yolo 2. Use yolo mode and find that it keeps doing something that annoys or scares you so you configure an exception for it

On number 2 I thought I would use it this way to prevent some unwanted behavior but I ended up learning how to avoid those behaviors in other ways.

Re: Show HN: Claude Composer

#70

Am I the only person who just runs claude code in yolo mode? Curious about these tools for fine-grained permission, did you get burned in a bad way? I think I'm going to trigger half of hacker news with this, but honestly nothing claude does on my machine seems particularly scary, and it's way too far from AGI for me to worry about hostile takeover right now =P

Personally yes I do run it in yolo mode. And I think, to the extent anyone will use this project, people mostly won't be using the fine grained control. For me toolsets and full yolo are what is useful in this project. I think the real use cases are something like: 1. Try cautious mode, gain confidence, switch to yolo 2. Use yolo mode and find that it keeps doing something that annoys or scares you so you configure a…

I think if I end up not finding a real person (or myself) using them I'll ax it. It would take some heft off the project. Maybe just yolo OR cautious and call it day.
Post reply on HN