Paseo

Paseo is a self-hosted control plane for coding agents that lets you run and supervise agent CLIs like Claude Code and Codex remotely from your phone, desktop, or terminal. Maintained by a solo independent developer, its core is open source and free, focused on remote oversight so you can keep watch even away from your desk.

Core Capabilities

• Multi-Provider Orchestration: Native support for Claude Code / Codex / OpenCode / Pi, plus roughly 35 agents including Copilot, Cursor, and Gemini CLI via ACP
• Cross-Platform Parity: Desktop, web, CLI, and native iOS / Android share one daemon, with mobile features aligned to desktop
• Remote Connections: End-to-end encrypted relay (the daemon is outbound-only) or direct LAN connection with no open ports
• Zero Upstream Modification: Launches upstream CLIs as subprocesses without extracting credentials or calling inference APIs, preserving subscriptions and configuration
• Developer Primitives: TypeScript SDK, built-in MCP server, plugin system, cron, and Git worktree isolation
• Privacy First: No telemetry, no tracking, no login required, and local voice stays on-device by default

Use Cases Individual developers and small teams already using CLI agents; remote-supervision users who need to monitor, approve, and append instructions away from their desks; and technical users with a VPS / NAS who prefer self-hosting. Not a fit if you need vendor SLAs or a purely zero-configuration setup.

Unique Strengths Rare among peers, it treats the phone in your pocket as a first-class citizen, with mobile already GA and feature-aligned with desktop; the core is Apache-2.0, completely free with zero lock-in, while Conductor ($50/month) and Superset keep core capabilities behind paywalls.

Editorial Review With 18.7k GitHub stars, 15k+ weekly downloads, and a 4.85 App Store rating, this is a genuinely active product. But the risks must be named: the maintainer is a self-employed individual in Spain with no corporate entity as backstop and a bus factor of 1; it remains in a fast-changing pre-1.0 phase; and the daemon defaults to trusting anything network-reachable—binding to 0.0.0.0 exposes your full development environment and credentials, so hardening is on you.