microsoft · MichaelDanCurtis · Jun 24, 2026 · Jun 24, 2026 · Jun 24, 2026 · Jun 24, 2026
@@ -0,0 +1,16 @@
+---
+description: Launch the HVE Cockpit agent gallery (all 65 agents) and show it live in the preview pane
+argument-hint: ""
+---
+
+# Gallery
+
+Open the **HVE Cockpit gallery** surface (the scrollable contact sheet of every HVE Core agent) and show it live in the Claude Code preview pane. Do this without asking for confirmation.
+
+1. **Build if needed.** From `rpi-cockpit/`, run `npm run build` only when `dist/` is missing or older than `src/`; otherwise skip it.
+2. **Launch the producer in the background:** `cd rpi-cockpit && node tools/agent-gallery.mjs` (pass `PORT=<n>` if 4505 is taken). It renders every agent through the real cockpit client and prints `agent gallery: http://127.0.0.1:<port>/?key=<token>` while it keeps serving. Capture that full keyed URL from its output.
+3. **Show it in the preview pane.** Start or reuse a preview server, then navigate the preview to the captured keyed URL (`preview_eval` setting `window.location.href`). The page loads the full cockpit with the `gallery` domain already open.
+4. **Verify** with a screenshot (agent tiles grouped by category, the S/M/L size toggle bottom-left of the header, click-to-expand lightbox) and a console-error check.
+5. **Report** the keyed URL so the user can open it in their own browser, and remind them the **S/M/L** toggle resizes the tiles and clicking a tile opens the full-size lightbox.
+
+Leave the producer running so the user can keep exploring; it serves until killed.
@@ -0,0 +1,11 @@
+{
+  "version": "0.0.1",
+  "configurations": [
+    {
+      "name": "rpi-cockpit",
+      "runtimeExecutable": "node",
+      "runtimeArgs": ["rpi-cockpit/dist/index.js", "live"],
+      "autoPort": true
+    }
+  ]
+}
@@ -5,15 +5,15 @@ handoffs:
   - label: "🗑️ Clear"
     agent: RPI Agent
     prompt: "/clear"
-    send: true
+    send: false
   - label: "🚀 Continue with RPI"
     agent: RPI Agent
     prompt: "/rpi suggest"
-    send: true
+    send: false
   - label: "🚀 Continue with Backlog"
     agent: GitHub Backlog Manager
     prompt: "/github-suggest"
-    send: true
+    send: false
 ---
 
 # Memory Agent

@@ -16,19 +16,19 @@ handoffs:
   - label: "🛠️ Refactor"
     agent: Prompt Builder
     prompt: /prompt-refactor all prompt files in this conversation
-    send: true
+    send: false
   - label: "🤔 Analyze"
     agent: Prompt Builder
     prompt: /prompt-analyze all prompt files in this conversation
-    send: true
+    send: false
   - label: "🔧 Apply Fixes"
     agent: Prompt Builder
     prompt: "/prompt-build make updates based on findings in this conversation"
-    send: true
+    send: false
   - label: "♻️ Cleanup Sandbox"
     agent: Prompt Builder
     prompt: "Clear the sandbox for this conversation"
-    send: true
+    send: false
 ---
 
 # Prompt Builder

@@ -10,27 +10,27 @@ handoffs:
   - label: "1️⃣"
     agent: RPI Agent
     prompt: "/rpi continue=1"
-    send: true
+    send: false
   - label: "2️⃣"
     agent: RPI Agent
     prompt: "/rpi continue=2"
-    send: true
+    send: false
   - label: "3️⃣"
     agent: RPI Agent
     prompt: "/rpi continue=3"
-    send: true
+    send: false
   - label: "▶️ All"
     agent: RPI Agent
     prompt: "/rpi continue=all"
-    send: true
+    send: false
   - label: "🔄 Suggest"
     agent: RPI Agent
     prompt: "/rpi suggest"
-    send: true
+    send: false
   - label: "💾 Save"
     agent: Memory
     prompt: /checkpoint
-    send: true
+    send: false
 ---
 
 # RPI Agent
@@ -99,6 +99,17 @@ When a task requires subagents but neither `runSubagent` nor `task` tools are av
 
 Treat the phase guidance below as operating defaults rather than ceremony. Delegate only when it materially improves the outcome.
 
