#MoonDesk

Desktop operator application · local single-user alpha. Read the product contract for capability-truth rules, pack hosting, current limitations and release gates.

MoonDesk is a pure MoonBit desktop host and Rabbita UI for browsing MoonBook workspaces, staging inbox notes, inspecting MoonFind-authored work, and reviewing MoonClaw run artifacts.

Current milestone slice:

workspace explorer, previews, raw links, search, favorites, and inbox writes/imports
MoonTown request ledger, standing-watch creation, town messages, live progress/events/review summaries, daemon lifecycle controls, and one-shot daemon tick dispatch
reusable PDF Evidence Watch publishing: a 7-step wizard creates a research-book with source websites, cadence, notification rule, method document, pdf-watch/pdf-analysis skills, schemas, generated site placeholders, a book-local config, MoonTown publish receipts, and a standing watch registration
portable app-tool export for books that carry generated miniapps/tools
saved views, selected-path tags, daily cadence calendar, ICS export, and outcome analytics for standing goals and watcher decisions
switchable MoonWiki/MoonCode workspace shell: MoonWiki for human-language projection of MoonBook-owned knowledge, MoonCode for book-scoped coding/chat sessions backed by the sole MoonClaw runtime
MoonFind-authored Work-graph inspection and composition: MoonDesk shows exact operation, schema, authority, claim, review, catalog, and validation evidence and sends only dependency-closed selections to MoonFlow
MoonBit-only desktop, bundle, release, and launch-agent commands; the default app bundle uses Lepusa as the native WebView host and supervises the MoonDesk MoonBit server as a localhost sidecar, with no Tauri/Rust app shell

MoonDesk is the human control and hosting surface, not another orchestration or agent layer. MoonFind owns discovery and desired graph intent; MoonFlow owns validation, scheduling, execution, reconciliation, and recovery; MoonGate owns exact capability and authority resolution; MoonClaw is the sole agent runtime; MoonBook owns MoonWiki and Bookkeeper; MoonTown owns civic coordination and reviewable cross-book synthesis.

Domain-specific examples are intentionally not MoonDesk core. They are standalone product packs that MoonDesk can create, configure, host, inspect, export, and launch through generic contracts. The validated MoonFind robotics reference has 63 stages and 43 exact operations across 11 domain products, but MoonDesk never hardcodes that inventory. MoonMini and MoonStat are not active graph products. Publication, trading, and physical robot commands require separate authority.

See docs/STATUS.md for the current completeness assessment. Short version: it is a usable local single-user alpha with a Lepusa-hosted native macOS app bundle; production distribution still needs a credentialed release channel.

Run locally:

npm --prefix ui/rabbita-desk run build
moon run cmd/main -- serve <workspace-root> --ui ui/rabbita-desk/dist --port 4199

Create the self-contained Lepusa native macOS app bundle:

moon run cmd/main -- bundle <workspace-root> --ui ui/rabbita-desk/dist --out dist --port 4199

Create a release manifest/notarization submission when credentials exist:

moon run cmd/main -- release <workspace-root> --ui ui/rabbita-desk/dist --out dist --port 4199 --notary-profile <profile>

Optional external services:

MoonDesk can browse and edit a workspace without sibling source checkouts. Starting or ticking the MoonTown daemon is optional and requires an explicit MoonSuite product-home descriptor at .moonsuite/products/moontown/service.json:

{
  "kind": "moondesk-town-service.v1",
  "cwd": "/absolute/path/to/moontown-runtime",
  "daemon": {
    "command": "/usr/local/bin/moontown",
    "args": ["daemon", "run"]
  },
  "tick": {
    "command": "/usr/local/bin/moontown",
    "args": ["daemon", "tick"]
  }
}

Without that file, daemon start/tick and town LaunchAgent creation return not-configured instead of assuming the workspace is a MoonTown source tree.

MoonCode can also launch MoonClaw from an explicit MoonSuite product-home descriptor at .moonsuite/products/moonclaw/service.json:

{
  "kind": "moondesk-moonclaw-service.v1",
  "cwd": "/absolute/path/to/moonclaw-runtime",
  "daemon": {
    "command": "/usr/local/bin/moonclaw",
    "args": ["daemon", "--port", "0"]
  }
}

Without that file, MoonDesk can still report an already-running MoonClaw daemon from its daemon-info file, but it will not discover, build, or launch a sibling MoonClaw source checkout.

Validation:

moon check
moon test
moon info
moon fmt
cd ui/rabbita-desk && moon check --target js

Source Files

moondesk.mbt

Site source Report issue Packages Build queue Skills Statistics