github / github/app

Show AI credit consumption per automation run

Open
#2,696 0 comments 0 reactions 0 assignees View on GitHub
triage
Dominant language
No language data
Stars
2.1k
Forks
153
PR merge metrics
No merged PRs in 30d

Description

### Feature summary

Surface AI credits (and token counts) consumed by each automation run in the GitHub Copilot app.

### What problem are you trying to solve?

Automations can be triggered frequently and run unattended, but the app does not show what an individual run consumed.

Run frequency is the main decision I have to make when setting up an automation, and cost per run is the input I need to make it. A run that costs 20 AI credits and a run that costs 400 AI credits imply completely different schedules. Today the only way to find out is to enable the automation, watch the total bill move, and reverse-engineer the per-run cost.

The practical result is that I under-use automations, because running them at a useful frequency feels like an unbounded financial risk.

### Proposed solution

- Show AI credits consumed for each run in the run detail view, alongside duration and status. Token counts per model would be a useful addition, but credits are the figure that maps to cost.
- Add a usage column to the automation's run history so runs can be compared at a glance.
- Show aggregate figures per automation: total and average credits per run over a selectable period (e.g. last 7/30 days), so the monthly cost of a given schedule can be projected.

### Workflow impact

Affects anyone running automations on a schedule or a frequent trigger, particularly individual users and small teams on usage-based billing where spend is directly visible.

With per-run cost visible, choosing a trigger frequency becomes an informed decision instead of a guess. It also makes it possible to spot an automation whose cost has drifted upward after a prompt or repository change.

### Installation context

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by locating the automation run detail, run history, and aggregate usage views and tracing the data available for each run. Done means per-run credits are visible, with optional token counts and selectable-period total and average figures.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
analytics, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.