+## Cockpit narration
+
+When the `rpi-cockpit` MCP tools are available, narrate this workflow to the RPI Cockpit following `rpi-cockpit/agents/cockpit-instructions.md`. Skip silently when the tools are not connected. Map the beats as follows:
+
+* Call `session_begin(task, host)` once when the user request starts.
+* Call `phase_enter(phase)` when entering each phase: `research`, `plan`, `implement`, `review`, and `discover`.
+* Wrap every `Researcher Subagent` and `Phase Implementor` dispatch with `subagent_start(name, role)` before and `subagent_stop(name, result)` after.
+* Call `validate(check, status)` for each check run in the Phase 3 validation gate.
+* Call `artifact_update(path, summary)` after writing or updating each `.copilot-tracking/` artifact.
+* In Phase 5, surface the Suggested Next Work list through `present_options(prompt, options[])` so the user can choose the next item in the cockpit. Act only on an explicit user selection; if no selection is made, stop and yield to the user rather than auto-starting the next cycle.
+
 ## Context Discipline
 
 After any subagent returns, this turn must be lean:

@@ -7,15 +7,15 @@ handoffs:
   - label: "🔬 Research Questions"
     agent: Task Researcher
     prompt: "/task-research Find and read the most recent challenge tracking document in .copilot-tracking/challenges/ (most recent by date prefix) for the Q&A log and unresolved items: these define the research scope."
-    send: true
+    send: false
   - label: "📋 Revise Plan"
     agent: Task Planner
     prompt: "/task-plan Find and read the most recent challenge tracking document in .copilot-tracking/challenges/ (most recent by date prefix) for challenge findings and unresolved items before planning."
-    send: true
+    send: false
   - label: "⚡ Implement Changes"
     agent: Task Implementor
     prompt: "/task-implement Address the immediate changes identified through the challenge session. Find and read the most recent challenge tracking document in .copilot-tracking/challenges/ (most recent by date prefix) for findings."
-    send: true
+    send: false
 ---
 
 # Task Challenger

@@ -9,7 +9,7 @@ handoffs:
   - label: "✅ Review"
     agent: Task Reviewer
     prompt: /task-review
-    send: true
+    send: false
 ---
 
 # Task Implementor
@@ -63,6 +63,15 @@ The Researcher Subagent returns deep research findings: subagent research docume
 
 Subagents can run in parallel when investigating independent topics or executing independent phases.
 
+## Cockpit narration
+
+When the `rpi-cockpit` MCP tools are available, narrate implementation progress to the RPI Cockpit following `rpi-cockpit/agents/cockpit-instructions.md`. Skip silently when the tools are not connected. Map the beats as follows:
+
+* Call `phase_enter("implement")` when implementation starts.
+* Wrap every `Phase Implementor` dispatch with `subagent_start(name, role)` before and `subagent_stop(name, result)` after.
+* Call `validate(check, status)` for each lint, type, test, and build check.
+* Call `artifact_update(path, summary)` after updating the changes log in `.copilot-tracking/changes/`.
+
 ## Context Discipline
 
 After any subagent returns, this turn must be lean:

@@ -9,7 +9,7 @@ handoffs:
   - label: "⚡ Implement"
     agent: Task Implementor
     prompt: /task-implement
-    send: true
+    send: false
 ---
 
 # Task Planner
@@ -54,6 +54,15 @@ Run `Plan Validator` using `runSubagent` or `task`, providing these inputs:
 
 Subagents can run in parallel when investigating independent topics or validating independent concerns.
 
+## Cockpit narration
+
+When the `rpi-cockpit` MCP tools are available, narrate planning progress to the RPI Cockpit following `rpi-cockpit/agents/cockpit-instructions.md`. Skip silently when the tools are not connected. Map the beats as follows:
+
+* Call `phase_enter("plan")` when planning starts.
+* Wrap every `Researcher Subagent` and `Plan Validator` dispatch with `subagent_start(name, role)` before and `subagent_stop(name, result)` after.
+* Call `artifact_update(path, summary)` after writing or updating each plan, details, or planning log file in `.copilot-tracking/`.
+* Present Planning Decisions (PD) choices through `present_options(prompt, options[])` instead of asking in chat, then act on the returned id.
+
 ## Context Discipline
 
 After any subagent returns, this turn must be lean:

