---
name: phone-opus
description: Use when you want a consultative Claude Code pass through the local `phone_opus` MCP server. Trigger for blocking second-opinion analysis, repository inspection, summaries, or planning where Claude should have read-only built-in tools but no edit capability.
---

# phone-opus

Use `phone_opus.consult` when you want a blocking Claude Code consult without edit permissions.

## When to use it

Whenever you're making a *major, nontrivial, high level* design decision, you should get a second opinion from Opus.
Opus is intelligent and has a different perspective, so takes its feedback seriously; but nothing it says
should be taken as authoritative or final. It is a pure consultant.

- Ask for a second opinion on code, architecture, debugging, or design.
- Point Claude at a specific repository with `cwd`.
- By default, phone_opus reuses the remembered Claude context for that `cwd`.
- Set `fresh_context: true` when you explicitly want a fresh Claude context instead of the remembered `cwd`-scoped one.

## Tool surface

- `consult`
  - required: `prompt`
  - optional: `cwd`, `fresh_context`, `render`, `detail`
- `health_snapshot`
- `telemetry_snapshot`

## Runtime posture

- Pins Claude to Opus 4.6 with max effort.
- Prepends a fixed consult prefix before your prompt so Opus knows it is advising another model in read-only mode and should return a prioritized actionable report.
- Uses `--dangerously-skip-permissions`, but wraps Claude in an external `systemd-run --user` sandbox.
- The sandbox keeps the filesystem globally read-only, gives Claude a separate persistent home under phone-opus state, leaves `/tmp` and `/var/tmp` writable, and forces the consulted `cwd` read-only when that tree would otherwise be writable.
- Web search is disabled; keep Opus focused on local inspection, reasoning, and any direct web fetches that are truly necessary.
- Previous consult outputs can be found in `/tmp/phone_opus-consults`.
- For related follow-ups on the same repository, keep using the same `cwd`; phone-opus will reuse that remembered context by default, which is much cheaper than cold-starting Opus.
- This surface is consultative only. Edit tools are unavailable.
- The returned `session_id` is still surfaced for traceability, but context reuse is now automatic per `cwd` instead of caller-managed.

## Example

Call `phone_opus.consult` with:

- `prompt`: `Inspect the Rust workspace and tell me where the retry logic is brittle.`
- `cwd`: `/absolute/path/to/repo`

Expect a blocking response containing Claude's answer plus execution metadata such as duration, turn count, session id, and cost when available.