| ▲ | avaer 10 hours ago |
| You'd be playing cat and mouse like yt-dlp, but there's probably more value to this code than just a temporary way to milk claude subscriptions. |
|
| ▲ | esperent 8 hours ago | parent | next [-] |
| If you're using a claude subscription you'd just use claude code. The real value here will be in using other cheap models with the cc harness. |
| |
| ▲ | somehnguy 5 hours ago | parent | next [-] | | I have no interest in Claude Code as a harness, only their models. I'm used to OpenCode at this point and don't want to switch to a proprietary harness. | |
| ▲ | jen20 2 hours ago | parent | prev | next [-] | | You can already do that though? [1] [1]: https://docs.ollama.com/integrations/claude-code | |
| ▲ | raincole 5 hours ago | parent | prev [-] | | Lol what? There is no value. OpenCode and Pi and more exist. Arguably Claude Code is the worst client on the market. People use Claude Code not because it's some amazing software. It's to access Opus at a discounted rate. |
|
|
| ▲ | stingraycharles 9 hours ago | parent | prev [-] |
| I don’t think that’s a good comparison. There isn’t anything preventing Anthropic from, say, detecting whether the user is using the exact same system prompt and tool definition as Claude Code and call it a day. Will make developing other apps nearly impossible. It’s a dynamic, subscription based service, not a static asset like a video. |
| |
| ▲ | falcor84 5 hours ago | parent [-] | | > detecting whether the user is using the exact same system prompt and tool definition as Claude Code Why would it be the exact same one? Now that we have the code, it's trivial to have it randomize the prompt a bit on different requests. |
|