hotdata-dev · zfarrell · Sep 6, 2026 · Sep 5, 2026 · Sep 5, 2026 · Sep 5, 2026
@@ -129,9 +129,20 @@ Bring your own model with `hotdata search embeddings add`.
 - `hotdata databases context push|show DATAMODEL` stores your data model as
   shared, server-side Markdown so humans and agents query with the same map.
 
+## Getting help
+
+File a support ticket without leaving the terminal:
+
+```sh
+hotdata support report -m "Queries against work_abc have been timing out for an hour" --subject "Queries timing out"
+hotdata support report --logs ./stderr.txt --context env=staging
+```
+
+Omit `-m` in an interactive terminal to compose the report in `$EDITOR` instead. Replies go to the email on your HotData account.
+
 ## Commands
 
-The full command surface. The top level has eight groups — `auth`, `workspaces`, `databases`, `query`, `jobs`, `ingest`, `search`, and `manage`. Run `hotdata <command> --help` for full flags on any command.
+The full command surface. The top level has nine groups — `auth`, `workspaces`, `databases`, `query`, `jobs`, `ingest`, `search`, `manage`, and `support`. Run `hotdata <command> --help` for full flags on any command.
 
 | Command | What it does |
 | :-- | :-- |
@@ -203,6 +214,7 @@ The full command surface. The top level has eight groups — `auth`, `workspaces
 | `manage skills install` | Install/update the agent skill into agent directories |
 | `manage skills status` | Show the agent skill's installation status |
 | `manage skills list` | List installed skills (alias for `status`) |
+| `support report` | File a support ticket with the HotData team |
 
 ## Configuration
 

@@ -73,7 +73,7 @@ Catalog, skill decision tree, epic flows (onboard, chain, retrieval), and instan
 
 ## Available Commands
 
-Top-level subcommands (each detailed below): **`auth`**, **`query`**, **`workspaces`**, **`databases`**, **`jobs`**, **`ingest`**, **`search`**, **`manage`**. Instant databases nest `databases tables`, `databases queries`, `databases results`, and `databases context`; `ingest` nests `ingest sources`, runs, and logs; `manage` nests `usage`, `completions`, `upgrade`, and `skills`. Search (bm25/vector), indexes, and embedding providers are documented in **`hotdata-search`**; query history, results, Chain, and OLAP patterns in **`hotdata-analytics`**.
+Top-level subcommands (each detailed below): **`auth`**, **`query`**, **`workspaces`**, **`databases`**, **`jobs`**, **`ingest`**, **`search`**, **`manage`**, **`support`**. Instant databases nest `databases tables`, `databases queries`, `databases results`, and `databases context`; `ingest` nests `ingest sources`, runs, and logs; `manage` nests `usage`, `completions`, `upgrade`, and `skills`; `support` nests `report`. Search (bm25/vector), indexes, and embedding providers are documented in **`hotdata-search`**; query history, results, Chain, and OLAP patterns in **`hotdata-analytics`**.
 
 Global CLI options: **`--api-key`**, **`-v` / `--version`**, **`-h` / `--help`**, **`--no-input`** (disable interactive prompts; commands that require input will error instead — useful in CI or non-TTY environments). Hidden developer flag: **`--debug`** (verbose HTTP logs).
 
@@ -424,6 +424,14 @@ hotdata auth logout           # Remove saved auth for the default profile
 
 `login` and `register` (both GitHub and `--email`) are **browser-based** PKCE flows: the CLI opens a browser and waits on a local callback to complete sign-in/sign-up — account details (email/password) are entered in the browser, not via CLI flags. They require a browser and an interactive terminal, so they do **not** work under `--no-input` or in headless/CI. For automation, authenticate once interactively, then use the saved session or `HOTDATA_API_KEY`.
 
+### Report a problem (`support report`)
+
+```
+hotdata support report -m "<body>" --subject "<subject>" [--kind bug|question|billing|feature|account|other] [--severity urgent|high|medium|low] [-w <workspace_id> | --no-workspace] [--logs <path>|-] [--context KEY=VALUE ...] [-o table|json|yaml]
+```
+
+Files a support ticket via the API — no browser needed. `-m`/`--subject` are required together for non-interactive use (agents: always pass both); omit both in an interactive terminal to compose in `$EDITOR` instead. Attaches the active workspace by default (`--no-workspace` to omit, `-w` for a specific one); `--logs` reads a file or `-` for stdin (cap 256 KiB); `--context key=value` adds extra diagnostic pairs (repeatable, max 20). Prints the ticket's `public_id` on success — replies go to the email on the HotData account, not to the CLI.
+
 ## Workflows
 
 End-to-end recipes — onboard a workspace, run a query, build an instant database (parquet), chain/materialize, add retrieval indexes — live in [references/WORKFLOWS.md](references/WORKFLOWS.md). The command sections above are the per-command reference; the workflows stitch them into sequences.
@@ -5,6 +5,7 @@ use crate::commands::jobs::JobsCommands;
 use crate::commands::query::QueryCommands;
 use crate::commands::search::SearchCommands;
 use crate::commands::skill::SkillCommands;
+use crate::commands::support::SupportCommands;
 use crate::commands::workspace::WorkspaceCommands;
 use clap::Subcommand;
 
@@ -143,6 +144,12 @@ pub enum Commands {
         #[command(subcommand)]
         command: ManageCommands,
     },
+
+    /// Get help — file a support ticket with the HotData team
+    Support {
+        #[command(subcommand)]
+        command: SupportCommands,
+    },
 }
 
 /// Subcommands for `hotdata manage` — account and CLI utilities.

@@ -3,3 +3,4 @@ pub mod ingest;
 pub mod jwt;
 pub mod raw_http;
 pub mod sdk;
+pub mod support;
@@ -404,7 +404,7 @@ pub fn none_if_404<T>(r: Result<T, ApiError>) -> Result<Option<T>, ApiError> {
 /// url through verbatim would produce `/v1/v1/...` on every call. Strip one
 /// trailing `/v1` (and any trailing slash) so both paths resolve to a single
 /// `/v1`.
-fn sdk_base_path(api_url: &str) -> String {
+pub(crate) fn sdk_base_path(api_url: &str) -> String {
     let trimmed = api_url.trim_end_matches('/');
     trimmed.strip_suffix("/v1").unwrap_or(trimmed).to_string()
 }