[parthshahp]

What/Why?

After an unexpected error, the CLI asks whether to send an error report. Part of a stack that lets Storefront Hosting users send feedback from the CLI. Stacked on #3276.

✖ Failed to create deployment: Something went wrong on our end…
Correlation ID: 3f2c…
? Send an error report to BigCommerce? It includes the error, the CLI version, and the `catalyst debug` report (no secret values). (y/N)
✔ Error report sent. Thank you!

• index.ts calls offerCrashReport (lib/crash-report.ts) only for unexpected errors (the ones that show the Correlation ID). A UserActionableError (bad input, an expired token, a 4xx) does not ask. Ctrl+C at a prompt is not a crash.
• The default answer is No, because the report contains the error text and stack.
• The report contains the first line of the error as the title, the message, the command, the Correlation ID, the CLI version, the stack, and the catalyst debug report. The home directory shows as ~. Source is catalyst-cli-crash. It works when telemetry is off.
• In CI, without a TTY, or without credentials, the CLI shows "To report this error, run catalyst feedback." --no-hints and CATALYST_NO_HINTS turn off the question and the hint.
• A preAction hook (recordActiveCommand) records the running command, so the handler can find the credentials from flags, env, or project.json.
• offerCrashReport never throws, so the handler always exits with code 1.

The feedback endpoint does not accept CLI tokens yet. A backend change for this is in progress.

Testing

• pnpm lint, pnpm typecheck, and pnpm test pass (890 tests).
• Manual, in a pseudo-terminal with an unreachable --api-host: the question shows with (y/N), and n exits without sending. Without a TTY, the hint shows. With --no-hints, nothing shows.

Migration

None.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
catalyst	Ready	Preview	Oct 19, 2026 5:09pm UTC

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6ed2baf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 1 package

Name	Type
@bigcommerce/catalyst	Minor

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Unlighthouse Comparison

✅ Resolved: the latest run found no regressions.

Full Unlighthouse report →

[jorgemoya]

lgtm!