peach support
Ask a question the docs do not answer and get an answer back in the terminal, report a problem, and check the status of both. Every ask and report belongs to the account your peach login names, so peach support status lists them with our replies, the commit that fixed each report, and the runtime release that shipped it. An ask sends the question, CLI and runtime versions, and the dependency compatibility scan. A report also attaches the project report printed by peach project-report, and requires confirmation before sending. Neither attaches source, environment variables, terminal output, logs, screenshots, or app data. The first 5 asks of an account are answered right away and later ones once we approve the account; peach support fund adds funds for onboarding support.
Options
| flag | description |
|---|---|
--wait <minutes> | how long ask waits for the answer (default 15) |
--no-wait | return the ask id at once; the answer shows in status |
--app <dir> | scan only this app directory instead of the detected workspace |
--dry-run | preview a report without sending it |
-y, --yes | send a report after the user has explicitly approved the preview; required in non-interactive sessions |
--new | list only what changed since the last status |
--amount <usd> | how much fund adds to the prepaid balance (default $10) |
--json | print machine-readable output |
Examples
Ask, Try, Report, Check
Ask when the docs do not cover something: peach support ask "<question>" waits up to 15 minutes and prints the answer, which comes from an assistant that reads the simulator’s docs and code with the earlier asks and reports of your account. --no-wait returns the id at once.
An account’s first 5 asks are answered right away. Later asks are kept and queued until we approve the account, then answered in order; peach support status shows them as waitlisted meanwhile. Reports and status are never held.
Want onboarding support? Add funds: peach support fund opens the payment page in your default browser, waits for the payment, and binds the funded account to this login.
Report when something is broken on our side: peach support report "<what happened, the exact steps, expected and actual>". The command shows the description and attachment summary before it sends anything. An interactive terminal asks for confirmation. A non-interactive agent must first show the finding to the user and ask whether to report it. Only after the user explicitly agrees may the agent rerun with --yes. A report attaches the local compatibility scan and the same report printed by peach project-report: discovered project paths, dependency versions, native build settings, and machine toolchain versions. Use --dry-run to inspect that attachment summary without sending.
Check with peach support status. It lists your account’s asks and reports, newest first, with our replies, the commit that fixed a report, and the runtime release that shipped it. --new lists only what changed since the last check, so an agent can run it every hour. Nothing needs an id kept by hand: the account your peach login names owns every item.