ask_opus5
Get guarded multi-turn code reasoning on Claude Opus 5, a faster, lower-cost Fable alternative. Use it to sanity-check plans, weigh trade-offs, and explore unfamiliar code.
Instructions
The same guarded, multi-turn reasoning as ask, but on Claude Opus 5 (claude-opus-5) instead of Fable — identical arguments, identical result shape (sidecar, followup, context_exhausted), same session/reset conversation model. Reach for it exactly where you'd reach for ask: before guessing at unfamiliar code, when weighing a design trade-off, or to sanity-check a plan or diff. WHICH ONE: Opus 5 is roughly half Fable's price and noticeably faster, so prefer it for high-volume or latency-sensitive reasoning and for long back-and-forth sessions; keep ask (Fable) for the hardest, most consequential single calls. Running BOTH on the same question is a cheap two-model cross-check without paying for a full council. Sessions are namespaced per tool: the same session key on ask and ask_opus5 is two independent conversations (use reset_session(model='opus5') to clear this one). The model has NO tools and CANNOT open files — paste the real code into context (or point at it with context_ref). Same scope as ask: broad and conceptual engineering questions, including brainstorming and ideas for future code, are fine; refused only for direct offensive-security asks (exploit development, attack tooling) and non-software domain knowledge (biology/medicine refused; neuroscience, cognitive science, AI/ML, and CS are in-scope). Opus 5 also works as the opus token in every multi-model mode — ask_council member or synthesizer, ask_chain stage, ask_debate proposer/opponent/adjudicator.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reset | No | Dump+clear this session before asking, starting a fresh conversation. | |
| context | No | Optional code snippets, file paths, or structural context. | |
| session | No | Conversation key. Reuse it to ask follow-ups (Opus 5 keeps context); use a new key or reset=true to start a fresh topic. Opus sessions are namespaced separately from `ask`'s Fable sessions, so the same key on both tools is two independent conversations. | default |
| trusted | No | Operator-authorized. When true, the prohibited-use denylist runs in log-only mode: security vocabulary in the question is audited but does not block. Use for legitimate security-engineering work (PoC analysis, CVE research, binary hardening review) where the question genuinely needs security terms. The operator is responsible for authorizing this flag. | |
| question | Yes | A specific question about concrete software code/architecture (structure, functionality, data flow, module/function relationships, routing). | |
| context_ref | No | Key(s) of context previously saved with `context_write` to pull in and prepend to `context` — so you paste a big codebase context ONCE and reference it by key across many asks instead of re-pasting. Missing keys are reported, not fatal. |