App Store
The daemon ships a builtin App Store panel at /store: a point-and-click
surface over the same verbs the MCP tools expose, so installing an app
(distribute an app) never requires a CLI session.
agentproto serve # then open http://127.0.0.1:<port>/store in a browser/store redirects to the panel's standalone UI
(/apps/@agentproto/store/ui). The panel is a daemon builtin, like the
sessions panel: nothing to install, and it always shows up under
app_catalog (category builtin).
What the shelf shows
- Installed: version, install source (local, git or
.agentapp), and anUpdate availablebadge whenapp_updatesreports one. Actions: Open (when the app has a UI), Update (app_resync), Uninstall (app_uninstall, with a confirmation). - Featured and Available: uninstalled catalog entries grouped by
category, with tier / placement / requires chips and an Install button
that pins the entry's own sha (
sha256for a bundle,shafor git). - Search and categories: a search box (name, app id, description,
publisher) and category chips filter every section. State lives in the URL
as
?q=and?cat=. - Icons: cards show the catalog entry's
icon, falling back to an initial-letter tile when the image is missing or blocked. - Install from URL: paste a
.agentappURL or a git repo URL; git entries take an optional ref and subdir. - Sources: warnings from unreachable catalog sources and offline state.
- Builtin panels: the daemon's own panels, collapsed.
App detail view
Click a card's title or icon to open ?app=<appId> (with a "← Back to store"
link). It shows the icon, publisher, version and update badge, license, tier,
size, origin and catalog, requires, the pinned source, the install and data
dirs (with a warning when one is missing), the app's agents and workflows, and
its last 10 runs. Install (with the same confirmation below), Update,
Uninstall and Open are available from there. A Copy block gives the equivalent
CLI commands and the exact app_install MCP arguments (builtin panels show
their MCP tool id / resource URI instead).
Install confirmation
Installing from the panel is always an explicit two-step confirmation: the first call answers a preview (URL, the pinned sha, and whether a build command would run) and installs nothing; the install only happens once you confirm in the dialog. Direct MCP and CLI calls keep the single-call behaviour; the confirmation applies only to installs driven from an app UI.
Deep link
Open the store with ?install=<appId> to pre-select and scroll to an entry
and open its install confirmation, so other pages (the empty states of the
apps tree, S7) can send a user straight to the shelf.
Related pages: distribute an app, app verb reference.