davinci-resolve-mcp 2.24.0 → 2.24.1

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 Release history for the DaVinci Resolve MCP Server. The latest release is summarized in the root README; older entries live here to keep the README focused.
 
+## What's New in v2.24.1
+
+**`npx davinci-resolve-mcp` no longer breaks MCP clients when invoked without a
+subcommand.** The npm bootstrapper previously defaulted to `--help`, which wrote
+usage text to stdout and exited 0. MCP stdio clients (Hermes Agent, Claude
+Desktop, Cursor, etc.) read that as malformed JSON-RPC, retried three times,
+then dropped the connection. `bin/davinci-resolve-mcp.mjs` now defaults to the
+`server` subcommand when no arguments are supplied. Explicit `--help`, `-h`,
+`help`, `--version`, and `-v` continue to print to stdout as before, and
+existing configs that already pass `server` explicitly are unaffected. Reported
+in [#41](https://github.com/samuelgursky/davinci-resolve-mcp/issues/41).
+
 ## What's New in v2.24.0
 
 **Host-chat vision protocol (V2)** — `analyze_*` actions now use
@@ -88,10 +100,7 @@ ffprobe/ffmpeg resolve even when the MCP server is launched by a GUI app
 Mandatory" section. `docs/SKILL.md` rewrites the `analyze_media` prompt
 guidance for the host-chat-paths protocol and adds the anti-regression rule.
 `docs/guides/media-analysis-guide.md` covers the deferred vision payload and
-commit step. New design docs under `docs/design/`:
-`v2-control-panel-design.md`, `v2-db-schema.sql`,
-`v2-implementation-gameplan.md`, `v2-shot-schema-spec.md`,
-`control-panel-polish-gameplan.md`.
+commit step.
 
 **Validation**: static import checks, API parity audit, focused
 media-analysis + marker/range/v232/v233 unit tests, npm CLI smoke,

package/README.md

@@ -1,6 +1,6 @@
 # DaVinci Resolve MCP Server
 
-[![Version](https://img.shields.io/badge/version-2.24.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.24.1-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
 [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
 [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
 [![Tools](https://img.shields.io/badge/MCP%20Tools-32%20(329%20full)-blue.svg)](#server-modes)
@@ -11,6 +11,10 @@
 
 A Model Context Protocol (MCP) server that lets AI assistants control DaVinci Resolve Studio through the official Scripting API. It provides full API coverage plus guarded workflow helpers for editing, media pool organization, render setup, review markers, grading, Fusion, Fairlight, project lifecycle tasks, extension authoring, and source-safe media analysis.
 
+[![Local control panel](docs/images/control-panel/01-overview.png)](docs/guides/control-panel.md)
+
+A local browser control panel ships with the server for inspecting Resolve state, running source-safe analysis, drilling into analyzed clips and shots, and editing analysis output inline. See the [Control Panel Guide](docs/guides/control-panel.md) for the full tour.
+
 ## Quick Start
 
 ```bash
@@ -114,6 +118,7 @@ For method-by-method status, see [API Coverage and Test Results](docs/reference/
 | [API Coverage and Test Results](docs/reference/api-coverage.md) | Key stats, API coverage table, live-test status, full method reference |
 | [Kernel Action Coverage](docs/kernels/README.md) | Current guarded workflow action map |
 | [AI Skill Reference](docs/SKILL.md) | Operational context for AI assistants using the compound server |
+| [Control Panel Guide](docs/guides/control-panel.md) | Local browser panel tour: Overview, Review (bin/clip/shot), Analyze, Setup, Preferences |
 | [Media Analysis Guide](docs/guides/media-analysis-guide.md) | Source-safe FFprobe, FFmpeg, Whisper, sidecar, and analysis-root workflows |
 | [Multicam Setup Helper Guide](docs/guides/multicam-setup-guide.md) | Stacked timeline prep, helper/API boundary, and Resolve UI conversion steps |
 | [Editorial Decision Guide](docs/guides/editorial-decision-guide.md) | Project-owned editorial craft guidance for analysis and timeline decisions |

package/bin/davinci-resolve-mcp.mjs

@@ -336,7 +336,10 @@ function commandControlPanel(args) {
 }
 
 function main() {
-  const [command = "--help", ...args] = process.argv.slice(2);
+  const argv = process.argv.slice(2);
+  // No args → run the MCP stdio server. Anything printed to stdout would
+  // otherwise be parsed as JSON-RPC by MCP clients and break the connection.
+  const [command = "server", ...args] = argv;
 
   try {
     if (command === "--help" || command === "-h" || command === "help") {

package/docs/guides/control-panel.md

@@ -0,0 +1,128 @@
+# Local Control Panel
+
+The DaVinci Resolve MCP ships with a local, single-user browser control panel for
+inspecting Resolve state, running source-safe media analysis, drilling into
+analyzed clips and shots, fixing analysis output inline, and managing
+preferences.
+
+The panel is a local HTTP server (default `http://127.0.0.1:8765`). It does not
+expose a network listener beyond loopback and does not modify source media.
+
+## Launching the panel
+
+```bash
+# From source
+venv/bin/python -m src.control_panel
+
+# From the npm package
+npx davinci-resolve-mcp control-panel
+
+# From a chat client via MCP
+resolve_control(action="open_control_panel")
+```
+
+Once running, you can `resolve_control(action="control_panel_status")` to check
+the pidfile or `resolve_control(action="close_control_panel")` to stop it.
+
+## Tour
+
+### Overview
+
+![Control panel overview](../images/control-panel/01-overview.png)
+
+The Overview tab is the at-a-glance summary for the active project: Resolve
+connection state, source clip counts, analysis progress, search index size,
+and the source-media safety status.
+
+### Analysis → Analyze
+
+![Analyze view](../images/control-panel/06-analyze.png)
+
+The Analyze view inventories the Resolve media pool read-only and lets you
+queue source-safe analysis jobs. Filters cover bin, media type, clip status,
+and analysis status. Resolve media stays read-only; analysis outputs land under
+the configured analysis root.
+
+### Analysis → Review (bin grid)
+
+![Review bin grid](../images/control-panel/02-review-bin-grid.png)
+
+The Review surface is the browser for analyzed clips. Each card shows a
+representative thumbnail, summary one-liner, primary use, shot count, and tags.
+Click into a card to drill down.
+
+### Clip detail
+
+![Clip detail with shot strip](../images/control-panel/03-clip-detail.png)
+
+The clip view shows the full summary, tags, editorial notes, and a strip of
+every detected shot with thumbnails. From here you can open the clip in
+Resolve, jump to the transcript, or click into any shot for the full V2 field
+breakdown.
+
+### Transcript
+
+![Transcript view with word-level timing](../images/control-panel/04-transcript.png)
+
+The transcript view is reachable from the clip detail (top-right `Transcript`
+button). Each segment shows its start timecode, the cleaned sentence, and the
+word-level transcription beneath. The segment filter narrows by text; clicking
+a segment can jump the Resolve playhead to that source time. `Re-transcribe
+with words` re-runs the configured local transcription backend (Whisper by
+default) without re-doing visual analysis, and `corrections.json` captures
+inline edits so they survive future re-runs.
+
+### Shot detail with inline correction
+
+![Shot detail with V2 fields and frames](../images/control-panel/05-shot-detail.png)
+
+The shot view shows every V2 schema field (shot size, framing, camera height,
+motion direction, lens character, lighting, composition notes, and more)
+alongside the frames the vision pass actually saw. Each subjective field is
+editable inline — edits land in `corrections.json` with an append-only
+changelog and are merged on top of the next re-analysis so human notes survive
+fresh vision runs. `Open in Resolve` bounces you straight to the clip in the
+source viewer with the shot's mark in/out set.
+
+### Setup → Resolve diagnostic
+
+![Setup / Resolve diagnostic](../images/control-panel/07-diagnostics-resolve.png)
+
+The Resolve diagnostic page reports the live connection, product/version,
+active page, project identity, and media pool inventory. Useful when chat
+sessions need to confirm Resolve is reachable before issuing scripted
+operations.
+
+### Preferences → Analysis
+
+![Preferences / Analysis defaults](../images/control-panel/08-preferences-analysis.png)
+
+Server-wide analysis defaults: vision on/off, transcription default, slate
+detection, source-trust grading (`auto` / `filename` / `low` / `medium` /
+`high`), default analysis depth, default sample frame count, persistence
+behavior, summary style, and report format. These are the defaults the
+`analyze_media` prompt uses when not overridden per call.
+
+## Chat ↔ panel state sharing
+
+The panel and chat share focus state through `panel_state.json` (under the
+active project's analysis root). MCP actions:
+
+- `media_analysis(action="get_panel_state")` — read current focus (project,
+  clip, shot)
+- `media_analysis(action="set_panel_state", params={...})` — set focus from
+  chat
+- `media_analysis(action="session_start_context")` — bootstrap a chat session
+  with the panel's current focus
+
+The dashboard polls `/api/panel_state` every 2 seconds, so changes from chat
+appear in the UI without a refresh.
+
+## Open in Resolve
+
+The shot view and clip view both have an Open-in-Resolve action. Under the
+hood this calls `media_pool_item(action="open_in_viewer", params={clip_id,
+mark_in, mark_out})`, which selects the clip on the Media page, loads it into
+the source viewer, sets mark in/out, and brings Resolve to the foreground via
+an OS-level window activation (AppleScript on macOS, PowerShell `AppActivate`
+on Windows, wmctrl/xdotool on Linux).

package/install.py

@@ -34,7 +34,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "2.24.0"
+VERSION = "2.24.1"
 SUPPORTED_PYTHON_MIN = (3, 10)
 SUPPORTED_PYTHON_MAX = (3, 12)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "davinci-resolve-mcp",
-  "version": "2.24.0",
+  "version": "2.24.1",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

package/src/granular/common.py

@@ -80,7 +80,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.24.0"
+VERSION = "2.24.1"
 logger = logging.getLogger("davinci-resolve-mcp")
 logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
 logger.info(f"Detected platform: {get_platform()}")

package/src/server.py

@@ -11,7 +11,7 @@ Usage:
     python src/server.py --full       # Start the 329-tool granular server instead
 """
 
-VERSION = "2.24.0"
+VERSION = "2.24.1"
 
 import base64
 import os
@@ -6037,7 +6037,7 @@ def _media_analysis_timed_marker_prompt() -> Dict[str, Any]:
 # one-marker-per-frame collisions). The canonical store is the analysis DB; the
 # correction surface is the control panel + chat, not Resolve markers.
 #
-# See docs/design/v2-shot-schema-spec.md §9.1 (Decisions log) for details.
+# See the V2 shot schema spec §9.1 (Decisions log) for details.
 V2_MACHINE_MARKER_WRITEBACK_ENABLED = False
 
 
@@ -6100,8 +6100,8 @@ def _media_analysis_timed_marker_decision(p: Dict[str, Any]) -> Dict[str, Any]:
             "note": (
                 "V2 architecture disables machine marker writeback to Resolve "
                 "(per-shot, qc_warning, best_moment). Clip-level metadata "
-                "(Description, Keywords, Comments) still writes. See "
-                "docs/design/v2-shot-schema-spec.md §9.1 for rationale."
+                "(Description, Keywords, Comments) still writes. See the V2 "
+                "shot schema spec §9.1 for rationale."
             ),
         }
 
@@ -9479,7 +9479,7 @@ def resolve_control(action: str, params: Optional[Dict[str, Any]] = None) -> Dic
 #
 # Until the SQLite source-of-truth migration (C1) lands, corrections live in a
 # per-clip sidecar JSON at {clip_dir}/corrections.json. Schema mirrors the V2
-# DB design (docs/design/v2-db-schema.sql §subjective_fields + field_changelog):
+# DB design (V2 schema — subjective_fields + field_changelog tables):
 #
 #   {
 #     "schema_version": "2.0",

package/src/utils/analysis_memory.py

@@ -1,6 +1,6 @@
 """Memory and heartbeat layer for V2 analysis architecture.
 
-Per docs/design/v2-shot-schema-spec.md §9 and the project_v2_architecture memory,
+Per the V2 shot schema spec §9 and the project_v2_architecture memory,
 each project's analysis root carries narrative memory alongside the structured DB:
 
     {analysis_root}/memory/

package/src/utils/media_analysis.py

@@ -3710,7 +3710,7 @@ async def execute_plan_async(
     ):
         manifest["index"] = build_analysis_index(output_root)
 
-    # V2 memory + heartbeat layer (per docs/design/v2-shot-schema-spec.md §9).
+    # V2 memory + heartbeat layer (per V2 shot schema spec §9).
     # Heartbeat tracks current project state for session-start awareness.
     # Bin summary is the machine's "first impression" briefing of the bin.
     if not session_only and manifest["successful_clip_count"]:

package/docs/design/control-panel-polish-gameplan.md

@@ -1,238 +0,0 @@
-# Control Panel Polish — Gameplan
-
-Tracks the round of UI/UX work that started 2026-05-19 after removing Batch
-Jobs / Job Detail from the Analysis menu. The work is sequenced so that the
-visual-design system from Phase 1 gets reused by every later phase, and so that
-schema/server changes land before the UI that consumes them.
-
-Source-of-truth: the user. This doc is a living checklist — strike items as
-they ship, append new ones surfaced during execution.
-
----
-
-## Findings worth knowing before we start
-
-- **`analysis_summary_style` and `report_format` are dead code today.** Both
-  prefs are validated and threaded through the request envelope
-  (`src/server.py:5695,5696,7364-7369,8709-8710`), but nothing in
-  `src/utils/media_analysis.py` or anywhere downstream branches on them. We can
-  rename the enum values without breaking behavior because there is no behavior
-  to break. The cost: renaming alone won't make summaries *act* different;
-  that's follow-up work.
-
-- **Two transcription settings exist and they don't sync.**
-  `Preferences › Analysis › Transcription default` (`prefTranscriptionDefault`,
-  server-wide, default `"yes"` at `src/server.py:5676`) is the real default.
-  `Preferences › Dashboard Convenience › Transcription` (`prefTranscription`,
-  browser-local checkbox, default off) was the per-run override for the
-  now-deleted batch composer. The browser-local one no longer has a UI
-  consumer; it only feeds the generated MCP prompt in `promptPayload()`
-  (`src/analysis_dashboard.py`).
-
-- **`timed_markers_default` defaults to `"yes"`** (`src/server.py:5673`). The
-  dropdown showing "yes" is not a UI bug — it reflects the actual server
-  default. The user has asked to flip this to `"ask"`.
-
-- **Resolve product/version are not in the boot payload.** `/api/boot` returns
-  capabilities, project info, output roots, but does not call
-  `GetProductName() / GetVersionString() / GetCurrentPage()` on the Resolve
-  handle. `_connect_resolve_read_only()` already returns the handle — easy to
-  extend.
-
-- **Package version source** is `package.json:3` (`"2.23.1"`).
-  `src/utils/update_check.py` already has `check_for_updates()` and writes to
-  `update_state.json`. The plumbing exists; the dashboard just doesn't surface
-  it yet.
-
-- **Browser file-system picker reality check.** `showDirectoryPicker()` exists
-  but is Chromium-only and requires HTTPS or `localhost`. The dashboard runs on
-  `localhost` so it's usable, but we need a graceful fallback for
-  Firefox/Safari users — keep the text input as source of truth.
-
----
-
-## Phases
-
-### Phase 0 — Server-side flips (small, foundational)
-
-These are tiny but they unblock Phase 1's data and Phase 3's correctness.
-
-- [ ] **Flip `timed_markers_default` to `"ask"`** in
-      `_MEDIA_ANALYSIS_DEFAULT_PREFS` (`src/server.py:5673`). Existing
-      user-saved prefs are untouched; this only affects fresh installs and
-      `Reset Defaults`. Validate by running the dashboard, hitting Reset, and
-      confirming the dropdown lands on "ask".
-- [ ] **Add Resolve identity to `/api/boot`.** Extend the boot route in
-      `src/analysis_dashboard.py` to call `GetProductName()`,
-      `GetVersionString()`, `GetCurrentPage()` against the read-only Resolve
-      handle (use `_connect_resolve_read_only`). Add a `resolve` block to the
-      response. Null-tolerant when Resolve is offline.
-- [ ] **Add `/api/update/status` route.** Wraps
-      `src/utils/update_check.py:check_for_updates` and exposes
-      `{ current, latest, update_available, last_checked, snoozed_until }`.
-      Cache result for at least 5 minutes; never block the dashboard on
-      network.
-
-**Exit criteria:** Boot payload includes `resolve.product`,
-`resolve.version_string`, `resolve.page`. `/api/update/status` returns a
-sensible payload offline (no exceptions). Fresh server prefs file shows
-`timed_markers_default: ask`.
-
----
-
-### Phase 1 — Status-pill design system + Diagnostics restyle
-
-This is the foundation for every later visual change. We build the components
-once on Diagnostics, then reuse them in Overview rows and (later) the Analyze
-header.
-
-- [ ] **Define status-pill primitives.** Three classes:
-      `pill-ok` (green, var(--accent-success)), `pill-warn` (amber,
-      var(--accent-warning)), `pill-err` (red, var(--accent-error)). A
-      `pill-icon` slot for an inline 12px SVG.
-- [ ] **Define `diagnostic-card`.** Compact card with: header (icon + title
-      + status pill), 2–4 KV rows beneath, optional bottom action row. Reuses
-      the existing `--lab-panel-bg` / `--lab-panel-elevated` tokens.
-- [ ] **Restyle Resolve diagnostics.** Replace the single `info-list` with a
-      grid of cards:
-      - **Connection** card: status pill + product name + version + page
-      - **Project** card: name + clip counts + warnings
-      - **Inventory** card: total / source / hidden / sequences
-- [ ] **Restyle Storage diagnostics** as cards (Analysis root / Index DB /
-      Jobs DB) with pills for "indexed / stale / missing".
-- [ ] **Restyle Tools diagnostics** so each detected tool is a chip with a
-      version line and a status pill — denser than today's `tool-row` layout.
-
-**Exit criteria:** Diagnostics page scans at a glance. Color encodes
-correctness; the eye can find a problem without reading every label.
-
----
-
-### Phase 2 — Overview rows visual upgrade
-
-Reuses Phase 1 primitives. No new components needed.
-
-- [ ] Convert the four overview metric cards to use the diagnostic-card
-      shell (consistent visual language).
-- [ ] Replace the flat `info-list` below the cards with a status-pill
-      grid: every row gets a leading icon and a pill that reflects health
-      (e.g. *Search index: indexed* in green, *Clip media status: 3 missing*
-      in amber).
-- [ ] Add a tiny meter for "X analyzed of Y source clips" so progress is
-      visible without math.
-
-**Exit criteria:** Overview communicates state without requiring the user to
-read every word. Green/amber/red dominates the scan path.
-
----
-
-### Phase 3 — Untangle Preferences (the big consolidation)
-
-Touches Analysis, Dashboard Convenience, Storage, and Paths & Workflow.
-
-- [ ] **Delete `Preferences › Dashboard Convenience` as a separate page.**
-      Keep only the fields that still feed live UI:
-      - `prefPollInterval` and `prefAutoPoll` → move to the Analyze page
-        header as inline controls.
-      - `prefDepth`, `prefFrames` → optional; consider moving to Analysis prefs
-        as "Default depth" / "Default sample frames" since they feed the
-        prompt and arguably *are* analysis defaults.
-      - `prefJobName`, `prefRecursive`, `prefTranscription` → delete. Job
-        name can default to "Editorial analysis pass" without a pref.
-        Recursive is no longer surfaced. Transcription is owned by
-        Preferences › Analysis.
-- [ ] **Merge `Preferences › Storage` into `Preferences › Paths & Workflow`.**
-      The Storage page becomes a "Where files live" section at the bottom of
-      Paths & Workflow, rendered as diagnostic cards (reuses Phase 1).
-- [ ] **Add a "Browse..." button** next to `prefPreferredAnalysisRoot` and
-      `prefPreferredGeneratedMediaFolder`. Uses `showDirectoryPicker()` when
-      available; falls back to plain text input. Show a dropdown of recently
-      used project roots sourced from `state.projects.related_project_roots`.
-- [ ] **Rename summary-style enum**: `concise / assistant_editor / qc /
-      producer / full` → `full / concise / creative / technical`. Update:
-      - `_MEDIA_ANALYSIS_DEFAULT_PREFS` (`src/server.py:5695`)
-      - normalizer at `src/server.py:5923`
-      - schema enum at `src/server.py:8709`
-      - error message at `src/server.py:8917`
-      - dashboard `<select>` options (`src/analysis_dashboard.py:2408`)
-      - dashboard help text (`src/analysis_dashboard.py:2788`)
-      - default value: `"concise"` is fine to keep.
-- [ ] **Discuss/add new Analysis prefs.** Open questions for the user:
-      - Default source-trust mode (the conservative-descriptions feature
-        flagged in `feedback_conservative_descriptions.md`). Worth a UI
-        toggle?
-      - Default analysis depth (would replace the Dashboard-Convenience
-        depth).
-      - Default sample frame budget (same).
-
-**Exit criteria:** One Transcription setting, in one place. Paths & Workflow
-shows where files live. Storage page is gone from the menu. Dashboard
-Convenience is gone from the menu. Summary-style dropdown reads
-`full / concise / creative / technical`.
-
-**Follow-up (not blocking this phase):** wire the renamed summary styles into
-actual prompt construction so they produce distinguishable output. Today they
-are stored and forgotten; renaming alone changes nothing downstream.
-
----
-
-### Phase 4 — Navbar version badge + update flow
-
-- [ ] **Read `package.json` at server start**, expose `version` on the
-      `/api/boot` payload.
-- [ ] **Render version as a navbar badge** next to the wordmark. Style: pill
-      with `--accent-brand-muted` background; chevron when an update is
-      available.
-- [ ] **Poll `/api/update/status` on dashboard boot** and at most once per
-      hour after that. Render a small "Update available → 2.24.0" decoration
-      on the badge when applicable.
-- [ ] **Click on the badge opens a brand-styled modal** (clone of
-      `projectSwitchModal` at `src/analysis_dashboard.py:2556`). Modal shows
-      current → next version, release notes link (if available), and
-      Cancel / Update buttons. **Defer** the actual `pip install -U` /
-      `npm install -g` kickoff — for v1, the modal can offer a "Copy update
-      command" button. Self-updating a running server is a footgun; we'll
-      design that separately.
-
-**Exit criteria:** Users see the current version at all times, get a clear
-indicator when a release is available, and have a one-click path to learn
-how to update.
-
----
-
-### Phase 5 — Polish pass
-
-Stuff we'll likely find as we work through the above.
-
-- [ ] Audit `setText('promptSourceSummary'/'promptSelectedSummary'/...)` no-op
-      calls left over from the Batch Jobs removal. Either re-attach them to a
-      surface on the Analyze page or delete them.
-- [ ] Verify the post-Batch-Jobs `promptPayload()` still works end-to-end
-      after Dashboard Convenience moves. Run the Analyze page's
-      "Copy Prompt" / "Analyze in Codex" once and confirm the generated
-      prompt is well-formed.
-- [ ] Add a small status-pill legend somewhere on Diagnostics so the
-      green/amber/red language is discoverable.
-
----
-
-## Out of scope (intentionally)
-
-- Wiring the renamed summary styles into actual prompt construction
-  (separate engineering task — needs prompt-engineering work, not UI work).
-- Self-updating the running MCP server from the dashboard
-  (separate safety design).
-- Touching the V2 Review surface — already shipped in the fourth push.
-- Any change to the Analyze page's clip table — out of scope for this round.
-
-## Open questions
-
-1. **Source-trust default as a pref?** You flagged conservative descriptions
-   in `feedback_conservative_descriptions.md` and it's now a `source_trust`
-   param. Should this surface as a UI default in Preferences › Analysis?
-2. **Depth and Sample Frames — move them or delete them?** They feed the
-   generated MCP prompt but the user can also pass them per-call in chat.
-   Are these worth keeping as UI prefs?
-3. **Brand styling for the update modal.** We have one modal pattern
-   (`projectSwitchModal`). Do you want a distinct visual treatment for
-   update prompts, or keep them visually consistent with project switching?