What is seven_day_omelette?

It is the JSON field name for Claude Design's separate weekly rate-limit bucket in Anthropic's internal /api/organizations/{uuid}/usage response. 'Omelette' is Anthropic's internal codename for the Claude Design product, visible in HTTP rate-limit response headers and in the JSON shape that claude.ai/settings/usage renders.

From Anthropic's own infrastructure. Ian Chan first posted publicly about it on X in 2026; the Lobster Pack writeup of Claude Design (May 2026) quotes the original observation: 'Anthropic's infrastructure calls the product Omelette. I'm mentioning it once because it's the codename visible in the API endpoints and rate-limit headers.' The bucket name in /usage is the same codename leaking through.

No. The /api/organizations/{uuid}/usage endpoint is undocumented; it is the call claude.ai/settings/usage makes on reload and was never published as a stable API. The field names are stable enough that the open-source claude-meter Rust client deserializes them by exact name (seven_day_omelette included). Anthropic can rename or drop them without notice.

Because Claude Design's per-request cost looks nothing like a normal chat turn. The Lobster Pack analysis showed the Claude Design system prompt is roughly 30,240 characters (about 8,500 tokens) cached with ephemeral prompt caching, and each design turn fans out into tool calls and a verification subagent. If Anthropic let that burn count against the same weekly seven_day bucket as plain chat, one weekend of design experimentation would wall everything else. A separate per-product weekly bucket lets the design tool have its own ceiling.

Open claude.ai/settings/usage in DevTools, copy the request Cookie header out of the Network tab, then curl 'https://claude.ai/api/organizations/{your-org-uuid}/usage' with that cookie and a Referer of https://claude.ai/settings/usage. Pipe it to jq .seven_day_omelette. If the response is null, your account is not on a plan that has Omelette enabled yet. If it is an object, utilization is a 0.0 to 1.0 fraction and resets_at is a UTC timestamp.

Two outcomes depending on plan. On accounts not in a tier that has the Omelette bucket enabled the field returns null, and there is nothing to render. On accounts that do have it, the field is an object with utilization: 0.0 until the first Claude Design turn lands on the account. After that, the bucket ages normally on its own rolling 7-day window.

Yes when the field is non-null. The Rust struct UsageResponse at lines 18-28 of github.com/m13v/claude-meter/src/models.rs declares seven_day_omelette: Option<Window>, so the parser surfaces it. The dropdown shows each non-null window with its name and percentage; the badge is the worst non-null seven_day window across the set. If your Omelette bucket is at 91% you see '7d_omelette 91%' next to the all-up 7d number.

No. ccusage sums input and output tokens from ~/.claude/projects/*.jsonl on your local disk. Claude Design runs over the claude.ai web app and stores nothing in ~/.claude. Even if it did, Anthropic's quota numerator is dimensionless utilization (computed against a private per-product, per-plan ceiling), and the local logs have no concept of which product bucket a turn counted against. You can only see seven_day_omelette by reading the /usage JSON itself.

Because the JSON shape is server-driven and Anthropic chooses to emit nullable fields rather than omit them. claude-meter's struct declares the field Option<Window>, which deserializes both shapes cleanly: present-as-object when your plan has the bucket, present-as-null otherwise. This is also why the existing pages that called seven_day_omelette an 'experimental bucket usually null for individual accounts' were correct in late 2025 and went out of date once Claude Design rolled out more broadly in 2026.