Skip to content

docs: update scheduler cost tracking and LLM provider aliases (fixes #807)#812

Merged
MervinPraison merged 1 commit into
mainfrom
claude/issue-807-20260623-1135
Jun 23, 2026
Merged

docs: update scheduler cost tracking and LLM provider aliases (fixes #807)#812
MervinPraison merged 1 commit into
mainfrom
claude/issue-807-20260623-1135

Conversation

@MervinPraison

Copy link
Copy Markdown
Owner

Summary

  • Replace outdated total_cost += ~$0.0001 Mermaid nodes in async-agent-scheduler.mdx and async-scheduler.mdx with the real ModelPricing cost flow introduced in PR #2171
  • Add <Note> callouts explaining the before/after behavior for cost tracking in both scheduler feature docs
  • Update Budget Control accordions to accurately reflect per-token spend
  • Replace sample log lines in scheduler.mdx (Estimated cost this run: $0.0001) with the real Run cost: $X (model=..., in=..., out=...) format
  • Add Safety Features <Note> in scheduler.mdx about --max-cost accuracy
  • Add ## Scheduler Integration H2 section to cost-tracking.mdx showing how ModelPricing/DEFAULT_PRICING connects to the scheduler max_cost brake
  • Append alias verification note to custom-provider.mdx confirming oai/claude/gemini/google_genai now resolve correctly

Fixes #807

Generated with Claude Code

…807)

- Replace fake $0.0001 cost constant in Mermaid diagrams with real
  ModelPricing flow in async-agent-scheduler.mdx and async-scheduler.mdx
- Add Note callouts explaining PR #2171 real cost tracking behavior
- Update Budget Control accordions to reflect accurate per-token spend
- Replace sample log lines in scheduler.mdx with real Run cost format
- Add Safety Features Note in scheduler.mdx about --max-cost accuracy
- Add Scheduler Integration H2 section to cost-tracking.mdx
- Append alias verification note to custom-provider.mdx Note block

Co-authored-by: Mervin Praison <MervinPraison@users.noreply.github.com>
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@MervinPraison, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 17 minutes and 56 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d2227f00-e7e4-4ec1-8273-fce907643323

📥 Commits

Reviewing files that changed from the base of the PR and between e201d44 and 57b7e6c.

📒 Files selected for processing (5)
  • docs/cli/cost-tracking.mdx
  • docs/cli/scheduler.mdx
  • docs/features/async-agent-scheduler.mdx
  • docs/features/async-scheduler.mdx
  • docs/models/custom-provider.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/issue-807-20260623-1135

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request updates the documentation across several files to reflect real cost tracking and pricing features introduced in PR #2171, including how AgentScheduler and AsyncAgentScheduler calculate per-token spend and how to register custom models. It also documents provider alias registration fixes. The feedback suggests a minor phrasing improvement in docs/cli/cost-tracking.mdx to make the explanation of cost tracking clearer.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.


## Scheduler Integration

`AgentScheduler` and `AsyncAgentScheduler` price every run through `ModelPricing` (since [PR #2171](https://github.com/MervinPraison/PraisonAI/pull/2171)). Any model you register here becomes spendable from the scheduler's `max_cost` brake:

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The phrase "becomes spendable from" is slightly awkward. Using "is tracked against" is more idiomatic and clearer for readers.

`AgentScheduler` and `AsyncAgentScheduler` price every run through `ModelPricing` (since [PR #2171](https://github.com/MervinPraison/PraisonAI/pull/2171)). Any model you register here is tracked against the scheduler's `max_cost` brake:

@mintlify

mintlify Bot commented Jun 23, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
praisonai 🟢 Ready View Preview Jun 23, 2026, 11:58 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@MervinPraison MervinPraison merged commit 9ed3747 into main Jun 23, 2026
18 checks passed
@MervinPraison MervinPraison deleted the claude/issue-807-20260623-1135 branch June 23, 2026 12:21
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 update: real scheduler cost tracking + live LLM provider aliases (PR #2171)

1 participant