These Twitter/X links are killing me, especially when they don't work with XCancel which seems to be happening more frequently. This one just gave me a summary by Grok, and I have no idea now if I'm seeing the same thing that others are commenting on.
Agreed. All I see is a grok summary of a lot of X posts. The original link is not suitable. Anyone have a link to a proper announcement?
Claude subscription changes coverage of `claude -p`
51–60 of 62 posts
Re: Claude subscription changes coverage of `claude -p`
#52It's a bit disheartening that this is generating so little discussion (this thread seems to be the one with the most comments, currently at 8). 99% of my max plan usage is non-interactive, and this post-June 15 pricing will far, far exceed what I can afford. I assume this applies to a great deal of us.
It's not bad at all. You get $200 in monthly extra usage credits. Unless you are a deeply unprofitable user this change is no big deal.
I assume that with API pricing it will run out in the first week and I might as well unsubscribe.
Re: Claude subscription changes coverage of `claude -p`
#53Earlier quoted context omitted.
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
Sure, 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.
The Pro plan is barely enough for this after the doubling of usage limits.
Re: Claude subscription changes coverage of `claude -p`
#54Considering what kind of fuckups happened up until now everytime Anthropic vibe codes a horrible anti-automation "fix" (like billing extra usage just because the string "hermes" exists somewhere in the prompt), this will get funny/horrible really fast. After all, you can very easily script tmux to use Claude Code "interactively".
What crazy shenanigans are gonna happen? Are people that type too fast, or people that copy paste too much, or people that output to markdown/json too often going to wake up to a 800$ extra usage bill or a banned account?
Re: Claude subscription changes coverage of `claude -p`
#55It's a bit disheartening that this is generating so little discussion (this thread seems to be the one with the most comments, currently at 8). 99% of my max plan usage is non-interactive, and this post-June 15 pricing will far, far exceed what I can afford. I assume this applies to a great deal of us.
It's not bad at all. You get $200 in monthly extra usage credits. Unless you are a deeply unprofitable user this change is no big deal.
Well..........
That was the point of the subscription. It gave you extremely discounted pricing, in exchange for recurring revenue.
For a normal subscription user, they would get multiple X of what they would if paying on-demand usage.
Re: Claude subscription changes coverage of `claude -p`
#56These Twitter/X links are killing me, especially when they don't work with XCancel which seems to be happening more frequently. This one just gave me a summary by Grok, and I have no idea now if I'm seeing the same thing that others are commenting on.
Agreed. All I see is a grok summary of a lot of X posts. The original link is not suitable. Anyone have a link to a proper announcement?
Re: Claude subscription changes coverage of `claude -p`
#57Before the doomers come in, you get $200 in API credits every month for claude -p usage. Usage counts against those API credits. This is a nothing burger.
$200 of on-demand usage credits is much, much, much less than what they were getting with $200 subscription.
Maybe "good," maybe "bad," but definitely, definitely not a nothing burger.
Re: Claude subscription changes coverage of `claude -p`
#58It's a bit disheartening that this is generating so little discussion (this thread seems to be the one with the most comments, currently at 8). 99% of my max plan usage is non-interactive, and this post-June 15 pricing will far, far exceed what I can afford. I assume this applies to a great deal of us.
Yeah, it's a pretty wild change. It's one thing for Anthropic to ban subscription usage of OpenCode etc of their backend. It's another thing to use their tools and still not get the full usage. Claude's recent one 9 of uptime [1] might have something to do with it. [1] https://status.claude.com/
Re: Claude subscription changes coverage of `claude -p`
#59I mostly get this change from their side except for the extremely misleading framing. I think in response to this change, I might write an open-source Claude Code GUI wrapper to wrap over the TUI and allow accessing it from a GUI interface. Still interactive (conforms to spirit of Anthropic's new rule), and runs Claude Code via the actual CLI (conforms to letter of Anthropic's rule), without even using the JSON outpu…
I'd really love a proper CC GUI myself. > Tradeoffs [...] Sounds like you're thinking of scraping the raw terminal output. Consider using a terminal library (pyte[0] comes to mind) for interaction and processing the session files for tool use data, etc. [0] https://pyte.readthedocs.io/en/latest/
Also I managed to get a VSCode Claude Code wrapper working last night. It launches instances of browser-based VSCode (via Coder's code-server) with Claude Code plugin pre-installed, then hides all toolbars and opens the CC window using another bundled custom plugin. Still have a few integration problems to solve, but in theory this should be perfectly allowed by Anthropic, give you a pretty good UI, and still allow integration into an agent orchestrator using hooks/session files to get the agent data.