[BUG] Artifact publish stuck on 429 frame_daily_push_cap_reached for 8.5+ hours

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

I'm hitting a persistent error when publishing/republishing Artifacts in Claude Code sessions:

Error: deploy 429: frame_daily_push_cap_reached

Details:

• First occurrence: 2026-08-11, 04:30 PT
• Still occurring as of: 2026-08-11, 13:07 PT (8.5+ hours continuous, no reset observed)
• Trigger: republishing existing Artifact pages to their existing URLs (not creating new artifacts)
• Volume: three separate Claude Code sessions on the same account, each republishing 1-3 small HTML pages (60-85KB each, well under any known size limit) on a 15-90 minute cadence over roughly 20 hours, totaling an estimated 60-100+ publish calls
• Affected scope: all artifact URLs on the account are blocked, not just one page (confirmed across 5 distinct artifact URLs)
• Local behavior: file writes on my end succeed every time, only the publish/deploy call itself returns the 429
• Every retry since the first occurrence has returned the same error, no successful publish since

There is no visible way, in the UI or otherwise, to check what the actual daily limit is, how much of it I've used, or when it resets. That's the core issue: I can't tell if this is expected behavior I should just wait out, or a stuck/bugged rate-limit counter, because there's no quota or reset-time visibility anywhere.

Questions:

1. Is this a documented daily cap, and if so what's the reset schedule/timezone?
2. Is there a way to check remaining quota or confirm when it resets?
3. Is 429 the correct/expected response here, or is this a bug (e.g. a stuck rate-limit counter)?

Happy to provide session IDs or further detail if useful.

What Should Happen?

The Artifact publish call should either succeed (if quota is actually available) or return an error that includes remaining quota and/or a reset timestamp, so it's possible to tell a genuine daily cap apart from a stuck rate-limit counter.

Error Messages/Logs

deploy 429: frame_daily_push_cap_reached

Steps to Reproduce

1. In a Claude Code session, publish a page via the Artifact tool (creates a new hosted page at a claude.ai/code/artifact/ URL).
2. Republish the same page to the same URL repeatedly over an extended period (in my case: 3 separate sessions, each republishing 1-3 small HTML pages, 60-85KB each, on a 15-90 minute cadence, ~60-100+ total calls over roughly 20 hours).
3. At some point (first observed 2026-08-11, 04:30 PT), every subsequent publish call starts returning "deploy 429: frame_daily_push_cap_reached" instead of succeeding.
4. The error persists on every retry from that point forward, across all artifact URLs on the account, not just the one being republished at the time. Still occurring 8.5+ hours later as of 2026-08-11, 13:11 PT.

Note: local file writes always succeed; only the Artifact publish/deploy call itself fails.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.221 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

This occurred across 3 concurrent Claude Code sessions on the same account, each running scheduled periodic tasks (cron-style, 15-90 min intervals) that included a republish step. The cap appears to be shared across sessions, not per-session, since all three (and a 4th session checking in on them) were blocked simultaneously once triggered.