@happyvertical/smrt-desktop
The versioned sidecar manifest, runtime bundler, installer builder, and plugin launcher for smrt desktop apps.
What it gives you
The versioned sidecar manifest, runtime bundler, installer builder, and plugin launcher for smrt desktop apps.
- 01A version 1 manifest names the executable, arguments, health route, data directory, and environment
- 02The bundler (smrt desktop bundle) writes the sidecar and a closed, timestamp-free report
- 03The builder (smrt desktop build) wraps the bundle in a Tauri installer, which is always unsigned
- 04The launcher gives an assistant plugin a local token from the running app
The sidecar manifest
The Rust wrapper reads the manifest before it starts the packaged Node executable. The parser rejects duplicate keys and reserved environment names. buildSidecarEnv builds the sidecar environment. The root entry and the bundler use only Node built-ins.
Sign-in belongs to the runtime
Owner sign-in and local MCP credentials belong to smrt-app-runtime: claimOwner, the loopback onboarding URL, and openLocalMcpTokenStore. This package does not duplicate them. The launcher is a thin client of that runtime and needs it as a dependency.
Release signing fails closed
A pull request build is unsigned and uses no secrets. The signing path refuses to start without every secret, a real updater key, a verified Node pin, and a real product identity. No default fills a missing value.
Examples
The tricia example packages smrt-app-shell as a desktop product. The generic-app example packages an app from the SvelteKit template with a placeholder identity.
Package UI
No UI layer to carry
This package stays focused on models, runtime behavior, or tooling. Build its interface with smrt-ui, or use a related domain package that exposes a /svelte entry point.
Intentionally headless
Package previews
No playground module yet
This package does not currently export a ./playground module. Its component names and import path remain available in the Components tab.
Intentionally not registered
Generated interface
REST
The exact route set comes from each model's @smrt({ api }) policy
and the application manifest—not from a second controller definition.
The package has no models. The bundler, builder, and launcher are Node-only entries. The smrt desktop bundle and smrt desktop build commands run the first two. An assistant plugin runs the launcher.
Generated interface
MCP
AI tools are generated from the methods you explicitly include. Their inputs are validated against the same model metadata used by REST and CLI.
The package has no models. The bundler, builder, and launcher are Node-only entries. The smrt desktop bundle and smrt desktop build commands run the first two. An assistant plugin runs the launcher.
Browser-native agent interface
WebMCP
The generated web definitions carry the same tool names, descriptions, and JSON Schema
inputs as MCP. smrt-web registers them with document.modelContext.
The package has no models. The bundler, builder, and launcher are Node-only entries. The smrt desktop bundle and smrt desktop build commands run the first two. An assistant plugin runs the launcher.
Generated interface
CLI
The app CLI turns manifest resources into predictable operator commands while keeping package-specific actions close to their models.
The package has no models. The bundler, builder, and launcher are Node-only entries. The smrt desktop bundle and smrt desktop build commands run the first two. An assistant plugin runs the launcher.