Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Claude Composer

github.com

Post reply on HN
Print view View original

11–20 of 99 posts

Re: Show HN: Claude Composer

#11

Post by gdudeman »

mikebannister wrote: post #5
BugsJustFindMe wrote: post #4

I read the description of what this is (nb. maybe move that to the top instead of the middle of the page?), and I don't think I understand what problem it solves. > Reduced interruptions: Automatically handles permission dialogs based on configurable rules Why? Claude Code already gives you the option to accept requests permanently going forward. The cost of configuring rules is worse than the cost of just telling Cl…

> Why? I have a lot of different projects, scenarios, and edge cases where it's helpful to me. I think you will find that if you're interactive mode there will always be some dialogs to dismiss, especially if you're jumping around a lot of different projects, etc. So for me the goals are somewhere at the intersection of the interactive mode and unattended operation. It depends what your goals are for sure. TBH I use…

You may be able to do this with a user-based settings file, so you can have a base layer of settings across all projects. More on how to do that here: https://docs.anthropic.com/en/docs/claude-code/settings

Re: Show HN: Claude Composer

#12

Post by serf »

BugsJustFindMe wrote: post #4

I read the description of what this is (nb. maybe move that to the top instead of the middle of the page?), and I don't think I understand what problem it solves. > Reduced interruptions: Automatically handles permission dialogs based on configurable rules Why? Claude Code already gives you the option to accept requests permanently going forward. The cost of configuring rules is worse than the cost of just telling Cl…

>Why? Claude Code already gives you the option to accept requests permanently going forward. The cost of configuring rules is worse than the cost of just telling Claude Code "yes and you don't need to ask again".

want to see this mode fail catastrophically? write enough CLI stuff w/ python w/ powershell or wsl or some other 'leaky' cli. It will eventually fail a command and then try to pipe a shell command through the python interpreter or a specific PS incantation.

This means that you now need to approve 'git' , and 'python sh git' and 'powershell.exe git' and 'wsl.exe ubuntu git' as separate and independent commands. (I dont remember the shell incantation command so excuse the pseudocode).

That means that for the entire gambit of approvals needed for continued permission for a singular task might be 4x greater than normal -- probably more given that claude is aware of so many different ways to pipe to shell..

Re: Show HN: Claude Composer

#14

Post by bckr »

serf wrote: post #12
BugsJustFindMe wrote: post #4

I read the description of what this is (nb. maybe move that to the top instead of the middle of the page?), and I don't think I understand what problem it solves. > Reduced interruptions: Automatically handles permission dialogs based on configurable rules Why? Claude Code already gives you the option to accept requests permanently going forward. The cost of configuring rules is worse than the cost of just telling Cl…

>Why? Claude Code already gives you the option to accept requests permanently going forward. The cost of configuring rules is worse than the cost of just telling Claude Code "yes and you don't need to ask again". want to see this mode fail catastrophically? write enough CLI stuff w/ python w/ powershell or wsl or some other 'leaky' cli. It will eventually fail a command and then try to pipe a shell command through th…

Claude has been adding PYTHONPATH to test commands, and for some reason, the “don’t ask again” doesn’t stick for these types of commands. So I’ve been trying to get it to use make commands, which can modify the environment, and don’t trigger the same permission issues. Just now I finally put it in CLAUDE.md “always use make commands to run tests”. Haven’t seen yet whether it will stick.

Re: Show HN: Claude Composer

#15

Post by mikebannister »

bckr wrote: post #14
serf wrote: post #12

Earlier quoted context omitted.

>Why? Claude Code already gives you the option to accept requests permanently going forward. The cost of configuring rules is worse than the cost of just telling Claude Code "yes and you don't need to ask again". want to see this mode fail catastrophically? write enough CLI stuff w/ python w/ powershell or wsl or some other 'leaky' cli. It will eventually fail a command and then try to pipe a shell command through th…

Claude has been adding PYTHONPATH to test commands, and for some reason, the “don’t ask again” doesn’t stick for these types of commands. So I’ve been trying to get it to use make commands, which can modify the environment, and don’t trigger the same permission issues. Just now I finally put it in CLAUDE.md “always use make commands to run tests”. Haven’t seen yet whether it will stick.

I hate to be pessimistic but this is something that CC doesn't seem good at: forgetting the tools that it loves and using the ones you want it to. You might want to try "disallowing" that command(?) explicitly (in addition to adding to CLAUDE.md and/or prompt).

I'm not sure what command is being called to set PYTHONPATH. If my assumption that it relates to a specific command is incorrect the above probably isn't helpful.

Good luck!

Re: Show HN: Claude Composer

#16

Post by caleblloyd »

serf wrote: 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.

Thinking of switching from API access to Max 20x tomorrow for a more consistent bill.

Been using $50-100 of Opus tokens through API access per day. Think I’ll hit the Max 20x limits and get put in timeout?

I wish Max could automatically overflow to API access when it times out so I would need to have token anxiety.

Re: Show HN: Claude Composer

#17

Post by Syzygies »

caleblloyd wrote: post #16
serf wrote: 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.

Thinking of switching from API access to Max 20x tomorrow for a more consistent bill. Been using $50-100 of Opus tokens through API access per day. Think I’ll hit the Max 20x limits and get put in timeout? I wish Max could automatically overflow to API access when it times out so I would need to have token anxiety.

I moved to Max after projecting a $2,000 annual API bill. I haven't yet hit five hour limits, but login/ toggles easily between plans. I believe the interface tells you when you've hit a limit, but as I said I don't know first hand.

Re: Show HN: Claude Composer

#18

Post by SatvikBeri »

caleblloyd wrote: post #16
serf wrote: 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.

Thinking of switching from API access to Max 20x tomorrow for a more consistent bill. Been using $50-100 of Opus tokens through API access per day. Think I’ll hit the Max 20x limits and get put in timeout? I wish Max could automatically overflow to API access when it times out so I would need to have token anxiety.

According to CCUsage, I hit limits on Opus usage around the equivalent of $150. If we naively extrapolate, that suggests about $600 of Opus usage per session on Max 20x.
Post reply on HN