Skip to content

docs(console): describe Go usage as a shared allowance - #61406

Closed
Antonio-Faure wants to merge 4 commits into
anomalyco:devfrom
Antonio-Faure:go-usage-docs
Closed

Antonio-Faure wants to merge 4 commits into
anomalyco:devfrom
Antonio-Faure:go-usage-docs

Conversation

@Antonio-Faure

@Antonio-Faure Antonio-Faure commented Nov 3, 2026 •

Copy link
Copy Markdown

Issue for this PR

Fixes #60311

Type of change

  • Documentation

What does this PR do?

The Go page said each model had its own 5-hour, weekly and monthly limits. The service actually enforces one workspace-wide allowance across all paid models, with each model's monthly limit weighting how heavily its usage counts. This updates the wording to match the behaviour and the Console gauges.

How did you verify your code works?

Docs-only. I checked the changed paragraph against the behaviour described in #60311 and the three workspace-wide counters in Console → Go. No code or generated files changed.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

Added by the opencode bot (AI-generated).

Related: #57197


Recreated after the source fork was deleted; original PR: #60951

@opencodejr opencodejr Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. The new wording matches the shared, weighted allowance described in #60311 and support's statement quoted in #54875. I checked the new claims against the rest of the page: the Go Teams per-member allowance matches the plan table and the setup section, and the $1 → $4 example works out with the Go table's $15 and $60 limits. Docs-only, so there was nothing to run.

Public API: unchanged.

No blocking concerns.

Related: #57197

The Go page said each model had its own 5-hour, weekly and monthly limits. The service enforces one workspace-wide allowance across all paid models, with each model's monthly limit weighting how heavily its usage counts.
Clarify that the allowance is shared across models but not across Go Teams members, note that the estimates assume one model, and spell out the weighting and the block behaviour.
Make explicit that the Monthly limit column is a weighting for the shared allowance, not a separate per-model budget.

@opencodejr opencodejr Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new commits only rebase this onto the latest dev, which moved the file to services/site/. The text is unchanged from what I reviewed before. The pricing tables on the new base still match the worked example. Docs-only, so there was nothing to run.

Public API: unchanged.

No concerns.

@Antonio-Faure

Copy link
Copy Markdown
Author

Rebased onto current dev; checks are green and the PR is mergeable. Ready for review.

@vaprdev vaprdev closed this Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: Go usage limits are shared across all models, not per-model as documented

2 participants