# Paseo Help > Responde dudas sobre el producto y la app de Paseo: setup, configuración, conectividad, providers, workspaces, actualizaciones, logs y troubleshooting. Para operar agentes y workspaces por MCP o CLI, usa la skill paseo. Fuente: https://skillsagentes.com/skills/getpaseo/paseo/paseo-help Markdown: https://skillsagentes.com/skills/getpaseo/paseo/paseo-help.md Repositorio: https://github.com/getpaseo/paseo Autor: getpaseo Licencia: NOASSERTION Actualizado: hace 20 días Coste de contexto: 85 tok instalada, 1.6k tok al activarse, 1.6k tok con todos los archivos del bundle Bundle: 1 archivo, 6 KB Permisos que pide: ninguno declarado ## Instalación Un skill son archivos markdown: los mismos archivos valen para cualquier agente y lo único que cambia es el directorio de destino, es decir la bandera `--agent`. Añade `-g` para instalarlo en todos los proyectos de la máquina. ```bash # Claude Code npx -y skills add getpaseo/paseo --skill paseo-help --agent claude-code # Cursor npx -y skills add getpaseo/paseo --skill paseo-help --agent cursor # Codex npx -y skills add getpaseo/paseo --skill paseo-help --agent codex # Gemini CLI npx -y skills add getpaseo/paseo --skill paseo-help --agent gemini # Windsurf npx -y skills add getpaseo/paseo --skill paseo-help --agent windsurf # Cline npx -y skills add getpaseo/paseo --skill paseo-help --agent cline ``` ## Qué hace - Ayuda a entender, configurar o diagnosticar el propio Paseo, verificando cada respuesta contra la documentación pública actual e incluyendo su enlace. - Obliga a fijar la topología antes de diagnosticar: dónde y cómo corre el daemon (desktop-managed, standalone, Docker) y cómo lo alcanza el cliente afectado. - Aplica cada comprobación al runtime del daemon, no al dispositivo cliente: binarios de provider, credenciales, `PATH`, workspaces, config y logs viven en la máquina del daemon. - Empieza por comparar versiones de app y daemon y pedir actualización, ya que el desfase causa muchos fallos aparentes. - Usa comprobaciones de solo lectura (`paseo daemon status --json`, `paseo provider diagnostic`) y no reinicia, edita config ni expone la red sin permiso. ## Cuándo usarla - Un usuario dentro de Paseo pregunta cómo funciona, cómo configurarlo o por qué algo está roto. - Dudas de setup, conectividad, providers, workspaces, actualizaciones o logs. ## Cuándo no - Operar agentes y workspaces por MCP o CLI: usa la skill paseo. ## Qué la activa - "¿Por qué no conecta mi cliente con el daemon remoto?" - "¿Dónde están los logs del daemon de Paseo?" - "Me sale command not found para el provider de Codex en Paseo" - "¿Cómo actualizo Paseo si uso la imagen de Docker?" ## Archivos - SKILL.md — 6 KB ## SKILL.md Reproducido tal cual desde getpaseo/paseo bajo NOASSERTION. Esta sección es el documento original y está en inglés. # Paseo Help You are helping a user understand, configure, or troubleshoot Paseo itself. Answer their question directly, verify the answer against the current public documentation, and include the relevant documentation link. Do not send the user away to read the docs in place of helping them. **User's question:** $ARGUMENTS ## Use current documentation Fetch [https://paseo.sh/llms.txt](https://paseo.sh/llms.txt) first. It is the current index of Paseo documentation, with a description and Markdown URL for each page. Use that index to select the page that owns the user's question, then fetch the linked `.md` page before answering. For troubleshooting, begin with [Common problems](https://paseo.sh/docs/troubleshooting.md) and follow its links when the issue belongs to a more specific page. Prefer the deployed docs over memory. Answer the user directly, then link the relevant `.md` page as supporting documentation. ## Establish the topology first Identify the daemon involved before diagnosing versions, paths, providers, logs, updates, or connectivity. Do not infer the daemon from the client: Paseo Desktop can manage its bundled local daemon and connect to other remote daemons at the same time. Establish two facts: 1. **Where and how the daemon runs** - **Desktop-managed:** Paseo Desktop bundles, starts, and updates a daemon on that computer. No separate daemon install is required. - **Standalone:** the daemon was installed separately, commonly through the npm CLI, and runs independently of the desktop app. - **Docker:** the daemon, its home, provider CLIs, credentials, and code mounts live in the container runtime. 2. **How the affected client reaches it** - same-machine local connection - relay connection - direct LAN, VPN, or Tailscale connection - daemon-served web UI Use **Settings → About** to compare the app version with each connected host. For the affected host, open **Settings → your host → Overview → Full status**. On the daemon machine, `paseo daemon status --json` reports facts such as server ID, hostname, version, home, listen address, process owner, log path, and whether the daemon is desktop-managed. Record which host the user is viewing and which machine or container runs it. A local `paseo daemon status` describes the daemon for that CLI's local `PASEO_HOME`; it may not be the remote host visible in the app. Apply later checks to the daemon runtime, not automatically to the client device: - Provider binaries, credentials, `PATH`, workspaces, config, and daemon logs live on the daemon machine or inside its container. - App version and app logs live on the client device. - A desktop-managed daemon follows the Desktop app lifecycle and update path. - A standalone daemon follows its own CLI/npm lifecycle and may use a different `PASEO_HOME` or listen address. - A Docker daemon uses container paths, volumes, user permissions, image versions, and container lifecycle commands. ## Diagnose before changing state After identifying the affected host, compare that daemon's version with the client app version. Ask the user to update both through the correct topology-specific update path. Old versions and app/daemon version skew cause many apparent bugs, and fixes ship frequently. Use the Updates page and the installation-specific docs for current instructions. Use the smallest relevant read-only checks: ```bash paseo --version paseo daemon status --json paseo provider diagnostic --json ``` Use the status-reported home, listen address, and log path for further checks. Probe `http://127.0.0.1:6767/api/health` or read `~/.paseo/daemon.log` only when those values match the affected daemon. Do not restart the daemon, edit config, update software, or expose a network listener without the user's explicit permission. A daemon restart can interrupt the agent doing the diagnosis. For a missing provider or `command not found`, run `paseo provider diagnostic ` against the affected host, or open **Settings → your host → Providers → provider → Diagnostic**. Compare its resolved binary, daemon `PATH`, and provider version with a brand-new login shell. Shell aliases and functions are not executable paths. ## Logs and local files Use these defaults on the machine where the daemon or Desktop app actually runs. Do not look for a remote daemon's files on the client device. - Daemon config: `~/.paseo/config.json` - Daemon log: `~/.paseo/daemon.log` - Agent state directory: `~/.paseo/agents/` - Default managed worktree root: `~/.paseo/worktrees/` - macOS desktop log: `~/Library/Logs/Paseo/main.log` - Linux desktop log: `~/.config/Paseo/logs/main.log` - Windows desktop log: `%APPDATA%\Paseo\logs\main.log` Substitute the status-reported `PASEO_HOME` for `~/.paseo`. In the official Docker image, the default is `/home/paseo/.paseo`; its host path depends on the volume mount, and container stdout is available through Docker. Desktop app logs describe the Desktop process; daemon logs describe the selected daemon. Read the narrowest useful slice and redact credentials, pairing offers, tokens, passwords, and user code before sharing logs. If diagnosing the bundled daemon on a computer with Paseo Desktop installed, but `paseo` is not on `PATH`, the bundled CLI is at: - macOS: `/Applications/Paseo.app/Contents/Resources/bin/paseo` - Linux: `/resources/bin/paseo` - Windows: `C:\Program Files\Paseo\resources\bin\paseo.cmd` Offer to fix the PATH or symlink; do not change shell configuration silently. ## Escalate with evidence If the current docs and diagnostics do not resolve the problem, collect the app and daemon versions, OS, install method, connection method, exact error, minimal reproduction, and a small redacted log excerpt. - Bugs: [GitHub Issues](https://github.com/getpaseo/paseo/issues) - Questions and quick help: [Paseo Discord](https://discord.gg/jz8T2uahpH) - Product workflow discussions: [GitHub Discussions](https://github.com/getpaseo/paseo/discussions) or `#product` in Discord ## Dónde encaja - Categoría: [Herramientas para desarrolladores](https://skillsagentes.com/categorias/herramientas-desarrollo.md) — Skills que cambian cómo tu agente escribe, revisa y despliega código. - Creador: [getpaseo](https://skillsagentes.com/creators/getpaseo.md) — 8 skills en el directorio - [Todas las skills](https://skillsagentes.com/skills.md) - [Ranking de instalaciones](https://skillsagentes.com/ranking.md) ## Otras skills del mismo repositorio - [Paseo](https://skillsagentes.com/skills/getpaseo/paseo/paseo.md): Referencia de Paseo para gestionar proyectos, workspaces, scripts de workspace, agentes, schedules y heartbeats. Paseo es un daemon remoto que administra agentes de código y terminales, controlable por MCP o por CLI. - [Paseo Plugin](https://skillsagentes.com/skills/getpaseo/paseo/paseo-plugin.md): Construye y gestiona plugins locales de confianza para Paseo: crear, editar, instalar, recargar, activar, desactivar, quitar o depurar un plugin, añadir superficies nativas o de barra lateral, o añadir RPC y attachments del composer. - [Paseo Handoff](https://skillsagentes.com/skills/getpaseo/paseo/paseo-handoff.md): Transfiere la tarea actual a otro agente con todo el contexto: decisiones, intentos fallidos y restricciones en un briefing autocontenido. Se activa con "handoff", "hand off" o "hand this to". - [Release Beta](https://skillsagentes.com/skills/getpaseo/paseo/release-beta.md): Corta una release beta de Paseo. Se activa con "release beta", "cut a beta", "ship a beta", "beta release" o "/release-beta", y sigue el Beta flow y su checklist en `docs/release.md`. - [Paseo Committee](https://skillsagentes.com/skills/getpaseo/paseo/paseo-committee.md): Forma un comité de dos agentes de alto razonamiento que dan un paso atrás, hacen análisis de causa raíz y producen un plan. Úsala cuando estés atascado, en bucle, con visión de túnel o ante un problema de planificación difícil. --- Skills Agentes · [Índice de páginas en markdown](https://skillsagentes.com/sitemap.md) · [Inicio](https://skillsagentes.com/index.md)