Issue cost: what an issue and its pulls spent

An issue's page and its terminal screen say what the issue cost: the dollars its own agent runs spent plus the dollars spent on every pull whose description closes it. It is for people who write to the repository and want to know what a piece of work cost before they look at the whole ledger.

Cost is the total. When a closing pull spent anything, This issue shows the issue's own runs and one Pull row per pull follows, with the pull number linking to the pull. With no runs of its own but a closing pull that spent something, the Runs card is left out and the cost rows stay.

Cost $0.75: this issue $0.50, #12 $0.25.

Rules

closesFromBody (src/core/pulls.ts), in any state: Closes #7 counts for #7 and not for #70. Runs are summed from run.cost_usd, in US dollars as recorded, rounded to a ten-thousandth.

up to more than the repository spent. The repository's total is the usage ledger's.

src/core/issue_cost.ts): the viewer must read the repository's runs, see the owner's facts (as the runs list hides cost from other readers), and be allowed to see the issue. A sealed pull the viewer may not see is left out of the sum. A guest sees nothing.

API and MCP

GET /api/v1/repos/:owner/:name/issues/:n and the MCP issue tool carry cost: {usd, own, pulls: [{number, usd}]}, the number the page prints, from issueCostFor. The field is absent when nothing was spent, for a guest, and for a viewer who may not read the runs or see the owner's facts.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs