anomalyco / anomalyco/opencode
[Question] Policy on third-party open-source apps using Zen free-tier models
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Hi opencode team — we're building a free IT assistant tool: a non-commercial, open-source (MIT-planned) Windows maintenance
assistant for office workers with no IT skills (adware cleanup, startup optimization, troubleshooting guidance).
TL;DR: we'd like to offer Zen free-tier models as our zero-config default, and to vendor your @opencode-ai/llm engine package
(MIT) as our LLM request layer. Before doing either, we want your explicit blessing.
Questions:
- Is third-party open-source use of the Zen free tier permitted under your ToS, with or without restrictions (rate limits,
attribution, specific User-Agent)? - If yes, is there a sanctioned way to identify our app (e.g. a dedicated header or UA string you would whitelist)?
- Are you comfortable with us vendoring @opencode-ai/llm in this way? Any requests beyond the MIT license terms (attribution
wording, a note that we're unaffiliated, etc.)? - If the free tier is off-limits for third parties, would a paid Zen API key be the recommended path for an app like ours?
We're happy to comply with whatever policy you set — attribution, linking to opencode, rate limiting, or staying out entirely.
Thanks for the great work on opencode.
Background & context (click to expand)
Who our users are. Office workers with no IT skills at all — when their PC slows down or gets hijacked by adware, they usually
just live with it, or fall for overpriced "PC cleaner" scams. We want to give them a trustworthy free tool that actually fixes
these problems, explained in plain language they can understand.
How we use LLMs. (a) intent classification and explaining diagnostic results in plain language; (b) reasoning about
troubleshooting approaches for problems our local knowledge base can't cover; (c) occasionally drafting short
analysis/remediation scripts (e.g. Python) to locate or fix an issue. Safety note: all consequential decisions are made by a
local deterministic rule engine, and every script or action goes through a mandatory user-confirmation gate with audit logging
before execution — the LLM never executes anything by itself.
What we observed. The free tier currently requires the x-opencode-session header (400 MissingSessionID, "OpenCode's free tier can
only be used in OpenCode"). We have NOT worked around this and won't: we would never ship the session-layer headers or present
ourselves as the opencode client — requests from our app would be honestly identified however you prefer.
Vendoring. @opencode-ai/llm is MIT licensed — thank you. If we vendor it, your copyright notice stays intact and our README will
carry clear attribution plus a note that we're unaffiliated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is identified; this is a maintainer policy question rather than a code change. Review the Zen free-tier terms and the MIT terms for @opencode-ai/llm, then document the permitted usage, identification requirements, and whether a paid API key is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100