Reference
trove report
Updated 1 Oct 2026
On this page
For agents
Load this page when: you need to report a bug or request a feature from the terminal
- Pass --title and one of --body, --body-file or --body - for stdin.
- Set --type to bug, feature, idea or other.
- Leave secrets and the user's private text out of the body.
trove report posts a ticket to your Trove support inbox. You can read it later in the web app under Support.
trove report
Posts a report.
Usage
bash
trove report --title TITLE [--body TEXT | --body-file PATH] [--type TYPE] [--json]Arguments and flags
| Flag | Value | Default | Meaning |
|---|---|---|---|
--title | text, up to 200 characters | required | Report title. |
--body | markdown, or - | none | Report body. - reads the body from stdin. |
--body-file | path | none | Read the body from a file. Use it for large diagnostic dumps. |
--type | bug, feature, idea or other | other | Report type. |
--body-file wins over --body. A body is required. It can hold up to 100000 characters.
Example
bash
trove report --title "toc fails on a large book" --type bug --body-file diag.mdOutput
✓ Report posted to support
View it at https://example.com/support/cmrep123json
{
"id": "cmrep123",
"url": "https://example.com/support/cmrep123"
}Errors
| Message | Fix |
|---|---|
Report body is empty. Provide --body "...", --body-file <path>, or pipe content with --body - | Pass a body. |
Body file not found: {path} | Check the path. |
Too many reports in a short window — wait a minute and retry. | Wait a minute. |
title exceeds 200 characters | Shorten the title. |
REST equivalent: Account API.