What problem does it solve?
It clarifies what each manifest.llm declaration field (provider, model, base_url, api_compat, capabilities) actually means versus credentials and live probes, preventing agents from conflating declaration-complete presets with working endpoints, and documents the exact Codex app-server operations for reading OAuth quota data.
Core Features & Use Cases
- Declaration field reference: Defines provider, model, base_url, api_compat, and capability flags as non-credential declarations, distinct from credential validity checks in
ResolveRefsWithAuth and from live /doctor probes.
- Codex OAuth quota inspection: Gives the exact app-server sequence — initialize handshake,
account/rateLimits/read request with null params, GetAccountRateLimitsResponse parsing, and optional account/rateLimits/updated subscription — plus the warning that codex doctor --json exposes no quota data.
- Context-window evidence discipline: Separates the official 272K Codex context figure from a dated, route/model/CLI-qualified measured ~372K boundary, with rules for citing each.
- Use Case: An agent asked "does this preset actually work?" routes the question to
/doctor instead of guessing from manifest fields, and an agent needing Codex rate-limit data follows the documented JSON-RPC sequence without touching tokens.
Quick Start
Ask the agent to explain what the provider, base_url, and capabilities fields in a preset manifest declare and how to query Codex OAuth rate limits via the app-server.
