jb/paseo
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Help agents diagnose Paseo provider problems (#3243)

Browse Source 
* feat(skills): add Paseo help and provider diagnostics

Give support agents a topology-aware troubleshooting entry point backed by the deployed documentation index, and expose the daemon provider diagnostic through the CLI so agents can inspect the affected host directly. Agent-launching skills now use configured profiles instead of the removed orchestration preferences.

* test(cli): keep provider diagnostics on real boundaries

Remove the internal client mock and preserve its normalization and host-targeting assertions through the existing isolated-daemon coverage.
This commit is contained in:
Mohamed Boudra
2026-08-12 00:57:33 +02:00
committed by GitHub
parent 5f5c585e68
commit d012b6f071
10 changed files with 239 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files
public-docs/cli.md
+12
View File
@@ -23,6 +23,18 @@ paseo logs <id> # View agent timeline
paseo stop <id> # Stop an agent
```
## Provider diagnostics
Ask the daemon to inspect the provider environment it actually uses:
```bash
paseo provider diagnostic claude
paseo provider diagnostic codex --json
paseo provider diagnostic opencode --host devbox:6767
```
The diagnostic includes the configured command, daemon `PATH` and shell, matching binaries, resolved path, version, model count, and provider status. Use `--host` for a remote daemon. This is the same diagnostic shown under **Settings → your host → Providers → provider → Diagnostic**.
## Running agents
Use `paseo run` to start a new agent with a task:
public-docs/troubleshooting.md
+9
View File
@@ -24,6 +24,15 @@ Open **Settings → your host → Providers**, tap the provider, then tap **Diag
- **Daemon PATH** — the `PATH` Paseo is searching. Compare it to `echo $PATH` in a fresh terminal.
- **Version** — whether the binary actually runs.
From a terminal or agent, request the same diagnostic from the affected daemon:
```bash
paseo provider diagnostic <provider>
paseo provider diagnostic <provider> --host <host:port> --json
```
Use `--host` when the affected daemon is not the CLI's default local daemon.
`not found` together with a **Daemon PATH** that's missing your binary's directory is the common case: that directory is on your terminal's `PATH` but not on Paseo's.
### Fix it