Skip to main content
prompt GP ChatGPT

phase-10c-murph-progress-research — Claude Code prompt

phase-10c-murph-progress-research is a Claude Code prompt for researching Murph’s progress contract to improve tool call cards in Phantom chat.

Apache-2.0 ★ 1,497 updated 2026-06-16

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/phase-10c-murph-progress-research.md
Open on GitHub

What phase-10c-murph-progress-research does

The prompt assigns the agent roles of principal engineer, architect, and product manager at Anthropic simultaneously and tasks it with studying what data Murph and pi-mono already provide about tool execution, what Phantom fails to translate into UI, and what minimal Murph changes would unlock detailed tool cards. The agent reads 16 source files (AGENTS.md, Phantom types, SDK converters, UI components, Murph and pi-mono sources), answers 10 questions about the current event contract, what to show safely (command, status, time, exit code) and what to hide (secrets, env, auth headers), and writes results to research/chat-experience/phase-10c-murph-progress-research.md.

The prompt requires an event map Murph → Phantom → UI, list of missing fields, tool_progress schema extension, disclosure policy, Phase 10C implementation plan split into Phantom-only and Murph changes, test cases, and a builder prompt seed. Without cloned repositories under /Users/truffle/work, the agent cannot read Murph, pi-mono sources, and notes.

What it helps with

  • study Murph event contract and identify what Phantom loses when translating to UI
  • design generic tool_progress schema without leaking UI policy into Murph
  • determine what to show safely in tool cards (command, status, time) and what to hide (secrets, env)
  • split Phase 10C plan into Phantom-only changes and Murph changes
  • verify compatibility with Anthropic SDK, OpenAI, and ZAI

Example prompts for the agent

  • Research Murph progress contract for Phantom and write findings to research/chat-experience/phase-10c-murph-progress-research.md
  • Analyze which Murph events reach Phantom and what gets lost in UI translation
  • Propose a tool_progress schema for detailed tool cards without leaking UI policy into Murph

How to install phase-10c-murph-progress-research

Manually: put the files in place

.claude/commands/phase-10c-murph-progress-research.md

Questions about phase-10c-murph-progress-research

How to install phase-10c-murph-progress-research in Claude Code?

Place the prompt file in .claude/commands/phase-10c-murph-progress-research.md at the project root.

What does phase-10c-murph-progress-research do?

The prompt launches autonomous research into Murph and pi-mono event contract to understand what tool execution data is already available, what Phantom fails to translate into UI, and what Murph changes are needed for detailed tool cards. The agent reads 16 source files, answers 10 questions, and writes results to markdown.

What does the prompt require to run?

The prompt requires cloned repositories of Phantom, Murph, pi-mono, Pi Code, OpenClaw, Claw Code, opencode, and notes under /Users/truffle/work. Without them, the agent cannot read sources and answer research questions.

Source text

phase-10c-murph-progress-research.md · Apache-2.0
ultrathink. ultrathink. ultrathink.

You are a principal engineer, principal architect, AND principal product
manager at Anthropic, all three at once. You are researching the richer Murph
progress contract needed for Phantom chat.

No context anxiety. No token limits. No time pressure. No cost anxiety. No v2
thinking. There is no v2. Build it right. Take as long as you need. This prompt
is your starting point, not your ceiling. Exceed it.

You are fully autonomous. You may inspect Phantom, Murph, pi-mono, Pi Code,
OpenClaw, Claw Code, opencode, and notes already cloned under `/Users/truffle/work`.
Use authentic source code and official docs only. Do not use SEO summaries.
Do not edit source code. Your only write target is:

`research/chat-experience/phase-10c-murph-progress-research.md`

## Mission

Phantom can now show basic active-run activity, but tool call cards are too thin:
they show that a tool ran, but not enough safe, useful detail inside the
dropdown. We need to understand what Murph and pi-mono can already provide,
what Phantom is failing to translate, and what small generic Murph additions
would unlock a best-in-class UI.

## Required Reading

Read these files in order:

