Hacker Newsnew | past | comments | ask | show | jobs | submit | lherron's commentslogin

Are they also going to refund all the extra usage api $$$ people spent in the last month?

Also I don’t know how “improving our Code Review tool” is going to improve things going forward, two of the major issues were intentional choices. No code review is going to tell them to stop making poor and compromising decisions.


Even for all of us plan users, where we got barely any use from our plan because we'd destroy our 5h and 1w usage limits, also unlikely, after all they have an out of "your usage limits are guaranteed to be 5x of Pro users" (who are also being screwed).

Of course, all their vibe coding is being done with effectively infinite tokens, so...


this is one reason i will not pay for extra usage - it is an incentive for them to be inefficient, or at least to not spend any effort on improving my token usage efficiency.


No, they will not.


I stopped using it for nearly a month because of the performance degradation. I paid for the whole month. Wasted money.


It’s interesting to watch Ant try to ship every value-add product feature they can while they still have the SOTA model for agentic. When an open weights equivalent to Opus 4.5’s agentic capabilities comes out, I expect massive shifts of workloads away from Claude.

Don’t get me wrong, I think their business model is still solid and they will be able to sell every token they can generate for the next couple years. They just won’t be critical path for AI diffusion anymore, which will be good for all sides.


Reality is Ant can supply X tokens and they see demand for 10*X tokens. So they’ll charge whatever the top 10% of users are willing to pay, and slowly degrade the value of the subscriptions until everyone has moved to another supplier or migrated to the 10% price point. The draconian ToS that they sometimes enforce is their mechanism to degrade subscription value over time. Expect agent-sdk to be next on the chopping block, moving from oauth supported to api only. When they switch it they will rightly point out the docs never explicitly said it was allowed.


I think maybe you are not familiar with what /loop and the Claude cron tools do.

https://code.claude.com/docs/en/scheduled-tasks


I think maybe you still don’t understand that not everyone will max out their usage, regardless of the methods available.


People don't pay double the $100 account in fixed recurrent payments if they don't intend to use a lot more than they would use in the $100 subscription.

Perhaps people at Anthropic should ask Sonnet (or Kimi, it's much better value) how power laws and pareto distributions work? You are advertising for people who can justify a virtually unlimited amount of tokens, why is it surprising that they would use as many as you're offering them in the plan?

PS: interesting that you'd use a throwaway account to post this


I need a hypothetical use case for things like this, I don't get how so many people have so much desire for use of features like this.


https://martinfowler.com/articles/harness-engineering.html it's being talked about everywhere.

If you manage developers or product folk, do you allow them to work when you're not looking over their shoulder? All developers can be managers/team leads now. You plan, you delegate, you review.

You're welcome to not do this, surely that's appropriate in quite a few areas of work, but many of us are because we can get more work done than if we we're micromanaging every line of code change. For startups, where a bit of quality can suffer in favor of finding market fit, this is huge.


The actual /loop and cron are beyond the normal "agentic loop"


I'm not sure what point you're trying to make. `claude remote` on a secure vm is basically all you need to operate a factory from your phone. I suspect a lot of people with your line of reasoning are stuck on human in the loop while awake level of AI use. Anthropic has no interest in that long term and all of their product moves validate that.


Every morning it summarizes a bunch of stuff for me, suggests me PRs to review, emails to reply to, freshly cloned any new repos, pulled all others, presents me with the suggested approaches to my PRs of that day, and gives me a list of my slack mentions that look more urgent.

This is just the morning ones, and saves shitloads of time of clicking around from tool to tool, freeing up time for the thinking and deciding.


Wow, you should probably ask it to write a script for 90+% of that instead . Sounds like a huge waste of electricity.


How? Most of what was mentioned requires discretion and judgment. You can question whether an LLM would be able to offer that, but there’s no script that can do b it.


Deduplicating/validating/processing incoming bug reports?


I was surprised the author didn’t mention Yegge’s list (or maybe I missed it in my skim).


Gross.


Somehow every 15 line shell script I write now turns into a 50kloc bun cli or tui app. Apparently there are many such cases.


Different use cases. I want aws-cli for scripting, repeated cases, and embedding those executions for very specific results. I want this for exploration and ad-hoc reviews.

Nobody is taking away the cli tool and you don't have to use this. There's no "turns into" here.


Oh I think you misinterpreted my comment! I am very much a fan of this, wasn't throwing shade. I am just remarking on how my side-project scope today dwarfs my side-project scope of a year or two ago.


I did :) and I from votes I'm guessing many others too. Text communication remains hard as usual, sorry about that :(


Terminal electron.


They buried the lede. The last half of the article with ways to ground your dev environment to reduce the most common issues should be its own article. (However implementing the proper techniques somewhat obviates the need for CodeRabbit, so guess it’s understandable.)


Why would the self-hosted runner fee be per-minute instead of per-job? I don’t get it.


I had the same question — I understand that the Actions control plane has costs on self-hosted runners that GitHub would like to recoup, but those costs are fixed per-job. Charging by the minute for the user’s own resources gives the impression that GitHub is actually trying to disincentivize third-party runners.


Self-hosted runner regularly communicates with the control plane, and control plane also needs to keep track of job status, logs, job summaries, etc.

8h job is definitely more expensive to them than a 1 minute one, but I'd guess that the actual reason is that this way they earn more money, and dissuade users from using a third party service instead of their own runners.


Might be an estimation of logs storage/bandwidth.


That's generous, but doesn't seem consistent with how Microsoft does business. Also, if that's the case why does self-hosted cost the same as the lowest hosted tier?


Because the competitor services that provide much cheaper hosted runners also charge per minute.

This isn't aimed at people actually self-hosting; it's aimed at alternative hosted runners providers. See this list

https://github.com/neysofu/awesome-github-actions-runners


Runner price based on CPU/memory and time makes sense, since those are the costs associated with executing runners.

The costs for GitHub doing action workflows (excluding running) is less related to job duration.

The most charitable interpretation is that per-minute pricing is easier to understand, especially if you already pay runners per minute.

The less charitable interpretation is that they charge that because they can, as they have the mindshare and network effect to keep you from changing.


or some other metric like how many logs your job produces and they have to process

the only rational outside rationale is this has the best financial projections, equitability with the customer be damned

gotta make up for those slumping ai sales somehow, amiright?


Freaking awesome. You should extend clicking on a link, similar to how this article describes infinite content:

https://worksonmymachine.ai/p/solving-amazons-infinite-shelf...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: