puter/paseo
1
0
Fork 0
mirror of https://github.com/getpaseo/paseo.git synced 2026-07-29 12:01:31 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
8e6455f1d60ea6112ee733cb6391bdfc55437207
paseo/public-docs/providers.md
Mohamed Boudra 8e6455f1d6 docs: add workspaces page explaining project/workspace/session model 
Adds a new conceptual Workspaces doc that explains how Paseo organizes work around projects, workspaces, and sessions. Reframed the existing Git worktrees page as the technical deep-dive it always was. Updated glossary with agent session and tab terminology. Reordered docs nav so workspaces and worktrees come before providers.
2026-06-10 15:50:19 +07:00

1.7 KiB
Raw Blame History

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

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, 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). 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.
  • Custom providers, add your own provider, point an existing one at a different endpoint, run multiple profiles, or override the binary in ~/.paseo/config.json.
  • paseo.sh/agents, per-agent landing page for each supported provider.