@@ -8,7 +8,7 @@ handoffs:
   - label: "📋 Create Plan"
     agent: Task Planner
     prompt: /task-plan
-    send: true
+    send: false
   - label: "🔬 Deeper Research"
     agent: Task Researcher
     prompt: /task-research continue deeper research based on potential next research items
@@ -46,6 +46,14 @@ Run `Researcher Subagent` with `runSubagent` or `task`, and parallelize calls wh
 
 Subagents can run in parallel when investigating independent topics or sources.
 
+## Cockpit narration
+
+When the `rpi-cockpit` MCP tools are available, narrate research progress to the RPI Cockpit following `rpi-cockpit/agents/cockpit-instructions.md`. Skip silently when the tools are not connected. Map the beats as follows:
+
+* Call `phase_enter("research")` when research starts.
+* Wrap every `Researcher Subagent` dispatch with `subagent_start(name, role)` before and `subagent_stop(name, result)` after.
+* Call `artifact_update(path, summary)` after writing or updating each research document in `.copilot-tracking/research/`.
+
 ## Context Discipline
 
 After any subagent returns, this turn must be lean:

@@ -10,15 +10,15 @@ handoffs:
   - label: "🔬 Research More"
     agent: Task Researcher
     prompt: /task-research
-    send: true
+    send: false
   - label: "📋 Revise Plan"
     agent: Task Planner
     prompt: /task-plan
-    send: true
+    send: false
   - label: "⚡ Implement Immediately"
     agent: Task Implementor
     prompt: /task-implement Address the findings found in the review document
-    send: true
+    send: false
 ---
 
 # Implementation Reviewer
@@ -33,6 +33,14 @@ Reviews completed implementation work from `.copilot-tracking/` artifacts. Valid
 * Match `applyTo` patterns from `.github/instructions/` files against changed file types to identify applicable conventions.
 * Subagents return structured, evidence-based responses with severity levels and can ask clarifying questions rather than guessing.
 
+## Cockpit narration
+
+When the `rpi-cockpit` MCP tools are available, narrate review progress to the RPI Cockpit following `rpi-cockpit/agents/cockpit-instructions.md`. Skip silently when the tools are not connected. Map the beats as follows:
+
+* Call `phase_enter("review")` when review starts.
+* Call `artifact_update(path, summary)` after writing or updating the review log in `.copilot-tracking/reviews/`.
+* When review surfaces a choice for the user, present it through `present_options(prompt, options[])` instead of asking in chat, then act on the returned id.
+
 ## Context Discipline
 
 After any subagent returns, this turn must be lean:

@@ -297,3 +297,61 @@ The `copilot-setup-steps.yml` and `.devcontainer/scripts/on-create.sh` share mos
 <!-- </coding-agent-environment> -->
 
 🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.
