Repository navigation
Conversation
analyze_issue_with_seer checks the organization's Seer credits before starting a run, and tells the user when a run stopped because the organization ran out of credits. get_issue_details shows the same reason. A failed credit check never blocks a run. Refs CW-2330
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
srest2021
changed the title
srest2021
marked this pull request as ready for review
November 5, 2026 22:05
Say auto-reload, which is what the billing settings call it, and point to someone with billing access, since MCP users can have any role. Refs CW-2330
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes CW-2330
analyze_issue_with_seernow checks the org's Seer credits before starting a new run (the credit check endpoint is feature-flagged). If there aren't enough credits, it says so and doesn't start the run.When a run stopped because the org ran out of credits (
failure_reason=out_of_credits), the tool andget_issue_detailsnow say why.If the credit check itself fails, the run starts anyway, since LLM proxy still stops a run that runs out of credits. We make a Sentry issue if there's a contract mismatch between the MCP and the credit check endpoint.