setup

MeiGen Plugin Setup

You are guiding the user through configuring the MeiGen plugin for image generation. Follow this flow step by step.

Step 0: Detect Platform

Before running any shell commands, detect whether you're on Windows. Many of the commands below assume a Unix shell (macOS / Linux / Git Bash). Quick check:

node -e "console.log(process.platform)"

• darwin / linux → Unix shell, use the commands as written
• win32 → Windows. Adjustments:
  • For 2>/dev/null in Step 1 (e.g. cat ... 2>/dev/null, ls ... 2>/dev/null): replace with 2>NUL in cmd or 2>$null in PowerShell. Or simpler: use a Node check instead, e.g. node -e "try{console.log(require('fs').readFileSync(require('os').homedir()+'/.config/meigen/config.json','utf8'))}catch{}"
  • For mkdir -p ~/.config/meigen: in PowerShell use New-Item -ItemType Directory -Force ~/.config/meigen. Or skip mkdir entirely — when you later call the Write tool with file_path: ~/.config/meigen/config.json, Claude Code's harness creates the parent directory automatically (Write creates the file, the parent dir is a side-effect).
  • Skip chmod 600 — NTFS has no chmod, and Windows file permissions are inherited from the parent directory.
  • For curl health checks (Step 3B-1, 3C): Windows 10+ has curl but lacks head -c; truncate with Select-Object -First 5 (PowerShell) or omit the truncation.
  • The config file lives at %USERPROFILE%\.config\meigen\config.json — Node's os.homedir() resolves ~ correctly when reading at runtime, so the config path in code works fine.

Step 1: Welcome

First, check if a config file already exists:

cat ~/.config/meigen/config.json 2>/dev/null

Also check for existing ComfyUI workflows:

ls ~/.config/meigen/workflows/*.json 2>/dev/null

If config exists, show the current configuration (mask API keys: show first 10 chars + "...") and any saved workflows. Ask if they want to reconfigure.

If no config exists, present this introduction: