Skip to content

chore: bump goose backend pin to 2c02ed6f - #331

Merged
kalvinnchau merged 1 commit into
mainfrom
bump-goose-usage-updates
Sep 16, 2026
Merged

kalvinnchau merged 1 commit into
mainfrom
bump-goose-usage-updates

Conversation

@kalvinnchau

Copy link
Copy Markdown
Collaborator

Category: infrastructure
User Impact: Session token usage and cost now update live during an agent turn in Berd, instead of only when the turn finishes.
Problem: goosed only sent an ACP usage_update notification when a prompt turn completed, so Berd's context meter and token/cost display (and the auto-compact-before-send check) worked from a snapshot that could be a full turn stale.
Solution: Pin the Goose backend to 2c02ed6fcf6a91b435aacfd5d02d713db8862153, which picks up upstream aaif-goose/goose#12006fix(acp): send session usage updates after each provider call — emitting usage_update after every provider call mid-turn. No Berd-side changes needed; the notification handler already handles updates at arbitrary frequency.

File changes

goose-backend.lock.json
Bumped ref/commit from 616cdce9 to 2c02ed6f. The delta is two commits: the usage-update fix itself (crates/goose/src/acp/server.rs + tests) and f4e97c353, which only touches ui/desktop/** and is not part of the goose-cli package we build.

Upstream fix: aaif-goose/goose#12006

Pulls in fix(acp): send session usage updates after each provider call
(#12006), so Berd receives ACP usage_update notifications mid-turn
instead of only at end of turn. Includes an unrelated ui/desktop-only
commit (f4e97c353) that is not part of the goose-cli package we build.
@kalvinnchau
kalvinnchau requested a review from a team September 16, 2026 14:08
@kalvinnchau
kalvinnchau merged commit ce48ca5 into main Sep 16, 2026
16 of 17 checks passed
@kalvinnchau
kalvinnchau deleted the bump-goose-usage-updates branch September 16, 2026 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant