FamReynaBrain/projects/paseo_integrations_research.md

Paseo Integrations Research — 2026-07-29

Context

User saw two cards in Paseo Desktop app:

• Command line — Control and script agents from your terminal
• Orchestration skills — Teach your agents to orchestrate through the CLI

Both are part of getpaseo/paseo v0.2.3.

1. Command line integration

What it is: The paseo CLI is a full client to the Paseo daemon. Everything the desktop/mobile apps do, you can script from terminal.

Install: npm install -g @getpaseo/cli → paseo onboard or paseo daemon start

Key commands (from README + dist/commands/):

• paseo run "<prompt>" — create and start an agent
  • --provider claude/opus-4.6, codex/gpt-5.4, copilot, opencode, pi
  • --mode plan|default|..., --thinking, --model
  • --new-workspace local|worktree + --worktree-mode branch-off|checkout-branch|checkout-pr + --new-branch, --base, --branch, --pr-number
  • --workspace <id>, --cwd <path>, --env KEY=VAL, --label, --image, --output-schema
  • --background / --wait-timeout 5m
• paseo ls --json — list agents
• paseo attach <id> — stream live output
• paseo send <id> "follow-up"
• paseo stop/archive/inspect/logs/wait
• paseo --host workstation.local:6767 run "..." — run on remote daemon
• paseo workspace create/ls/archive
• paseo script ls/start/stop — runs paseo.json scripts supervised
• paseo schedule create --cron "*/15 * * * *" --provider claude "..."
• paseo heartbeat create --cron "..." "check PR #42"
• paseo loop run --verify-check "npm test" --max-iterations 10 --sleep 2m "..." — Ralph loop primitive
• paseo daemon status/start/stop/restart/pair
• paseo hub connect <offer-url> / status / disconnect

Why useful for homelab: Can bash-loop across .110/.124/.102/.119 hosts, CI integration, cron orchestration from .126 Pi.

Example: PASEO_HOST=192.168.68.110:6767 paseo run --provider claude/sonnet "deploy the docker compose stack"

2. Orchestration skills

What it is: Agent Skills (Claude Code skills standard) that teach your coding agent to use Paseo to spawn other agents. It's meta-orchestration: inside a Claude Code / Codex session, you type /paseo-* and the agent uses Paseo tools/CLI to delegate.

Install: npx skills add getpaseo/paseo — installs into ~/.claude/skills/ or similar.

Skills directory from github.com/getpaseo/paseo/skills/:

• paseo (base) — reference skill: teaches workspaces, workspace scripts, agents, provider discovery, schedules, heartbeats, waiting semantics, CLI mapping, and ~/.paseo/orchestration-preferences.json (providers map: impl, ui, research, planning, audit + freeform preferences). MUST be read first.
• paseo-handoff — /paseo-handoff [--provider X] [task] — hands off to fresh agent with self-contained briefing (Task/Context/Relevant files/Current state/What was tried/Decisions/Acceptance/Constraints). Stays in subagent track until user detaches.
• paseo-loop — /paseo-loop — worker/verifier loop via paseo loop run. Supports --verify-check (shell) and --verify (LLM judge), --provider + --verify-provider (different families catch blind spots), --sleep, --max-iterations, --max-time, --archive. For babysitting PRs: gh pr checks --fail-fast. For heartbeat vs loop vs schedule distinction.
• paseo-advisor — /paseo-advisor [--provider] <question> — single agent second opinion, analysis-only (ends with "Do NOT edit..."). Contrasts provider for fresh perspective. Can forward other skills /unslop. Waits, synthesizes.
• paseo-committee — /paseo-committee — 2 high-reasoning agents, contrasting providers, root-cause analysis, planning only, no edits. Phases: Plan (both in parallel, must read both, challenge), Implement (you or impl agent), Review (diff review). ~10 iter without convergence → fresh committee.

Preference file: ~/.paseo/orchestration-preferences.json

{
  "providers": { "impl": "codex/gpt-5.4", "ui": "claude/opus", "research": "codex/gpt-5.4", "planning": "codex/gpt-5.4", "audit": "codex/gpt-5.4" },
  "preferences": ["Claude Opus is right for artistic/human-skill tasks, Codex for mechanical work"]
}

Skills must read this file before create_agent. No hardcoded providers.

Bundle path: Desktop app bundles CLI at /Applications/Paseo.app/Contents/Resources/bin/paseo (mac) → symlinked to ~/.local/bin/paseo.

Fleet status 2026-07-29

All daemons installed and reachable via relay:

• aeropi5 .126: srv_tiVh-B58uFpG - original Hermes host (this agent)
• imac .124 adolforeyna-iMac11-3: srv_J-2ulbATSCWw - Daughter Inc (already existed)
• Mac-mini-M4 .102: srv_jXWNo2jS9wrR - newly installed, node 26.3.0, no CC/Codex providers yet
• FamReynaServer .110 adolforeynaserver: srv__J7VJt0qZQkO - newly installed, node 25.6.1 via nvm v22.23.2 base, docker+ollama present
• emiserver .119 aeroreyna: srv_-QueoZDel-3B - newly installed, node 24.13.1 via nvm

Next to pair to laptop: desktop app Settings → Add Daemon → scan QR from paseo daemon pair on each host. Or paseo hub connect <offer-url>.

For Hermes skill integration: create ~/.hermes/skills/paseo that wraps paseo ls, paseo run, paseo send, etc., with capability routing per original plan: browser→.124, image→.102, docker/build→.110, heavy-llm→.110, light/cron→.126.