1. `/Users/truffle/.claude/AGENTS.md` around 70 lines.
2. `/Users/truffle/.claude/CLAUDE.md` around 300 lines.
3. `research/chat-experience/phase-10a-synthesis.md` around 351 lines.
4. `src/chat/types.ts` around 222 lines.
5. `src/chat/types-tool.ts` around 151 lines.
6. `src/chat/sdk-to-wire.ts` around 297 lines.
7. `src/agent/chat-query.ts` around 177 lines.
8. `chat-ui/src/lib/chat-types.ts` around 190 lines.
9. `chat-ui/src/lib/chat-dispatch-tools.ts` around 158 lines.
10. `chat-ui/src/components/tool-call-card.tsx` around 144 lines.
11. `/Users/truffle/work/murph/AGENTS.md` around 40 lines.
12. `/Users/truffle/work/murph/ARCHITECTURE.md` if present.
13. `/Users/truffle/work/murph/packages/anthropic-sdk-shim/src` relevant files.
14. `/Users/truffle/work/murph/packages/core/src` relevant runtime files.
15. `/Users/truffle/work/pi-mono` relevant agent/runtime files if present.
16. `/Users/truffle/work/notes-main` relevant notes on compaction, tool use,
    progress, and agent event design.

If a path is missing, note it and continue.

## Questions To Answer

1. Which Phantom wire frames exist for tool start, tool input, running,
   result, blocked, aborted, and error?
2. Which Murph events currently reach Phantom?
3. Which Pi or pi-mono event details are available but not forwarded?
4. What should a generic Murph progress contract expose without leaking UI
   policy into Murph?
5. How should Phantom safely render:
   - command
   - cwd
   - status
   - elapsed time
   - partial progress
   - exit code
   - stdout/stderr summaries
   - artifact paths or URLs
   - errors
6. What must remain hidden by default?
7. What parts can be fixed entirely in Phantom translation/rendering?
8. What parts require Murph changes?
9. How should this work across OpenAI, Anthropic, and ZAI?
10. What tests must prove compatibility with SDK-style streams?

## Acceptance Criteria

Your research file must include:

1. A current event-contract map from Murph to Phantom wire frames to UI.
2. A list of missing fields and whether each belongs in Phantom or Murph.
3. A proposed generic `tool_progress` or tool lifecycle schema extension.
4. A safe disclosure policy for tool-card contents.
5. A concrete Phase 10C implementation plan split into Phantom-only and Murph
   changes.
6. Test cases and real provider verification scenarios.
7. A "builder prompt seed" section.

## Anti-Patterns

Do not:

1. Recreate pi-mono behavior that Murph already exposes.
2. Build Phantom-specific telemetry into Murph.
3. Show raw JSON by default.
4. Show secrets, env values, auth headers, cookies, or raw hidden reasoning.
5. Break Anthropic SDK compatibility to improve OpenAI behavior.
6. Assume every provider emits identical lifecycle events.
7. Treat tool cards as decorative. They are trust surfaces.

ultrathink before finalizing. Self-review the output against every acceptance
criterion. Your final answer should list the output file you wrote and the top
five findings only.

© ghostwright · Apache-2.0 · ghostwright/phantom

Similar prompts

All prompts for Agent setup: memory, context, orchestration →

From the same set38

The whole set →
phase-10i-chat-detail-research The phase-10i-chat-detail-research prompt asks Claude Code to examine Phantom’s chat UI and recommend the next implementation slices. Use it to shape a focused interface plan and Playwright checks. GP ChatGPT ★ 1,497repo stars phase-10i-memory-architecture-research phase-10i-memory-architecture-research — a Claude slash command that researches how Phantom chat should keep user-facing memory apart from the agent's working memory, then writes a report with a plan. GP ChatGPT ★ 1,497repo stars phase-10a-murph-pi-event-research phase-10a-murph-pi-event-research is a Claude Code prompt that audits Murph and Pi runtime events to surface agent progress, compaction, and tool calls in Phantom chat. GP ChatGPT ★ 1,497repo stars phase-10a-product-experience-research The phase-10a-product-experience-research prompt guides research into Phantom’s long-running agent chat, from run status to tool details and error states. Use it to shape an interface proposal and a phased build plan. GP ChatGPT ★ 1,497repo stars phase-10b-durable-timeline-research phase-10b-durable-timeline-research directs an autonomous research run on durable chat timelines and SSE reconnect logic in Phantom without touching source files. GP ChatGPT ★ 1,497repo stars echo Before answering a substantive question, echo searches memory for a similar earlier decision. If it finds a strong match, it brings up that conclusion and asks whether it still applies. CX Codex +1 ★ 1,497repo stars phase-10m-pi-murph-continuity-research phase-10m-pi-murph-continuity-research is a prompt for Claude Code and ChatGPT that investigates context recovery and compaction in Murph and Phantom, checking whether they reinvent Pi primitives. GP ChatGPT ★ 1,497repo stars phase-10i-transcript-recovery-builder The phase-10i-transcript-recovery-builder prompt for Claude Code builds transcript recovery for Phantom on Murph, letting agents search chat history after context compaction. GP ChatGPT ★ 1,497repo stars

Project sponsors

Companies that keep this analytics open