Coming from another tool

This is about files and sessions on this machine.

Picked up automatically

You do not have to copy these by hand. matcha inspect shows what landed and which vendor it came from.

Rules and instructions

• AGENTS.md (and Agents.md, AGENT.md)
• CLAUDE.md, Claude.md, CLAUDE.local.md
• *.md under .matcha/rules/, .claude/rules/, .cursor/rules/
• Home copies under ~/.matcha/rules/, ~/.claude/rules/, ~/.cursor/rules/

Deeper files win when instructions conflict. .gitignore skips ignored rule **files**; skill roots do not use gitignore.

Skills and custom commands

• ~/.claude/skills/, ~/.claude/commands/
• ~/.cursor/skills/
• Project twins (.claude/, .cursor/, .matcha/, .agents/)
• Flat command .md files become slash commands

MCP servers

• ~/.claude.json
• .cursor/mcp.json (user and project)
• Project .mcp.json

Hooks

• .claude/settings.json (and settings.local.json)
• .cursor/hooks.json
• Matcher aliases such as Bash still fire

Turn a vendor surface off in ~/.matcha/config.toml:

[compat.claude]
mcps = true
skills = true
hooks = true
rules = true

[compat.cursor]
mcps = true
skills = true
hooks = true
rules = true

Environment equivalents: MATCHA_CLAUDE_MCPS_ENABLED, MATCHA_CURSOR_SKILLS_ENABLED, and the other MATCHA_*_*_ENABLED cells documented with configuration.

One-step Claude import: `/import-claude`

/import-claude

No arguments (extra text is ignored). The command opens a checkbox preview of importable items from ~/.claude / .claude — permissions, environment variables, MCP servers, hooks, and paths.

Confirm writes the selected items into your .matcha config. Re-run anytime. An empty scan shows “No Claude settings found to import.” Dismissing the welcome prompt records that you opted out of silent .claude fallback for that content.

Continue a foreign session

Bundled skills (when local skills load) expose:

/resume-claude
/resume-codex
/resume-cursor

Use them to continue a recent session from that tool **in this Matcha CLI session**. They are skills, not a cloud sync of those products.

Check what was discovered

matcha inspect
matcha inspect --json

Expect rules files (path + token estimate), skills with source tags, and MCP servers tagged [claude] or [cursor] when they came from compat paths.

What not to do

• Do not treat an old xAI / Grok credential as a MatchaCode account. Import it only as an **xAI Provider** key if you want that Provider.
• Do not use /marketplace to install what you used in another product. Install a local plugin folder instead.
• Do not expect /flush or /dream to recreate another tool's memory pipeline. Use /remember and the local store.

Things you may have missed: /btw asks a side question without interrupting the current task; /rewind rolls the conversation back (file changes stay on disk).

What you should see