Better error messaging when user hits daily usage cap

[brandonling27]

Problem

When a user hits their daily token/cost cap, Addie stops responding without explanation. This looks like a bug rather than an expected limit, causing confusion in the community.

Expected behavior

When a user hits their daily usage cap, they should receive a clear, human-readable message explaining:

• That they've reached their daily usage limit
• When the limit resets (e.g., "Usage resets in ~18 hours" or "back tomorrow")
• Optionally, what they can do in the meantime (e.g., upgrade tier for higher limits)

Current behavior

Addie goes silent. No error, no explanation. Users assume something is broken.

Suggested copy (example)

"You've hit your daily usage limit for Addie. You're all set to continue tomorrow when it resets. [Upgrade your membership] for higher limits."

References

• Related work: per-user Anthropic cap + dashboard (PRs feat(addie): per-user Anthropic cost cap (#2790) #2946, feat(cost-cap): wire remaining callers + fail-closed warn default (#2950) #2954, feat(admin): Addie cost-cap observability dashboard (#2945) #2961, feat(cost-cap): resolve real tier for authenticated callers (#2945 f/u) #2969)
• The cap and observability infra is shipped; this is a UX/messaging gap on the consumer side

[bokelley]

Triage

Outcome: Execute — root cause confirmed, fix implemented, PR open.

Root cause: processMessageStream yields a done event with flag_reason: 'cost_cap_exceeded' and the cap message in response.text. The done handler in handleUserMessage (bolt-app.ts) stores response but the subsequent streamer.stop() call had no markdown_text — the streamer buffer was empty because no text events are emitted for cap responses — so the user received silence.

Fix: PR #4922 — check flag_reason === 'cost_cap_exceeded' before streamer.stop(), run response.text through guardBareJsonEnvelope → validateOutput → wrapUrlsForSlack, and deliver it with blocks: [buildFeedbackBlock()]. Catch-block fallback updated to use cap text for the same case. Copy also updated: "You can try again in" (was "The cap resets in") and "AgenticAdvertising.org team" (was "AAO team").

---

Generated by Claude Code