miso-tui（味噌图伊）

miso-tui

Use this skill when configuring multi-process TUI display, task ordering, or concurrent tasks.

tui Field

Controls the terminal UI mode. Set at the top level of miso.json.

Auto-exit behavior: After all processes finish, the TUI waits 2 seconds then exits. By default, all buffered output is also dumped to stdout after the TUI closes. Set cleanExit: true to suppress that dump.

repo Field

Controls how miso discovers and orchestrates workspaces or pipeline tasks.

repo.tasks — Concurrent and Dependent Tasks

tasks is an object where each key is a script name. Configure ordering and concurrency:

dependsOn

Run upstream tasks before this one (topological order):

"repo": {
  "mode": "mono",
  "tasks": {
    "build": {
      "dependsOn": ["^build"]
    }
  }
}

"^build" means: run build in all upstream dependencies first. Without ^, it's a same-workspace dependency (rarely needed).

concurrent

Launch additional tasks alongside this one in the TUI:

"repo": {
  "mode": "turbo",
  "tasks": {
    "dev": {
      "concurrent": ["studio"]
    }
  }
}

Running miso dev will also launch studio as a TUI tab alongside it. concurrent tasks are always run by miso directly — they are not passed to turbo/nx even when mode is "turbo".

In "mono" mode, concurrent launches extra scripts from the root scripts/ folder alongside the workspace-distributed task. In "turbo" mode, concurrent launches extra scripts from the root scripts/ folder alongside miso's native dev orchestration (not turbo's).

Overriding a Turbo (or Nx) Task

When repo.mode is "turbo" or "nx", miso routes each command individually:

• Task name is in repo.tasks → miso runs it directly with its own TUI orchestration
• Task name is NOT in repo.tasks → miso delegates to turbo run <task> (or nx run-many)

This lets you pick exactly which tasks miso controls and which turbo handles.

Example: take over dev, keep turbo for everything else

Before (turbo handles dev — string shorthand):

{
  "repo": "turbo",
  "tui": "tabbed"
}

miso dev → delegates to turbo run dev; turbo parses output into TUI tabs.

After (miso handles dev — object form with tasks):

{
  "repo": {
    "mode": "turbo",
    "tasks": {
      "dev": {
        "concurrent": ["studio"]
      }
    }
  },
  "tui": "tabbed"
}

miso dev → miso discovers workspaces from package.json, launches dev + studio in parallel in TUI tabs directly. miso build and miso lint still delegate to turbo.

Minimum override (no extra config needed):

"tasks": {
  "dev": {}
}

An empty task entry is enough to make miso take over dev.

Full Example

{
  "$schema": "https://misojs.dev/miso.schema.json",
  "tui": "tabbed",
  "repo": {
    "mode": "turbo",
    "tasks": {
      "dev": {
        "concurrent": ["studio", "worker"]
      },
      "build": {
        "dependsOn": ["^build"]
      }
    }
  }
}

Common Mistakes

• repo: "turbo" without Turbo installed — Turbo must be in PATH; miso shells out to turbo directly
• dependsOn without ^ — "dependsOn": ["build"] means same-workspace dependency; use "dependsOn": ["^build"] for cross-workspace topological ordering
• Expecting TUI for a single process — the TUI only launches when multiple processes are involved (either monorepo workspaces or concurrent tasks configured)
• tui nested inside repo — tui is a top-level field, not under repo
• "repo": "turbo" when you want miso to run dev — string shorthand "turbo" fully delegates all tasks to turbo; to make miso handle specific tasks, use the object form with tasks: {"mode": "turbo", "tasks": {"dev": {}}}
• concurrent tasks going to turbo — concurrent tasks are always run by miso directly, even in "turbo" mode; they are not passed to turbo run