Vibeleaderboard
← All Intel
Intel / post

Cutting GitHub rate-limit use 75% in an agent PR watcher

Source
x.com
Date

I have spent far too much time on the Github integrations in T3 Code the last few days. Cut rate limit usage by over 75% and made monitoring behaviors much more reliable. Julius moved us off the CLI for API calls we can do more efficiently directly. We rotate between the GQL and rest APIs depending on which uses your rate limits most efficiently (with fallbacks). This was a ton of work that will largely go unnoticed, but it's the type of stuff I love. Had to do like 30 implementations of the PR watcher before I got it to a good spot. On one hand, I'm thankful the details can be seen by those who dig into the source code. On the other, feels weird that everyone else will just copy our work and never have to think so much about this.

Why it matters

tools that poll GitHub burn rate limits. Calling APIs directly and alternating GraphQL and REST by cost cut usage over 75% and made PR monitoring more reliable.

Terms in this piece · Glossary
  • AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
More from Theo - t3.gg
Recommended reads
Comments

Checking sign-in…

Loading comments…