anomalyco / anomalyco/opencode

docs(web): Better Transparency for OpenCode Go Documentation

Open
#43,651 1 comment 0 reactions 0 assignees View on GitHub

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, I love the app in general, love what you're doing but I feel like there could be some better transparency in the documentation with some things.

Usage Limits

  • I only found out recently some models only have a $15 per month usage limit and this is buried in the documentation. It would have been best to add a side note right at the top of https://opencode.ai/docs/go/#usage-limits so it's not hidden.
  • When I view my GO sub usage limits at https://opencode.ai/workspace/<WORK_SPACE_ID/go It shows the usage left based on the $15 per month model usage, not what I still have left for $60, which is confusing. You might want to show different charts for the different usage limits.

Model Training from Data

  • I only use paid models because I assume they don't train on my data. I had to Google Muse Spark 1.2 Contributor to find out that it trains on data. I think any paid model that trains on data should be clearly annotate

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Go documentation page at opencode.ai/docs/go/#usage-limits and the workspace Go usage page at opencode.ai/workspace/<WORK_SPACE_ID>/go. Review how the $15 and $60 limits and model data-training policies are currently presented. Done means the limits and training disclosures are clearly visible and the different usage limits are distinguishable.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.