ES version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
100% Positive
Analyzed from 268 words in the discussion.
Trending Topics
#claude#code#using#same#understand#don#more#agents#sdk#technical

Discussion (7 Comments)Read Original on HackerNews
One of the technical things I don't really understand, is that it is not that hard to have an agent use tmux/etc to type into Claude code directly if you really want to? Like using tmux vs Claude -p are effectively the same aren't they?
Like, I understand the way they are subsidizing or whatever but on a technical level, I don't see how this makes any meaningful difference?
Am I missing something? Is this more about policy than the specific way it is invoked?
The credit doesn’t apply to:
Interactive Claude Code in the terminal or IDE
Claude conversations on the web, desktop, or mobile apps
Claude Cowork
Other features that draw from extra usage
------------
Next month, interactive claude code will no longer be allowed.
On the bright side, at least we finally have some clear communication around using the agents SDK. I wonder if this in turn will cause more people to build custom agents on top of the SDK or if more people will move off it completely.
These seem like not the same thing and it seems silly to bill them the same way but differently than using the CLI or official app.
(Not that I don't blame them)