Diagnose Superset connection, host, terminal, authentication, and update problems using status checks and logs. Get a matching fix, approve changes before they run, and verify whether the original problem is resolved.
Diagnose and fix Superset problems such as connection failures, offline hosts, terminals not attaching, auth or update issues. Use when the user reports something broken or misbehaving in Superset itself ("Superset won't connect", "my host shows offline", "terminal won't attach", "the app is stuck"), before filing feedback.
Review the instructions the agent will receive before you install.
Diagnose first, change one thing at a time, verify after each change.
superset status for host service healthsuperset auth whoami for auth and the active orgsuperset hosts list for host reachabilitysuperset --version| Signature | Fix |
|---|---|
whoami fails / session expired | superset auth login |
| Host shows offline | superset hosts wake <id>; confirm the machine is awake and online |
| Host service not running | superset start |
A host set up with superset hosts add is offline or broken | re-run superset hosts add <ssh-target>; it checks each step and fixes only what is wrong. On Linux its log is ssh <ssh-target> journalctl --user -u superset-host -n 50 |
hosts add cannot reach or set up the machine | confirm ssh <ssh-target> works from here, the remote is macOS or glibc Linux (x64 or arm64; Alpine and Windows are not supported), and it has curl |
Private repos will not clone on a host added with hosts add | sign in GitHub there: ssh -t <ssh-target> gh auth login (install gh first if missing) |
| Linux host stops when the user logs out of it | enable lingering on that machine: loginctl enable-linger |
hosts add stops on an empty or invalid /etc/machine-id (cloned VM or container image) | on that machine, sudo rm -f /etc/machine-id && sudo systemd-machine-id-setup, then re-run hosts add. The user runs this, since it needs sudo on their box |
superset pages publish in a Superset terminal fails with "Not a member of organization" | superset update; newer CLIs use the desktop app's account inside its terminals |
| CLI and desktop app version mismatch, or stale CLI | superset update |
| App-side misbehavior (macOS) | read the newest entries in ~/Library/Logs/Superset/main.log for errors |
Propose the matching fix and get the user's go-ahead before running anything that changes state. Never delete data as a "fix".
Re-run the originally failing action. If it works, say exactly what was wrong and what fixed it.
If unresolved, offer to file it with the feedback skill and carry over the collected diagnostics (versions, status output, the relevant log excerpt) so the report arrives pre-triaged. Ask before including any log content; logs can contain paths and project names.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.
Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.
Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.
Build Stripe payments, subscriptions, and invoicing using verified documentation and API parameter definitions. The skill guides product selection, sandbox testing, and webhook handling, where server notifications determine payment and subscription state.
Verify desktop UI changes through the Chrome DevTools Protocol, a connection for controlling the running app. Reproduce the user’s actual steps and compare screenshots, measured state, and console errors to establish evidence before and after a fix.
Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.