Skip to content

Fix agent spend limits with BigInt stroops - #484

Open
chiemezie1 wants to merge 1 commit into
Stellar-Ecosystem:mainfrom
chiemezie1:fix/agent-bigint-spend-limits
Open

Fix agent spend limits with BigInt stroops#484
chiemezie1 wants to merge 1 commit into
Stellar-Ecosystem:mainfrom
chiemezie1:fix/agent-bigint-spend-limits

Conversation

@chiemezie1

Copy link
Copy Markdown

Fix agent spend limits with BigInt stroops

The BigInt-based spend-limit fix is now implemented, verified, committed, and pushed to the fork branch.

What changed

  • Replaced float-based USDC/stroop handling with precise BigInt arithmetic in agent.js
  • Added regression tests for exact-limit and one-stroop-over cases in agent.test.js

Verification

  • Ran the agent test suite:
    • 1 test file passed
    • 31 tests passed
    • 0 failed

Closes: #362

@drips-wave

drips-wave Bot commented Jul 29, 2026

Copy link
Copy Markdown

@chiemezie1 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@chiemezie1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 reviews.

How do review limits work?

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

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 20a53fba-5c25-4d5c-9926-91faa566f812

📥 Commits

Reviewing files that changed from the base of the PR and between a3fd824 and 28440cb.

📒 Files selected for processing (2)
  • agent/agent.js
  • agent/agent.test.js

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.

@ritik4ever

Copy link
Copy Markdown
Collaborator

Hi @chiemezie1,

This PR could not be merged because it has merge conflicts with the target branch.

Please resolve the merge conflicts, push the updated changes, and the PR can be reviewed and merged.

Thank you!

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.

Agent: AGENT_MAX_PER_TX default of '0.001' is parsed as a float

3 participants