Sprint 9 closed: Desktop MVP

#devtools #tauri #ai #opensource

Sprint 9 is closed.

The goal was to ship the first desktop shell over Meronq's existing packages — a native window that connects a project, shows its handshake and memory, and manages the product MCP server. Sprint 8 explored productization; Sprint 9 turned the desktop track into running code.

What Sprint 9 delivered

Tauri 2 scaffold in apps/desktop — native window wrapping the web UI
Project folder picker → sets MERONQ_PATH for the connected project
Handshake and memory stats UI — vision, sprint, ADRs, and memory counts
MCP server lifecycle — start/stop with live status

The desktop is a shell over existing packages (@meronq/server-core, @meronq/memory, @meronq/mcp-server), consistent with ADR-0008.

Architecture

Web UI (Vite)  →  Node sidecar (HTTP :39281)  →  <project>/.meronq/
                   · handshake (server-core)
                   · memory stats
                   · spawn mcp-server

Tauri 2 (src-tauri/) adds the native window and folder picker; the same UI runs in the browser for fast iteration without compiling Rust.

Two ways to run it

Web dev (browser, no Rust): pnpm --filter @meronq/desktop dev
Tauri native (Rust): pnpm --filter @meronq/desktop tauri:dev

Web dev mode boots the sidecar and Vite UI on http://localhost:1420 and builds the server-core / mcp-server dependencies automatically on first run.

Connect → inspect → run

Empty folder → Initialize (creates README, package.json, .meronq/local)
Existing repo → Connect (handshake + memory stats)
Start MCP → spawns meronq-mcp with MERONQ_PATH set to the connected project