1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
---
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`.
- Treat each consult as a fresh one-shot pass.
## Tool surface
- `consult`
- required: `prompt`
- optional: `cwd`, `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`.
- This surface is consultative only. Edit tools are unavailable.
## 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, and cost when available.
|