+
+<!-- rpi-cockpit:narration:begin -->
+## Cockpit instrumentation
+
+When the `rpi-cockpit` MCP tools are available, narrate your work to the cockpit by calling them. Pick the surface that matches what you are doing: the cockpit renders one view per kind of work, so a reviewer drives the findings panel, a backlog manager drives the kanban, an orchestrator drives the team board, and so on. These calls are informational and non-blocking unless noted. When the tools are not available, do nothing extra (the user's steering is still readable from disk, see the end).
+
+### Always, in any workflow
+
+* At the start of a coding session or build, call `session_begin(task, host)`.
+* Call `set_context(instructions, skills, collection)` to show which coding standards, skills, and collection are active for this work. Pass everything currently active; omitting a field clears that group.
+* At each major step, and before any decision, call `check_directives()`. It returns immediately with any notes or picks the user queued in the cockpit (or "no pending directives"). You MUST read and act on them.
+* To let the user choose what to do, call `present_workflows()` (a native choice card in the chat), or `open_navigator()` to pop the in-cockpit workflow picker (for example on a `/Nav` request).
+* To show the user's app under development beside the cockpit, call `set_app_frame(url)` with a loopback http(s) URL (localhost, 127.0.0.1, or [::1]); non-loopback URLs are rejected. Pass null to clear it.
+
+### Asking the user (any workflow, these BLOCK)
+
+* `present_options(prompt, options[])` for a bounded choice: it blocks until the user picks (in the cockpit or the native card) and returns the chosen `id`. Act on the returned id.
+* `ask_question(prompt)` for a free-text answer: it blocks until the user answers and returns the text.
+
+### RPI build loop (research, plan, implement, review, discover)
+
+* `phase_enter(phase)` on entering each phase (research|plan|implement|review|discover).
+* `subagent_start(name, role)` before a subagent and `subagent_stop(name, result)` after.
+* `artifact_update(path, summary)` after writing a tracking file.
+* `validate(check, status)` on each validation check (status ok|running|fail|pending).
+* `offer_approaches(label, options[])` to populate the cockpit's Steer select with the real choices for the next phase (non-blocking).
+* `show_screen(html, title?)` and `clear_screen()` for arbitrary static HTML (a mockup, a diff, rendered markdown, a diagram) in a sandboxed pane.
+
+### Reviews and audits (code review, PR review, security, accessibility, RAI)
+
+* `review_start(target)` when you begin a review (target is the branch, PR, or scope).
+* `add_finding(severity, title, file?, line?, detail?)` per finding (severity critical|high|medium|low|info). The cockpit groups findings by severity with file links.
+
+### Guided document builders (PRD, BRD, ADR, security, RAI, accessibility plans)
+
+* `interview_start(docType)` when you begin the guided interview.
+* Ask each question with `ask_question(prompt)` (it blocks for the answer); render the growing draft with `show_screen(html, "…")`.
+
+### Backlog orchestration (GitHub, ADO, Jira: discover, triage, sprint, execute)
+
+* `backlog_start(target, columns[])` to open the board (target is the sprint, repo, or project; columns are the ordered state names).
+* `add_item(id, title, column, kind?, tier?)` to add or update a work item, `move_item(id, column)` as it progresses, and `set_backlog_action(text)` to show the action you are taking (null clears it).
+
+### Team orchestration (an orchestrator running subagents)
+
+* `team_start(task, orchestrator)` to open the team board.
+* `add_agent(id, name, role?, status)` (status queued|running|blocked|done|failed), `update_agent(id, status?, action?)` as each subagent progresses, and `remove_agent(id)` when one leaves.
+* The user's pause, swap, and spawn interventions arrive as directives: call `check_directives()` and act on them. The cockpit expresses intent only and never controls agents directly.
+
+### Codebase navigation (research and large edits)
+
+* `codemap_set(nodes[])` with the slice of files relevant to the task (each node has id, path, kind file|dir, and an optional group). This opens the spatial codebase map.
+* `codemap_focus(id)` as you move to a file, and `codemap_touch(id, kind)` to mark a node read or edit (your trail through the code).
+
+### When the tools are not available
+
+Do not call them. The user's steering is still readable from disk: notes and approach picks are appended to `<state-dir>/directives.jsonl` and answered decisions to `<state-dir>/decisions.jsonl`, one JSON object per line. The `<state-dir>` is printed on startup (`rpi-cockpit: state dir <state-dir>`).
+<!-- rpi-cockpit:narration:end -->
@@ -421,6 +421,7 @@ FodyWeavers.xsd
 !.vscode/launch.json
 !.vscode/extensions.json
 !.vscode/*.code-snippets
+!.vscode/mcp.json
 !.vscode/mcp.json.sample
 !.vscode/README.md
 
@@ -488,6 +489,9 @@ dependency-pinning-artifacts/
 .mcp/*.local.json
 .mcp/.env
 
+# Codex MCP config holds a machine-specific absolute path (rpi-cockpit init) - never commit
+/.codex/
+
 # Docusaurus build artifacts
 docs/docusaurus/build/
 docs/docusaurus/.docusaurus/

@@ -0,0 +1,14 @@
+{
+  "mcpServers": {
+    "rpi-cockpit": {
+      "type": "stdio",
+      "command": "node",
+      "args": [
+        "${CLAUDE_PROJECT_DIR}/rpi-cockpit/dist/index.js"
+      ],
+      "env": {
+        "RPI_COCKPIT_PORT": "4399"
+      }
+    }
+  }
+}
@@ -0,0 +1,12 @@
+{
+  "servers": {
+    "rpi-cockpit": {
+      "type": "stdio",
+      "command": "node",
+      "args": [
+        "${workspaceFolder}/rpi-cockpit/dist/index.js"
+      ],
+      "cwd": "${workspaceFolder}"
+    }
+  }
+}