Orchestrate coding agents across desktop, mobile, and headless sessions with Paseo
Paseo runs a local daemon for Claude Code, Codex, Copilot, OpenCode, and Pi agents so operators can start, monitor, attach to, and hand off coding-agent work from desktop, mobile, web, or CLI clients.
npx skills add agentskillexchange/skills --skill orchestrate-coding-agents-across-desktop-mobile-and-headless-sessions-with-paseo
Use Paseo when an operator needs to coordinate multiple coding-agent sessions on their own machines, especially when work needs to move between a desk, phone, remote shell, or headless server. The upstream project provides a daemon, desktop/mobile/web clients, CLI commands such as paseo run, paseo ls, paseo attach, and paseo send, plus installable skills for handoff, loop, advisor, and committee workflows.
What this skill actually does
This is skill-shaped because the job is bounded: operate and coordinate coding agents through one local control plane rather than manually juggling separate terminals, devices, and provider CLIs. Invoke it for cross-device delegation, follow-up, acceptance-loop, or second-opinion workflows. It is not a generic mobile app listing, IDE replacement, agent framework, or broad project-management product card.
Inputs and prerequisites: At least one configured supported agent CLI such as Claude Code, Codex, GitHub Copilot CLI, OpenCode, or Pi; Paseo desktop app, mobile app, web client, Docker daemon, or the @getpaseo/cli package; local network or pairing access for cross-device clients..
Setup notes: For the desktop path, install Paseo from https://paseo.sh/download or the GitHub releases page and pair mobile devices from Settings. For CLI/headless use, run npm install -g @getpaseo/cli and then paseo to start the daemon and display a QR code. For containerized use, run the upstream Docker command with port 6767 , PASEO_PASSWORD , and persistent workspace/home volumes. Install the agent skills with npx skills add getpaseo/paseo when you want agents to invoke Paseo handoff, loop, advisor, or committee workflows.
Source and verification boundary: use https://paseo.sh/docs as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.