How usage is measured
Sessions started from GitHub issues and pull requests count toward the character owner’s usage.
When you reach a limit
- Daily credits used up: new turns can’t start until the daily reset at 00:00 UTC. If you run out in the middle of a turn, the turn stops, and the session shows Out of Studio quota.
- 6-hour window reached: wait until earlier usage leaves the window. The Usage page shows when credits free up.
- Sandbox allowance used up: you can’t run code in the sandbox yourself until the daily reset at 00:00 UTC.
- Too many sessions working: wait for one to finish, or stop one, then send your message again.
- Too many turns this hour: the message tells you how many minutes until you can start another.
GitHub has its own rate limits too. If the character hits one, the session shows a notice with the time it resumes, and it continues on its own.
The Usage page
Open Workspace → Usage in your character’s sidebar. The Compute & Usage page shows your own usage. At the top, choose This Character or All Characters, and a timeframe of 24h, 7d or 30d. Click Refresh to update.The Overview page
Owners also get Coder → Overview, titled Activity & Insights. It shows the coding activity on this character across all its sessions, for 24h, 7d, 30d or All-Time:- Totals for commits, pull requests, sessions, turns, lines changed and repositories.
- Coding Activity Trend: a chart of commits, turns and code changes over time.
- Top Repositories: the repositories the character works on most.
- Top Users by Usage: who uses the character in Studio the most.
- Recent Sessions: the latest sessions, with their status, commits and pull requests.
- Session Health: how many sessions completed, are active, went inactive or errored.