Repository navigation
💡 Live Cost Meter & Avatar-Spoken Budget Guardrails (BYOK Transparency) #69
Replies: 1 comment
Weekly UpdateWhat ChangedClaude Cowork usage limits are now the #1 complaint in user reviews, providing strong market validation for this idea. Key new signals since this idea was created (April 7):
Updated Assessment
RecommendationAdvance — promote to architectural requirement. The cost tracking data pipeline (extracting usage metadata from each API response) should be designed into the Sources: Claude Cowork Review (Intelligence & Power), Claude Cowork Review (LowCode), Claude Cowork Limits (VibeCoding), ChatGPT Voice Launch (Fortune) |
Uh oh!
There was an error while loading. Please reload this page.
Summary
Surface real-time token spend, per-tool cost breakdowns, and a hard budget cap directly in the avatar UI — with the avatar verbally narrating cost milestones ("That last research turn cost about 12 cents — we're at $0.43 of your $2 session budget"). BYOK users currently fly blind: they pay Anthropic directly but have no in-app visibility into what each agentic loop is actually costing them, which is the #1 friction point for non-technical users adopting agentic workflows.
Market Signal
The Claude Agent SDK now ships a
max_budget_usdparameter that hard-caps spend per session, plus first-class cost/usage tracking APIs (Python v0.1.48 / TS v0.2.71, March 2026). Anthropic explicitly documents cost tracking as a primary SDK concern. Meanwhile, every BYOK competitor (Cursor, Continue, Windsurf) is being criticized in dev forums for opaque billing — Cursor shifted to a usage-based pricing model in 2025 specifically because users demanded cost transparency. None of these tools surface cost in a way Sarah (PM/analyst persona) can act on mid-session.User Signal
No direct user feedback exists yet (project pre-launch), but the PRD's Sarah persona is non-technical and explicitly cost-sensitive — a single runaway agentic loop on Opus could cost more than her monthly SaaS budget. The lack of an in-product cost ceiling is a known adoption blocker for BYOK in non-technical segments. Existing Discussion #55 (Effort Modes) hints at this concern but addresses model selection, not live spend visibility.
Technical Opportunity
The Claude Agent SDK exposes token usage on every message and supports
max_budget_usdnatively. TheAgentBackendport insrc/main/agent/is the natural seam — wrap the SDK adapter to emit cost domain events through the existingDomainEventBus, persist them in the audit repository, and bridge them to the renderer via theagent:*IPC namespace. The avatar's existing TTS pipeline (renderer/speech/) already supports interrupt-driven utterances, so cost narration can ride the same channel as agent responses without a new subsystem. A simpleBudgetPolicyvalue object inshared/types/domain/keeps the limit logic testable.Assessment
Adversarial Review
Strongest objection: "Cost narration is annoying noise — users will mute it within a day, and the cost meter is just a number that no one looks at."
Rebuttal: Narration should be opt-in and budget-threshold-driven (only speaks at 50%/80%/100%), not a constant nag. The real value is the hard cap —
max_budget_usdmakes it impossible for an agent loop to silently burn $50, which is the actual fear. The visible meter is secondary; the budget guardrail is the load-bearing feature. This also unlocks per-workflow ROI conversations Sarah can take to her manager ("this saved me 3 hours and cost $0.40").Suggested Next Step
Create a product brief for "BYOK Cost Transparency v1": scope the
BudgetPolicydomain object, theagent:cost-updateIPC event, the threshold-based avatar narration, and a minimal cost panel in the overlay. Spike on the SDK'smax_budget_usdbehavior under streaming to confirm partial-message cost emission.Proposed by the BMAD Analyst (Mary) on 2026-04-07.
Workflow run
All reactions