mmsetup

name	mmsetup
description	Set up, reconfigure, or remove Memory Mason. Configures vault path, installs hooks if missing, or uninstalls everything. Use when the user says "set up memory mason", "install hooks", "configure memory mason", "reconfigure memory mason", "get memory mason running", "my hooks aren't working", "uninstall memory mason", "remove memory mason", or runs /mmsetup.

Memory Mason Setup

You are setting up or removing Memory Mason for the current session.

This command is operational only. Do not write /mmsetup, /memory-mason:mmsetup, or their execution chatter back into the vault.

Platform detection: Check the OS before running any scripts. Use bash / .sh scripts on macOS and Linux. Use powershell / .ps1 scripts on Windows. Never ask the user which OS they're on — detect it from the environment.

If the user says "uninstall", "remove", or "clean up" → skip to Uninstall section below.

---

Setup

Step 1: Detect Agent

Identify which agent you are running in:

• If CLAUDE_CONFIG_DIR or CLAUDE_PLUGIN_ROOT is set -> Claude Code
• If .github/hooks/session-start.json exists in workspace -> GitHub Copilot workspace install already done
• If ~/.copilot/hooks/memory-mason/ exists -> GitHub Copilot user-level already done
• If gemini-extension.json exists in workspace root -> Gemini CLI
• If ~/.codex/ or .codex/ exists -> Codex
• Otherwise -> skills-only host (Cursor, Windsurf, Cline, etc.)

Step 2: Check if Already Installed

For Claude Code: check ~/.claude/hooks/memory-mason/session-start.js exists AND ~/.claude/settings.json contains memory-mason hook entries. For Copilot: check ~/.copilot/hooks/memory-mason/session-start.js exists. For Codex: check ~/.codex/hooks/memory-mason/session-start.js exists. For Gemini CLI: check whether the extension is already installed or linked in the active Gemini extensions directory before reinstalling.

If already installed: report status and skip unless user says "reinstall" or "force".

Step 3: Configure Vault

Check if vault is already configured (file-based vault-path priority order):

1. .env in project root contains MEMORY_MASON_VAULT_PATH
2. memory-mason.json exists in project root
3. ~/.memory-mason/.env contains MEMORY_MASON_VAULT_PATH
4. ~/.memory-mason/config.json exists

If none found, ask user and create global config:

1. Ask: "What is the absolute path to your Obsidian vault?"
2. Ask: "What subfolder name should Memory Mason use? (default: ai-knowledge)"
3. Ask: "Enable deterministic assistant prose compression before vault writes? (default: no)"
4. Create ~/.memory-mason/config.json:

{ "vaultPath": "<input>", "subfolder": "<input>", "minimize": <true|false> }

Set minimize to true only when the user explicitly opts in (step-3 answer). Default is false.

minimize precedence (highest first): process environment variable MEMORY_MASON_MINIMIZE > .env file MEMORY_MASON_MINIMIZE > config.json key minimize. Process env overrides everything.

Step 4: Install Hooks (if missing)

Skip this step if hooks are already wired (plugin install or shell installer already ran).

Claude Code:

bash scripts/install/claude-code.sh
# Windows:
powershell -File scripts\install\claude-code.ps1

Or if no local clone:

bash <(curl -fsSL https://raw.githubusercontent.com/s-gryt/memory-mason/main/scripts/install/claude-code.sh)

GitHub Copilot:

bash scripts/install/copilot.sh
# Windows:
powershell -File scripts\install\copilot.ps1

Or remote:

bash <(curl -fsSL https://raw.githubusercontent.com/s-gryt/memory-mason/main/scripts/install/copilot.sh)

Codex:

bash scripts/install/codex.sh
# Windows:
powershell -File scripts\install\codex.ps1

Skills-only hosts (Cursor, Windsurf, Cline): no hook system available. Inform user that automatic session capture is not supported on this platform. Knowledge base commands (/mmc, /mmq, /mml, /mms, /mma) work once vault is configured.

Step 5: Configure Obsidian Graph View (optional)

Write .obsidian/graph.json — see references/obsidian-graph.md for template and field explanations.

Step 6: Verify

After setup, verify:

1. Config exists at ~/.memory-mason/config.json
2. If hooks were installed: hook runtime files exist in agent hooks dir
3. If hooks were installed: agent config is updated (settings.json / hooks.json)

Report success or troubleshoot any failures.

---

Uninstall

Guided removal of Memory Mason hooks and configuration. Vault content (daily logs, knowledge articles) is never deleted.

Step 1: Detect What's Installed

Check all locations:

• Claude Code hooks: ~/.claude/hooks/memory-mason/ and entries in ~/.claude/settings.json
• Claude Code plugin: ~/.claude/plugins/marketplaces/memory-mason/
• Copilot hooks: ~/.copilot/hooks/memory-mason/ and .github/hooks/ JSON files in workspace
• Codex hooks: ~/.codex/hooks/memory-mason/ and .codex/hooks.json in workspace
• Global config: ~/.memory-mason/config.json
• Project config: memory-mason.json or .env entries in project root

Report what was found and ask user to confirm removal.

Step 2: Remove Hooks

For Claude Code (shell install):

bash scripts/uninstall/claude-code.sh
# Windows:
powershell -File scripts\uninstall\claude-code.ps1

Or if no local clone:

bash <(curl -fsSL https://raw.githubusercontent.com/s-gryt/memory-mason/main/scripts/uninstall/claude-code.sh)

For Claude Code (plugin install):

/plugin uninstall memory-mason

For Copilot: remove ~/.copilot/hooks/memory-mason/ directory and any .github/hooks/ JSON files that reference memory-mason.

For Codex: remove ~/.codex/hooks/memory-mason/ directory and memory-mason entries from .codex/hooks.json.

Step 3: Remove Config

Ask user: "Also remove vault configuration? Your vault content will not be touched."

If yes: delete ~/.memory-mason/config.json. Remove memory-mason.json or Memory Mason entries from .env in project root if present.

Step 4: Report

List everything that was removed. Confirm vault content is untouched. Remind user to restart their agent for changes to take effect.