Report a problem with useful diagnostic details
Prepare a concise report that makes a Choro problem reproducible.
Last updated 16 September 2026
Prepare a concise report that makes a Choro problem reproducible.
Before you start
Keep the original error or failed conversation available. Use a small example that demonstrates the issue without including unrelated private work.
Help → Send feedback opens the requests portal. Include the trigger, expected and actual result, and a focused screenshot or error excerpt.
Step by step
Write a short title naming the failed action, such as “Preview stays blank after the server starts.”
Describe the steps from a known starting point. Include the relevant project scope, tool, provider, and whether Solo or Band was involved.
State the expected result and the actual result separately. Copy the exact error text and note when it occurred.
Attach a focused screenshot or relevant terminal excerpt when it clarifies the problem. Remove secrets, personal content, and unrelated information first.
Include the Choro build and macOS version when available, whether the issue repeats, and any recovery steps already tried.
For performance issues, use Settings → Process monitor and report the workload alongside the readings. For provider failures, name the provider and model rather than sharing credentials.
Use the support or feedback route available to you. Choro’s Help → Send feedback opens the requests portal; describe a reproducible problem clearly and follow any portal guidance about the appropriate category.
What to expect
The report contains enough evidence to investigate the behavior without requiring someone to guess the missing steps.
Troubleshooting and useful details
A screenshot of an error without its trigger is often insufficient. Do not publish a complete workspace archive, credential, or private conversation merely because it might contain useful evidence. Preserve the original work until the failure is understood.