agentleFS
doublejdoublej/consult-user-mcp/dialog-cli-windows/CLAUDE.md

consult-user-mcp / dialog-cli-windows

CLAUDE.md39 starsChanged 4 months agoMITView on GitHub

The Windows counterpart to dialog-cli/. Ephemeral WPF process, spawned per dialog, prints the same JSON contract, exits. .NET 8, net8.0-windows, <UseWPF>true</UseWPF>. Cannot be built or run from macOS. See the windows-build skill. Mirrors the macOS structure deliberately, so a change on one side has an obvious counterpart on the other: DialogManager.Shared is the singleton, split into partial classes — one file per dialog type. DialogBase is the abstract WPF Window: borderless, dark, draggable. There is no skin seam here. That…

The file

Files
CLAUDE.md

Dialog CLI (Windows)

What this is

The Windows counterpart to dialog-cli/. Ephemeral WPF process, spawned per dialog, prints the same JSON contract, exits. .NET 8, net8.0-windows, <UseWPF>true</UseWPF>.

Cannot be built or run from macOS. See the windows-build skill.

Mental model

Mirrors the macOS structure deliberately, so a change on one side has an obvious counterpart on the other:

HeremacOS equivalent
Services/DialogManager.*.csServices/DialogManager+*.swift
Dialogs/*.csDialogs/SwiftUI*Dialog.swift
Components/DialogBase.csWindow/BorderlessWindow.swift + DialogContainer
Theme/DialogTheme.csTheme/Theme.swift
Services/SettingsReader.csUtilities/UserSettings.swift

DialogManager.Shared is the singleton, split into partial classes — one file per dialog type. DialogBase is the abstract WPF Window: borderless, dark, draggable.

There is no skin seam here. That is a macOS-only concept so far; DIALOG_SKIN is ignored.

Important invariants

  • The response JSON must match the macOS CLI exactly. mcp-server runs both through one DialogProvider interface and one compact.ts. A field named differently here is a silent bug on Windows only.
  • tweak and propose_layout do not exist here. WindowsDialogProvider throws before reaching this binary. Do not stub them into the command switch.
  • This directory cannot be renamed to dialog-cli/. It would collide with the macOS Swift CLI.
  • %APPDATA%\ConsultUserMCP cannot be renamed. Existing users' settings and snooze state live there.
  • JSON convention: camelCase names, string enum converter, nulls ignored on write.

Common change patterns

Porting a macOS dialog change → find the mirrored file from the table above. Keep the request and response models in lockstep; the models are the contract, the WPF layout is not.

Adding a dialog type → Program.cs command switch, Services/DialogManager.<Type>.cs, Dialogs/<Type>Dialog.cs, request/response models. Then the cross-platform checklist in .claude/rules/dialog-parity.md.

Verification

On the Windows machine only:

cd dialog-cli-windows
dotnet publish -r win-x64 --self-contained -p:PublishSingleFile=true
dialog-cli.exe confirm "{\"body\":\"test\",\"title\":\"t\"}"

Compare the printed JSON against the macOS CLI for the same input. That diff is the real test.

Related context

  • .claude/skills/windows-build/SKILL.md — SSH access, prerequisites, gotchas
  • ../dialog-cli/CLAUDE.md — the implementation this mirrors
  • ../windows-app/CLAUDE.md — the tray app that writes the settings this reads
  • .claude/rules/dialog-parity.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.