Document billing usage and CLI empty-output recovery

[charlesrhoward]

Summary

• explain that each settled model call is charged and code-review usage is identified by repository and PR
• explain display rounding, exact ledger precision, reconciliation timing, and invoice behavior
• document safe CLI recovery when a model returns no output
• add the symptom and recovery path to Support

Validation

• pnpm lint
• pnpm types:check
• pnpm build
• Simplified Technical English copy check

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
mogplex-docs	Ready	Preview	Aug 18, 2026 7:36pm

[mogplex]

Mogplex PR Review

Status: No material issues found

Summary

Documentation-only PR covering two topics: billing usage transparency and CLI empty-output recovery. Three files changed, all additions, no deletions.

What was added

plans-and-billing.mdx — Two additions: (1) in the "Hosted usage rates" section, explains that each model call appears after cost settlement, shows repository and PR number for code reviews, rounds display to nearest cent, keeps ledger precision to 8 decimal places, and can take up to 10 minutes to appear. (2) In the "Payment methods and invoices" section, clarifies that usage charges appear in "Recent usage costs" and do not produce Stripe invoices — they spend existing credit.

cli/quickstart.mdx — New bullet in "Common first-run issues" for when a run reports the model returned no output. Guidance: open /model, choose another model, retry. Notes that Mogplex doesn't retry automatically to avoid added cost.

support.mdx — New row in the symptom table for "CLI says that the model returned no output" with the same recovery guidance.

Consistency check

The no-retry behavior is described consistently in both the quickstart ("Mogplex does not retry an empty response because the retry can add cost") and the support table ("The CLI stops before an automatic retry can add cost"). Both convey the same design decision from slightly different angles, which is appropriate for their respective audiences.

Minor observation

In the support.mdx symptom table, every other row in the "Start here" column contains links to documentation pages. The new row contains inline action instructions with no links. This is arguably the right format for this symptom (the resolution is a CLI action, not reading a doc), but if you want to be consistent, you could add a cross-reference to the quickstart's "Common first-run issues" section alongside the inline text.

Verdict

Approve-ready. No issues found.

View check run