Enable live subscription limits

txtop can read current Codex and Claude Code subscription windows with the credentials those clients store locally. This is experimental, uses undocumented provider behavior, and is disabled by default.

Review the risk

The requests may break without notice and may violate provider terms of service. They can also expose account identifiers and quota state to the local txtop database. Read unofficial integrations before enabling them.

Local log scanning does not require this feature. Keep it disabled if usage history is enough.

Enable both gates

Live limits require subscription scanning, the global auth-request gate, the source, and its source-specific gate:

[subscription]
enabled = true
auth_requests_enabled = true

codex_enabled = true
codex_auth_requests_enabled = true

claude_code_enabled = true
claude_code_auth_requests_enabled = true
claude_code_live_limits_transport = "auto"

auto tries Claude’s quota-probe transport before the OAuth usage fallback. Use oauth-usage or quota-probe only when diagnosing one transport.

Verify the result

Start txtop after signing in to the corresponding coding client. Open the focused dashboard and select the subscription series, or inspect source health with D.

For structured diagnostics:

txtop db doctor --json

A healthy row records the transport, last success, and current windows. A stale row keeps the last good values while showing the refresh failure. Repeated 401, 403, or 429 responses can mean expired local credentials, an upstream schema change, or provider throttling.

Disable auth_requests_enabled to stop every credential-backed request without turning off local log scanning.