--- title: "Report a problem" description: "Create a useful Fabricator bug report with diagnostics, logs, version details, and privacy checks." url: https://spatney.github.io/rayfin-fabricator/docs/troubleshooting/report-a-problem markdown_url: https://spatney.github.io/rayfin-fabricator/docs/troubleshooting/report-a-problem.md app_version: "1.20.1" section: troubleshooting product: Fabricator last_updated: 2026-10-06T23:07:33-07:00 source: troubleshooting/report-a-problem.mdx --- # Report a problem > Create a useful Fabricator bug report with diagnostics, logs, version details, and privacy checks. Use this page when the troubleshooting fix did not work or Fabricator shows an error that is not covered. ## Ask Help before reporting In the status bar, select **Help** and describe the problem. Help reads the same activity history that goes into a diagnostics export and often explains the cause directly. If it turns out to be a fault in Fabricator, Help writes the bug report for you from what it found, so you don't have to reconstruct it. See [Ask Help](https://spatney.github.io/rayfin-fabricator/docs/troubleshooting/help). ## Let Help report it The fastest report starts in Fabricator, and Help writes most of it for you. 1. In the status bar, select **Help**. 2. Describe the problem, or say "report this for me". 3. Help reads your activity history and shows **Bug report ready** with the problem written up. 4. Select **Review it first** to read it, then **Report this on GitHub**. 5. The issue opens prefilled, with app, Tauri, WebView2, Copilot CLI, and user-agent versions added. 6. Drag the diagnostics file from the opened logs folder onto the GitHub issue before submitting. Nothing is submitted until you select the submit button on GitHub yourself. If you aren't signed in to GitHub Copilot, **Help** offers **Report an issue** instead, which opens the same prefilled issue with an empty description for you to fill in. The public issue tracker is [https://github.com/spatney/rayfin-fabricator/issues](https://github.com/spatney/rayfin-fabricator/issues). ## Export diagnostics from Settings Use settings when you want to export diagnostics without opening a GitHub issue. 1. Open **Settings**. 2. Go to **Diagnostics**. 3. Select **Export diagnostics** to create a bundle and open the logs folder. 4. Select **Open logs folder** if you need to browse existing logs. 5. Use **Full diagnostics** only when you need more detail for a bug. It is off by default. **Full diagnostics** also captures prompts, responses, and tool output for each chat turn. Leave it off unless you are comfortable sharing that extra content with the maintainer. ## What diagnostics include A diagnostics export is a Markdown file named like `fabricator-diagnostics-20261004-010507.md` in the logs folder. It contains: - Fabricator version. - Operating system and architecture. - Tauri version. - WebView2 version when available. - Copilot CLI version. - Recent activity as JSON lines. - Recent chat-turn diagnostics as JSON lines. - Recent crash or hang log entries. Recent activity covers both what worked and what didn't: setup finishing, signing in, installing a tool, creating or opening an app, starting a preview, deploying, and every message the app showed you. Each entry includes the time, whether it was a success or a failure, the part of the app it came from, and the message. Credentials and token-like values are masked before anything is written. By default, chat-turn diagnostics are lightweight metadata: timing, model or mode when present, attachment count, files modified count, tool names and success, deploy involvement, outcome, and errors. ## What diagnostics do not include Diagnostics are local files. Fabricator does not send them automatically. The export says "Attach this file to your bug report. It contains no credentials." Fabricator also redacts bearer tokens and JWT-looking strings from Fabric helper errors before they can cross into diagnostics. Still review the file before posting publicly. With **Full diagnostics** on, prompts, assistant responses, and tool output can include app details, file paths, data names, or text you typed. ## Where logs are stored Logs live in Fabricator's per-user data folder under `logs`. - Windows: `%APPDATA%\Rayfin Fabricator\logs` - macOS: `~/Library/Application Support/Rayfin Fabricator/logs` Use **Settings → Diagnostics → Open logs folder** instead of browsing manually when possible. See [Files and folders](https://spatney.github.io/rayfin-fabricator/docs/reference/files) for the rest of Fabricator's stored data. ## What to include in a report A useful report includes: 1. The exact quoted message from Fabricator, chat, the preview, or the deploy log. 2. Numbered steps from a fresh launch to the problem. 3. Whether the issue happens after **Restart**, **Re-check**, **Refresh Fabric authentication**, or **Redeploy**. 4. The Fabricator version from the status bar. 5. The diagnostics bundle. 6. Screenshots or screen recordings with names, emails, tenant names, workspace names, URLs, and app data hidden. 7. Whether you are on Windows 10/11 or macOS Apple Silicon. ## Report security issues privately Do not open a public GitHub issue for a security vulnerability or sensitive credential exposure. Use the repository security policy instead: [SECURITY.md](https://github.com/spatney/rayfin-fabricator/blob/master/SECURITY.md).