yup :)

i'm doing opencode <-> openrouter <-> official deepseek api (i don't get the opencode hate, i like it)

how are you doing it?

am also using Kimi K3 via kimi-code

and also GLM 5.2 via ZCode

happy with all three, they're trailing frontier but i figure if i'm running GNU/Linux then i ought to favour open weights models with my €s -- reduced my usage of claude/gpt to the ~$20 tier just to keep abreast of claude_code/codex developments

▲

literallyroy 5 hours ago | parent [-]

> i don't get the opencode hate, i like it

When the company I work for was evaluating it, there were multiple rough points. Their terms and conditions allowed training on prompts, the default behavior was to route prompts to their servers for conversation summary/labeling. One of their lead maintainers is also super toxic on many issues.

Sorry this is all baseless with no links, I’m on my phone and locating those issues again isn’t something I have time for.

It’s a good tool I just don’t like the privacy policies nor maintainers attitudes.

	▲	HDBaseT 5 minutes ago \| parent [-]
		1. The privacy policy was a bit misleading, but it has since been updated to reflect the exact state of things. [1]. For example, DeepSeek models have ZDR, although their ZDR contract is renewed monthly. It COULD change. You need to toggle a Setting in your account to use DS. 2. At one point (apparently) summary and title generations were handled by Grok. This has changed, by default it uses your 'small_model' configured in your config. By default, it will use a cheap model provided by your provider. E.g. if you have ChatGPT API connected, it will use the cheapest ChatGPT model. OpenRouter users MAY see it routed to a free model however. [2] [3] [1] - https://opencode.ai/docs/go/#privacy [2] - https://github.com/anomalyco/opencode/blob/9b805e1cc4ba4a984... [3] - https://opencode.ai/docs/config/