paseo-help

Diagnose Paseo setup, connectivity, provider, and update issues using current documentation.

15.7k|1.7k|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/getpaseo/paseo --skill paseo-help
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paseo-help
Source: https://github.com/getpaseo/paseo/tree/main/skills/paseo-help
Command: npx skills add https://github.com/getpaseo/paseo --skill paseo-help

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users running Paseo often hit configuration, connectivity, provider, or version-skew problems and need accurate answers grounded in current documentation rather than guesswork. This Skill answers Paseo product questions directly, verifies them against the live docs, and guides structured troubleshooting.

Core Features & Use Cases

  • Documentation-grounded answers: Fetches the live docs index at paseo.sh/llms.txt and the relevant Markdown page before answering setup, configuration, or troubleshooting questions.
  • Topology-aware diagnosis: Identifies whether the daemon is desktop-managed, standalone, or Docker-based, and how the client connects (local, relay, LAN/VPN/Tailscale, or web UI) before diagnosing.
  • Read-only diagnostics: Uses commands like paseo daemon status --json and paseo provider diagnostic <provider> --json plus known log and config paths to pinpoint issues without changing state.
  • Use Case: A user reports that Claude Code is missing in the desktop app. The Skill identifies the affected daemon host, runs the provider diagnostic, compares the daemon PATH with a fresh login shell, and links the relevant troubleshooting doc.

Quick Start

Ask the assistant to explain why a provider is not detected in Paseo and have it diagnose the affected daemon using the current documentation.

Frequently Asked Questions about paseo-help

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Paseo when a provider is not detected?

Run paseo provider diagnostic <provider> --json against the affected daemon host, or open Settings → your host → Providers → provider → Diagnostic. Compare the resolved binary, daemon PATH, and provider version with a fresh login shell, since shell aliases are not executable paths.

How do I check the Paseo daemon status and version?

Run paseo daemon status --json on the daemon machine to see the server ID, hostname, version, home directory, listen address, log path, and whether the daemon is desktop-managed. Compare this with the app version under Settings → About.

Where are Paseo daemon logs and config files located?

By default the daemon config is ~/.paseo/config.json and the log is ~/.paseo/daemon.log, with agent state under ~/.paseo/agents/. Substitute the status-reported PASEO_HOME if it differs; in the official Docker image the default is /home/paseo/.paseo.

Does Paseo Desktop manage its own daemon?

Yes, Paseo Desktop bundles, starts, and updates a daemon on that computer with no separate install required. It can also connect to other remote standalone or Docker daemons at the same time, so always identify which host is affected before diagnosing.

Why does Paseo behave differently after an update?

App and daemon version skew causes many apparent bugs because fixes ship frequently. Compare the client app version with each connected daemon's version and update both through the correct topology-specific update path described in the docs.

What should I do if Paseo troubleshooting does not resolve my issue?

Collect app and daemon versions, OS, install method, connection method, the exact error, a minimal reproduction, and a small redacted log excerpt. Report bugs via GitHub Issues, or ask in the Paseo Discord for quick help.