Munk AI logoMunk AI
Install
Back to docs Munk AI
Munk AI
Product

Relationship with Munk Test

How Munk AI (desktop orchestration) and Munk Test (CLI verification) relate — and what each product owns.

Munk AI and Munk Test share a brand and a feedback story. They are two products, not two names for the same binary.

One-line split

ProductShapeOwns
Munk AIDesktop appWhen to plan, code, gate, deploy, verify, repair, and deliver
Munk TestCLI / Local API / MCP / Web UIDevice-level verification across Android, iOS, and Web

Munk AI is the orchestrator. Munk Test is a primary verify surface inside that loop — not the orchestrator itself.

How they connect

In a typical Munk AI run:

  1. Coding agents change the codebase under Host policy
  2. Gates (for example code gates) must pass before delivery side effects
  3. When UI verification is required, Munk AI drives Deploy → Verify
  4. Verify calls into a local Munk Test service (munk serve) over HTTP
  5. Pass opens delivery; fail can re-enter coding / repair under Host rules

You can use Munk Test without Munk AI (CI, QA, MCP, manual munk verify). You cannot replace Munk AI’s workflow ownership with Test alone.

What not to mix up

  • Docs under /docs/ai describe the desktop product
  • Docs under /docs/test describe the CLI verification engine
  • Marketing pages: / is Munk AI; /test is Munk Test

How to tell which product a guide belongs to:

  • Talks about munk serve, munk doctor, Local API, or the local 16888 Web UI → Munk Test
  • Talks about desktop Settings MCP / Skills / webhooks, Workbench, or Inbox → Munk AI
  • Both may mention “MCP”: on Test it is the verification runtime surface; on AI it is desktop config for coding agents

Next