Skip to content

CLI Command Reference

Switch to Zen Mode

Launch the Mutsumi TUI task board.

Terminal window
mutsumi [OPTIONS] [COMMAND]
OptionShortDescriptionDefault
--path PATH-pPath to task file (default: ./mutsumi.json, fallback: ./tasks.json)
--watch PATH-wAdditional task file paths to watch (multi-project)
--versionShow version and exit
--helpShow help and exit
Terminal window
# Launch TUI (watches mutsumi.json in current directory)
mutsumi
# Watch a specific file
mutsumi --path /path/to/mutsumi.json
# Watch multiple files (multi-project)
mutsumi --path ~/proj-a/mutsumi.json -w ~/proj-b/mutsumi.json
# Print version
mutsumi --version

If this is your first launch, the onboarding wizard runs automatically. See Startup Flow for details.


Create a new task and append it to mutsumi.json.

Terminal window
mutsumi add TITLE [OPTIONS]
OptionShortTypeValuesDefault
--priority-Pchoicehigh, normal, lownormal
--scope-schoiceday, week, month, inboxinbox
--tags-ttext
--description-dtext
Terminal window
# Minimal
mutsumi add "Fix login bug"
# Full options
mutsumi add "Fix login bug" -P high -s day -t "bugfix,urgent" -d "Session expires on refresh"
# Short flags
mutsumi add "Write tests" -P low -s week -t "dev"

A unique ID and created_at timestamp are auto-generated.


List tasks from mutsumi.json.

Terminal window
mutsumi list [OPTIONS]
OptionShortTypeValuesDefault
--scope-schoiceday, week, month, inbox
--done / --no-doneflag
Terminal window
# List all tasks
mutsumi list
# Filter by scope
mutsumi list --scope day
# Only pending tasks
mutsumi list --no-done
# Only completed tasks
mutsumi list --done

Mark a task as done (supports ID prefix matching).

Terminal window
mutsumi done TASK_ID
ArgumentDescription
TASK_IDFull task ID or any unique prefix
Terminal window
# Full ID
mutsumi done 01JQ8X7K3M0000000000000001
# Prefix matching
mutsumi done 01JQ
# If prefix is ambiguous, Mutsumi lists matches
mutsumi done 01
# Error: Multiple tasks match '01'. Be more specific.

Sets status to "done" and auto-fills completed_at.


Edit an existing task’s fields (supports ID prefix matching).

Terminal window
mutsumi edit TASK_ID [OPTIONS]
OptionShortTypeValuesDefault
--titletext
--priority-Pchoicehigh, normal, low
--scope-schoiceday, week, month, inbox
--tags-ttext
--description-dtext
Terminal window
# Change title
mutsumi edit 01JQ --title "New title"
# Change priority and scope
mutsumi edit 01JQ -P low -s week
# Replace tags
mutsumi edit 01JQ -t "docs,review"
# Update description
mutsumi edit 01JQ -d "Updated requirements"

Remove a task from mutsumi.json (supports ID prefix matching).

Terminal window
mutsumi rm TASK_ID
ArgumentDescription
TASK_IDFull task ID or any unique prefix
Terminal window
mutsumi rm 01JQ

Removes the task and all its children.


Generate a template mutsumi.json.

Terminal window
mutsumi init [OPTIONS]
OptionDescription
--forceOverwrite existing file
--personalInitialize personal task file (~/.mutsumi/mutsumi.json)
--projectCreate mutsumi.json in cwd AND register as a project source
Terminal window
# Create mutsumi.json in current directory
mutsumi init
# Overwrite existing file
mutsumi init --force
# Initialize personal tasks
mutsumi init --personal
# Create and register as project
mutsumi init --project

Set up Mutsumi integration for an AI agent.

Terminal window
mutsumi setup [OPTIONS]
OptionShortTypeValuesDefault
--agent-achoiceclaude-code, codex-cli, opencode, gemini-cli, aider, custom
--modechoiceskills, skills+project-doc, snippetskills
ModeBehavior
skillsRemember preferred agent in config only. No files modified.
skills+project-docSave preference AND append integration instructions to the agent’s project doc (CLAUDE.md, AGENTS.md, etc.)
snippetPrint the integration prompt to stdout for manual pasting.
Terminal window
# List available agents and modes
mutsumi setup
# Skills-first (default -- no files modified)
mutsumi setup --agent claude-code
# Inject project doc into CLAUDE.md
mutsumi setup --agent claude-code --mode skills+project-doc
# Print prompt for manual use
mutsumi setup --agent custom --mode snippet
# Gemini CLI with project doc injection
mutsumi setup --agent gemini-cli --mode skills+project-doc

Running skills+project-doc again is safe — it detects existing sections and does not duplicate.


Migrate from legacy file names and config locations.

Terminal window
mutsumi migrate [OPTIONS]
OptionDescription
--configMigrate config from ~/.config/mutsumi/ to ~/.mutsumi/
--allMigrate both task file and config directory
Terminal window
# Migrate tasks.json -> mutsumi.json
mutsumi migrate
# Migrate config directory
mutsumi migrate --config
# Migrate everything
mutsumi migrate --all

Validate the task file schema.

Terminal window
mutsumi validate
Terminal window
# Validate default file
mutsumi validate
# Validate a specific file
mutsumi -p /path/to/mutsumi.json validate

Output the JSON Schema for mutsumi.json.

Terminal window
mutsumi schema
Terminal window
# Print schema to terminal
mutsumi schema
# Pipe to a file
mutsumi schema > schema.json

Manage registered project sources.

Terminal window
mutsumi project

Register a project directory as a source.

Terminal window
mutsumi project add PATH [OPTIONS]
OptionDescription
--nameDisplay name (default: directory name)
Terminal window
mutsumi project add .
mutsumi project add ~/projects/saas-app

Unregister a project source.

Terminal window
mutsumi project remove NAME
ArgumentDescription
NAMEProject name
Terminal window
mutsumi project remove saas-app

List all registered projects with their paths.

Terminal window
mutsumi project list

Commands that take a TASK_ID argument (done, edit, rm) support prefix matching. You don’t need to type the full ID:

Terminal window
mutsumi done 01EX # Matches if only one ID starts with "01EX"

If the prefix is ambiguous, Mutsumi lists matching tasks and asks you to be more specific.


CodeMeaning
0Success
1General error (file not found, ambiguous ID, etc.)
2Invalid arguments (click usage error)