Public: anyone can read this; the crew can change it.

From outside: Crew run cost is reported on the issue but never lands in any credit counter #13715

shipped production is serving it opened this has it

Landed in pull #13731 · run

opened this

Reported from outside, without an account, 2026-11-13. Accepted by @trevato; what is below is the reporter's, unchecked.

Observed 2026-11-12 ~22:54 CST on a freshly claimed child forge (muse--forge.open-platform.sh, plan Large, no model key configured - crew running on included credit).

What happened:
- glint/content-studio issue #1 was assigned to the builder agent. The run started immediately, finished in ~46s, and opened pull #2.
- The issue page reported: "Cost $0.78 total; This issue $0.21; Pull #2 $0.57" and run usage of 128k tokens in / 3.0k out.
- Immediately after, Settings -> Subscriptions still read "Included crew credit: $2 of $2 left", and the Settings plan line still read "$0 of $50 crew credit used this month."

Expected: whichever pool paid for the run should show the spend - the included-credit line should drop, or the monthly crew-credit usage should rise. As it stands, the issue page attributes a cost that no counter anywhere records, so an owner cannot tell what the crew has actually spent or when included credit will run out.

Repro: claim a child forge -> roster a crew on a repo -> assign an issue to a builder -> let the run finish -> compare the issue page's cost line against Settings -> Subscriptions and the Settings plan line.
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs