/feedback

name: feedback
description: Collect and submit feedback about Paradev (formerly Superset) (bug reports, feature requests, or general feedback) privately to the Paradev team or as a public GitHub issue. Use when the user wants to report a Paradev bug, request a feature, or send feedback about Paradev.
argument-hint: describe the bug, request, or feedback
allowed-tools: Bash(superset:*) Bash(paradev:*) Bash(gh:*) Bash(uname:*) WebFetch WebSearch

Paradev Feedback

`paradev` is an alias for the `superset` CLI: every `superset` command here also runs as `paradev`.

Check Paradev's documentation for an existing answer first. When feedback still needs reporting, turn it into a short, scannable report and submit it where the user chooses. Treat whatever they wrote after the command as the seed.

The reader is a Paradev engineer triaging dozens of reports. They should get the point from the title, the full picture from the summary bullets, and only read further when they need detail. Cut everything that doesn't help them reproduce or decide.

0. Is this a follow-up?

Every private submission CCs the reporter, so they already have a copy in their inbox with a subject starting `[Feedback: ...]`. A reply to that email lands on the same thread; a new submission opens a new one and the team has to reconcile them by hand.

If the seed reads like a continuation ("follow-up", "again", "still happening", "update on", "retraction", "root cause", "I already sent", "third time"), or the user filed something on this topic earlier in the session, ask whether they already sent a report about it. If they did, tell them to reply to that email with the new information and stop here. Only file fresh when they confirm it's a different issue.

Never title a report "Follow-up:", "ROOT CAUSE:", or "RETRACTION"; those belong in a reply.

Check the knowledge base before gathering report details

Search the Paradev documentation for the user's question, symptom, or requested capability. Use `docs_search` with relevant keywords, then `docs_read` on promising results when the Paradev docs MCP tools are available. Otherwise fetch `https://docs.paradev.com/llms.txt` and read the relevant linked pages, or use web search restricted to `docs.paradev.com`. Use generic product terms and error messages; keep private paths, account details, and logs out of search queries.

Read the actual page before treating a result as an answer. Check that it applies to the user's platform, version, and circumstances. If it does, answer directly with the relevant steps and a link to the source. For a requested feature that already exists, explain how to use it. For a bug, offer the documented fix and verify the outcome before treating it as resolved. A related article or workaround alone does not mean the issue is resolved.

If the answer resolves the request and the user has not asked to file anyway, stop without drafting a report. If it does not help, or the user still wants to send feedback, continue below and include the relevant article and what was tried in the draft. Do not make them repeat troubleshooting already covered in the conversation. If the docs are unavailable or no answer matches, continue with the report; do not block submission or claim no answer exists when the lookup failed.

1. Gather context (best effort, never block)

Run in parallel; skip anything that fails:

• `superset --version` and `uname -sm` for the environment line
• `superset auth whoami` for the signed-in user/org (private submissions only)
• `superset status --json` for the host service; its `hostServiceVersion` is the desktop app's version when the app spawned the service

Don't include repository contents, terminal output, or logs unless the user explicitly agrees when asked; they can contain private paths and code.

Version check

Many reports describe bugs already fixed in a newer release. Desktop, CLI, and host service share one version number, so compare what's running against the latest release:

• Latest: `superset update --check --json` (standalone CLI). If it says the CLI is bundled with the desktop app, the CLI version is the app version; get the latest from `gh release download cli-latest -R paradevai/paradev -p version.txt -O -` instead.
• Running: the CLI version, and `hostServiceVersion` from `superset status --json` if it differs.

If anything is behind, say so before drafting and ask whether they want to update first (the desktop app updates itself from its menu; a standalone CLI with `superset update`). If they'd rather file now, note the versions in the report.

Bugs about hosts, automations, terminals, or remote workspaces

Symptoms like "host not registered", "hosts list is empty", "automations create fails", "host shows offline", "terminal won't attach", or "workspace missing from the sidebar" are the most common reports and usually have a known cause. Before drafting, run the doctor skill's snapshot (`superset status`, `superset auth whoami`, `superset hosts list`) and apply its signature table. If that fixes it, there's nothing to report. If it doesn't, keep the `superset status --json` output for the report; it's what the team asks for first.

Evidence (bugs only, offer, never assume)

• **Screenshot**: if the bug is visual and you can capture one, offer to attach it. Evidence beats prose.
• **Diagnostics**: offer the `--diagnostics` bundle: versions, OS, and the last 200 lines of the app log and the host-service log. Tell the user logs can contain file paths and project names before they agree. Prefer the bundle over attaching raw log files; attach a file only when the tail isn't enough. Attachments must total under about 3 MB; a single larger log is cut to its tail automatically.

2. Classify and draft

Classify as **bug**, **feature request**, or **general feedback** from their words; ask only if genuinely ambiguous.

**One report per root issue, one request per ask.** Two symptoms of the same fai