mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-04 23:44:41 +00:00
Odin Glynn-MartinandClaude Opus 5.5
0d0b89314e
The ACP shim only terminalized its own tool calls when a turn ended, so a running row published by a transformer stayed running after a cancel or failure. Track transformer tool rows and close them with the turn. A canceled turn also marked open tool calls failed with a null error, which the wire schema rejects, making the agent's timeline unfetchable. Cancel those rows instead, and give failed rows a non-null error. Add `hoplite` to the known ACP provider icon names so the catalog icon resolves without a snapshot SVG, and stop listing Hoplite under the promise that local MCP servers stay intact. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.2 KiB
2.2 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, Hoplite). Auto-discovered when the underlying CLI is installed, with mode metadata and voice support where applicable. Hoplite's CLI runs on your machine, but its agent works in a Hoplite cloud workspace, so your local MCP servers and Paseo tools are not available there.
- 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.