Current Status
There is no Support CLI command group.
Support is currently an in-app and help-center workflow, not a terminal interface. The macOS app embeds the configured Chatwoot support surface and the public help center carries module articles for users who need setup or workflow guidance. CLI users should open those resources rather than expecting commands to create tickets or chat sessions.
GUI-Only Coverage Today
Use the macOS Support module for Chatwoot support access.
When reporting an issue, include the Firestruct version, macOS version, target Firebase project type, emulator or production environment, module name, command or UI action, relevant logs, and whether the project is read-only. For data operations, avoid sending secrets, service-account JSON, private Firebase data, or access tokens unless a secure support channel explicitly requests them.
The absence of a Support CLI command keeps diagnostics gathering manual for now. That is deliberate while the product is early: users can review the contents of any logs or screenshots before sharing them with support.
Future CLI Shape
Support CLI coverage is optional. If added, it should focus on diagnostics bundles rather than interactive chat:
support diagnostics --output firestruct-diagnostics.zip
support open-ticket --subject "Issue summary"
If diagnostics support is added later, it should generate a local archive first and ask the user to review it before upload. Interactive chat and account identity should remain tied to the configured support provider.
Source Anchors
Sources/FirestructApp/Features/Support/