---
title: Experimental Features
description: Opt-in toggles for features that are still maturing — what each one gates and where to read more.
---

**Settings > Experimental** holds toggles for features that are still maturing. "Experimental" doesn't mean unsafe — these are shipped and tested — but the surface area, defaults, or persistence shape may shift between releases. Toggling one off is always reversible.

Two toggles live there today — **Claude Code Usage** and **OpenRouter balance in usage meter**. Agent backend choices such as Ollama, LM Studio, OpenAI API, and Codex live in **Settings > Models** as first-class model/provider controls. Claude Code Plugins, Claude Remote Control, Community Registry, and Claudette Terminal are visible by default in their normal settings locations.

## Claude Code Usage

Gates the **Anthropic OAuth Usage API** integration: the chat composer's usage meter normally shows local token totals (or, on Codex backends, live Codex `account/rateLimits/*` quotas), but for Anthropic / Custom Anthropic sessions the meter can additionally surface real Claude subscription quotas — 5-hour session, weekly all-model, weekly Sonnet/Opus, extra usage — by querying Anthropic's usage API directly. Requires a Pro or Max plan with standard login (env-var auth tokens don't have the OAuth scopes the API needs).

When this is off, the meter on Anthropic-family sessions renders in a greyed-out state that links here when clicked. Codex (Native and Subscription) / OpenAI / OpenRouter / Pi / Ollama / LM Studio sessions are unaffected — the meter stays live for them because it's driven by Codex's own rate-limit notifications and Claudette's per-turn token records, not the Anthropic Usage API.

When this is off, Claudette never reads your Claude Code OAuth tokens for usage data — they stay strictly in the keychain / `.credentials.json` for the `claude` CLI's own use. The Claude Code sign-in flow in **Settings > Models** remains available because agent credential failures need a recovery path independent of usage tracking.

Enabling this toggle opens a confirmation dialog that explains how the data flows and warns that this endpoint is undocumented, so programmatic access may not be permitted under [Anthropic's Consumer Terms](https://www.anthropic.com/legal/consumer-terms). Disabling never prompts.

→ What the panel shows and how it's cached: **[Usage & Metrics](/claudette/features/usage-and-metrics/)**

## OpenRouter balance in usage meter

Shows your live OpenRouter credit balance alongside local token totals for OpenRouter-backed sessions, including Pi OpenRouter models. Turn this off to avoid polling the OpenRouter credits endpoint.

## Stability outlook

| Toggle | What's still moving |
|---|---|
| Claude Code Usage | Cache invalidation around tier changes; richer breakdown views; (non-Anthropic providers already render local-aggregate totals unconditionally). |
| OpenRouter balance in usage meter | Polling cadence and how the balance is surfaced in the meter. |

If a toggle moves to "default-on" or graduates out of experimental, the release notes for that feature describe any one-time migration. Experimental toggles are otherwise independent, never bundled.

## See also

- [Settings](/claudette/features/settings/) — the full settings layout that the Experimental section sits inside
- [Privacy](/claudette/privacy/) — what data each experimental feature does or doesn't send
