Files
paseo/public-docs/providers.md
T
Mohamed Boudraandmillerben95 8332f4d1ff feat(muse): add Muse Code as a built-in provider plugin (#5719)
* test(muse): record real host protocol fixtures

* feat(muse): add built-in MSP provider

Co-authored-by: millerben95 <millerben95@users.noreply.github.com>

* fix(muse): expose provider settings in the app

The daemon registered host settings without a client contribution, leaving sandbox, network, and workspace trust unreachable. Share the definition with a settings screen and expose it through Command Center even when installed plugins are disabled.

* docs(muse): publish setup and provider support

* test: correct runtime fixtures and restart readiness

* fix(muse): hide reminder housekeeping from the timeline

* fix(muse): use the official Muse Code mark

Source: https://muse.ai/images/favicon/app-squiggle.svg

Preserve the official silhouette path verbatim. Remove its gradient definition and use currentColor, scaling the original 100-unit coordinates into the 24-unit viewBox. Black silhouette renders match pixel-for-pixel.

* fix(muse): adapt to current plugin APIs

Use the screen API introduced with sidebar plugin items. Usage reports now come from source account discovery; remove the retired agent usage-reference request and headline marker, and exercise discovery through the existing provider fixtures.

---------

Co-authored-by: millerben95 <millerben95@users.noreply.github.com>
2026-09-30 14:56:41 +01:00

2.0 KiB

title, description, nav, order, category
title description nav order category
Providers How Paseo thinks about coding agents, wrapping existing CLIs, native vs ACP support, and where to go next. Providers 20 Providers

Providers

Paseo doesn't ship its own coding agent. It launches and supervises existing CLIs you've already installed and authenticated, Claude Code, Codex, OpenCode, Antigravity, Muse Code, Cursor, Gemini, and the rest. Your subscriptions, your config, your skills, your MCP servers all stay intact. Paseo just gives you a UI, a CLI, a relay, and orchestration on top.

Mental model

A provider is the contract between Paseo and one external agent CLI: how to launch it, how to stream its output, how to send input back, what modes it supports. The actual binary lives on your machine and runs as a normal subprocess.

Two tiers

  • Native support, Paseo ships a bundled adapter for the major agents (Claude Code, Codex, OpenCode, Pi, Antigravity, Muse Code). Auto-discovered when the underlying CLI is installed, with mode metadata and voice support where applicable.
  • ACP catalog, any agent speaking the Agent Client Protocol is supported through a generic adapter. Paseo ships a curated catalog of one-click installs (Cursor, Gemini, GitHub Copilot, Hermes, Kimi, Qwen Code, and 25+ more), and you can add any other ACP agent yourself.

Either way, you install the underlying CLI. Paseo runs it.

Where to go next

  • Supported providers, the full list with install links.
  • Agent profiles, save model, mode, and thinking settings together, with notes to guide delegation.
  • Custom providers, add your own provider, point an existing one at a different endpoint, configure multiple provider aliases, or override the binary in ~/.paseo/config.json.
  • paseo.sh/agents, per-agent landing page for each supported provider.