|
|
|
|
|
|
by slipheen
32 days ago
|
|
|
I'm not sure I understand the intention here- 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? |
|
|
They say they want to do it due to their percieved misuse(via automation) of `claude -p`, this I find laughable because they can always rate limit based on how fast a human types/STT's into a text box. Heck, they could provide TUI based extensions(something you vibe code in a few days today) to get better observability and DX for harness use, I would not mind using `claude` CLI directly, but they wont.
Forcing people to using their garbage harness — 0 observability, no extensibility and poor DX — is a showcase of how this fiasco is playing out: They refuse to improve their CLI and want to push everyone to use their API with multiple poorly rolled out policies.