3 ms·
This is much of a something burger for users who actively use `claude -p` under their subscription. Users will have to do their own math, but that 200 could com
by ramoz 5mo ago
This is much of a something burger for users who actively use `claude -p` under their subscription. Users will have to do their own math, but that 200 could come and go quite fast and then you're hitting normal API rates versus what you had previously been hitting.
https://x.com/jeremyphoward/status/2054682882753597603?s=20 https://x.com/jeremyphoward/status/2054682882753597603?s=20
- solenoid0937 5mo agoSure, but if you spend that many tokens you're probably a pretty big net loss for the company anyways. No company will subsidize that level of compute for you indefinitely.
- ramoz 5mo agoYea that's fine and understandable. But like I said, this is something for those users. I launch many review processes locally with `claude -p`
- user34283 5mo agoNo. I just use claude -p to review some Codex output. The Pro plan is barely enough for this after the doubling of usage limits.