chore(crashlytics-autotriage): drop verbose, bump max-turns, pass app ID to prompt#93
Merged
Merged
Conversation
…to 40 The Firebase MCP server now connects and the Crashlytics tools load, so the temporary verbose logging is no longer needed (and it prints the full Claude execution). Also raise --max-turns 25 -> 40 so a slow/flaky Crashlytics API call doesn't exhaust the turn budget and fail the run before Claude can post its triage comment.
…y in the prompt google-services.json is gitignored (absent in CI), so Claude can't discover the app ID from the repo. Hardcode it in the prompt (app IDs aren't secret — they ship in the APK) so the Crashlytics tools are called immediately with the right app instead of burning turns searching.
stozo04
changed the title
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
1 participant
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.
Description
Post-breakthrough polish — the Firebase MCP server now connects and the Crashlytics tools load (run #7 onward). Three small changes:
show_full_output: "true"— it was only there to debug the MCP connection; it also dumps the full Claude execution to the run log.--max-turns25 → 40 — run chore: Bump targetSdk to API 36 (Android 16 Baklava) for Play Store compliance #7 hit the 25-turn cap (failing the run with exit 1) because Claude retried the then-404'd Crashlytics calls. With the Data API now enabled the loop shouldn't recur; the headroom keeps a slowcrashlytics_*call from exhausting the budget before Claude posts its comment.1:95815153197:android:c30254bb713d1e6ae96aa4) so Claude calls the Crashlytics tools immediately with the right app instead of searching the repo for it —google-services.jsonis gitignored and absent in CI, so the search can't succeed anyway. App IDs aren't secret (they ship in the APK), so no secret needed.Type of Change
How Has This Been Tested?
Checklist