paseo-cafe

Name: paseo-cafe
Author: paseo-cafe

by paseo-cafe

Browse the paseo.cafe plugin catalog inside Paseo and install plugins without leaving the app.

Requires Paseo ^0.8.0productivity

9 starsLicense: Apache-2.0Last updated 09 Sep 2026 paseo-cafe/paseo-cafe

Community-submitted — not owned or vetted by paseo.cafe

This listing is generated automatically from the plugin's own public repository. We don't audit, endorse, or take responsibility for third-party plugin code. Paseo plugins are trusted, unsandboxed code with filesystem, process, and network access on the machine they run on — read the source at paseo-cafe/paseo-cafe before installing.

Caveats

Requires Paseo: ^0.8.0 — from this plugin's own paseo-plugin.json.

Installs plugins by running the paseo CLI on the daemon host
Browsing the catalog requires the daemon to reach the configured catalog URL

From the plugin's README

Plugins listed here are community-submitted and are not vetted by paseo.cafe. They are trusted, unsandboxed code on your daemon host: read the source before installing.
Installing shells out to the paseo CLI, so that binary must be on the daemon's PATH.
The composer attachment source always searches the default catalog. Paseo calls an attachment search with the query alone, and a plugin's server handler cannot read its own settings, so a custom Catalog URL applies to the sidebar surface only.
Catalog responses are cached on the daemon for five minutes. Refresh bypasses that cache.

Install

paseo plugin add paseo-cafe/paseo-cafe --path plugin

From the plugin's README

paseo plugin add paseo-cafe/paseo-cafe:plugin

Requires a Paseo 0.8 release; the manifest declares requirements.paseo as ^0.8.0.

By default the catalog is read from https://paseo.cafe/api/plugins. Point Settings → Plugins → Paseo Cafe at another deployment (a local bun run dev, a staging build, or a self-hosted fork) that serves the same shape. PASEO_CAFE_DIRECTORY_URL on the daemon is a lower-priority fallback for hosts that cannot persist plugin settings.

A custom catalog must use HTTPS, or HTTP on loopback (localhost, 127.0.0.0/8, [::1]). The catalog picks which repositories the install button hands to the paseo CLI, so anyone able to rewrite a plaintext response chooses what gets installed on the daemon host.

Health checks

Manifest ID matches registry
Has a README
Has a license
Has tests
Has a typecheck script
Updated in the last 6 months

Scanned 09 Sep 2026, 19:11 UTC from paseo-cafe/paseo-cafe/plugin.