EM Kit CLI

The EM Kit CLI lets you query and update EM Kit data from your terminal.

• Works with the EM Kit desktop app runtime.
• If EM Kit is not running, the first CLI command launches it automatically.
• Supports both one-shot commands and an interactive TUI.
• Focuses on EM Kit local data (no GitHub CLI replacement).

Install from EM Kit desktop

1. Open Settings -> Command Line Tool.
2. Click Install Command Line Tool.
3. Confirm the install location.

On macOS, the default install directory is:

~/.emkit

The executable path is typically:

~/.emkit/emkit

Add to PATH

If you see CLI install directory is not in PATH, add the install directory to your shell PATH.

zsh (default on macOS)

echo 'export PATH="$HOME/.emkit:$PATH"' >> ~/.zshrc
source ~/.zshrc

bash

echo 'export PATH="$HOME/.emkit:$PATH"' >> ~/.bashrc
source ~/.bashrc

fish

fish_add_path $HOME/.emkit

Verify:

which emkit
emkit help

EM Kit MCP

If you want to connect EM Kit to Claude Code, Cursor, or Codex through MCP, use the dedicated guide:

• EM Kit MCP

Usage modes

One-shot commands

emkit doctor
emkit workspace list
emkit member list --workspace-id 1
emkit ai workspace-summary --workspace-id 1
emkit ai feedback --workspace-id 1 --status to_share
emkit issue list --workspace-id 1 --status todo,in_progress

Interactive TUI

emkit
# or
emkit tui

TUI supports:

• Tab autocomplete
• Up/down history
• help and quit

Common commands

emkit doctor
emkit mcp

emkit ai workspace-summary --workspace-id 1
emkit ai team-members --workspace-id 1 --limit 20
emkit ai feedback --workspace-id 1 --status to_share
emkit ai daily-notes --workspace-id 1 --days 14
emkit ai work-log --workspace-id 1 --days 14
emkit ai latest-review-period --workspace-id 1

emkit workspace list
emkit workspace get --id 1
emkit workspace create --name "Platform"
emkit workspace update --id 1 --name "Platform Team"
emkit workspace delete --id 1

emkit member list --workspace-id 1
emkit member get --id 2
emkit member create --input '{"workspace_id":1,"name":"Jane Doe"}'
emkit member update --id 2 --input '{"name":"Jane D."}'
emkit member delete --id 2

emkit issue list --workspace-id 1
emkit issue list --workspace-id 1 --status todo,in_progress
emkit issue list --workspace-id 1 --priority urgent,high --assignee-type me
emkit issue get --id 5
emkit issue create --input '{"workspace_id":1,"title":"Fix login bug","priority":"high"}'
emkit issue update --id 5 --input '{"status":"in_progress"}'
emkit issue delete --id 5

emkit report history --workspace-id 1
emkit report get --report-id 12
emkit report delete --report-id 12

emkit db query --sql 'SELECT id, name FROM workspaces LIMIT 10'
emkit db exec --sql 'UPDATE workspaces SET name = ? WHERE id = ?' --params '["Platform",1]'

JSON output

CLI responses are JSON, which makes it easy to consume from scripts and AI agents.

{
  "ok": true,
  "command": "workspace list",
  "data": [
    { "id": 1, "name": "Platform", "created_at": "2026-03-06 19:21:00" }
  ]
}

Use compact output when needed:

emkit workspace list --compact

Troubleshooting

CLI install directory is still reported as not in PATH

1. Make sure your shell config contains $HOME/.emkit (or your selected install directory).
2. Open a new terminal window (or source your shell config).
3. Check current PATH:

echo $PATH

4. Re-run Refresh in EM Kit Settings -> Command Line Tool.

Install directory is not writable

Create the directory and set ownership:

mkdir -p ~/.emkit
chown -R "$USER" ~/.emkit

Then install again from EM Kit Settings.

Development mode behavior

If EM Kit is running via npm run dev:electron, the installed dev launcher can target your dev app runtime. Keep the dev app running while testing terminal commands.