What problem it solves

Coding agents often need to be coordinated across separate tools while developers also manage files, terminals, diffs, and pull requests. Paseo addresses this by bringing multiple agents and the development workflow into one interface, with self-hosted operation and access from desktop and mobile devices.

Key features

• Parallel agent orchestration — Run multiple agents concurrently, isolate each one in its own worktree, and allow agents to create worktrees, launch other agents, and communicate with them.

  Source: README

• Complete development workflow — Edit files, run terminals, review diffs, open pull requests, and use a built-in browser in configurable split panes.

  Source: README

• Multi-provider access — Use Claude Code, Codex, Copilot, OpenCode, Pi, Antigravity, and Muse Code through a shared interface, selecting a provider and model for each job.

  Source: README

• Cross-device clients — Connect desktop, mobile, web, and CLI clients to the local daemon, including the full native mobile app on iOS and Android.

  Source: README

• Extensible plugin system — Plugins run on the daemon and appear consistently in every connected client, with hooks for interface elements, agent lifecycle events, and additional providers.

  Source: README

Quick start

Copied verbatim from the project's README.

npm install -g @getpaseo/cli
paseo

paseo run --provider claude/opus-4.6 "implement user authentication"
paseo run --provider codex/gpt-5.5 --worktree feature-x "implement feature X"

paseo ls                           # list running agents
paseo attach abc123                # stream live output
paseo send abc123 "also add tests" # follow-up task

# run on a remote daemon; --cwd is a path on that host
paseo run --host workstation.local:6767 --cwd /workspace "run the full test suite"

Who it may suit

Inference: this may suit developers who want to coordinate multiple coding-agent providers through one workflow and who need to continue or inspect work from desktop, mobile, web, or terminal clients.

Topics to discuss

• Which agent orchestration patterns should receive first-class workflow support?

• How should plugins balance shared interfaces with daemon-specific capabilities?

• Which cross-device workflows deserve better documentation and examples?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/getpaseo/paseo#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.