Add "Open Application Logs" to Help menu

[ivan-ottinger]

Related issues

• N/A (no existing Linear issue)

Proposed Changes

I think it could be useful to make it easy for our users to access app logs in case they need to troubleshoot something - or if we need to ask them for the logs.

At the moment, it is possible to easily get to logs from error modals only (after some error is triggered already). What we could to is to add a menu item as follows. What do you think?

• Add an "Open Application Logs" menu item to the Help menu, placed before "Report an Issue"
• Clicking it opens the Studio log file (current.log) in the user's default text editor via shell.openPath()
• Uses the existing getLogsFilePath() utility from src/logging, following the same pattern as the error dialog's "Open Studio Logs" button

Testing Instructions

1. Run npm start
2. Open the Help menu
3. Verify "Open Application Logs" appears between the Windows speed-up item (or the separator on macOS) and "Report an Issue"
4. Click "Open Application Logs"
5. Verify the Studio log file opens in your default text editor

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[sejas]

It works as expected. I tested it on a Mac, and it opens the log file in the Console app. Another alternative could be opening Finder with showItemInFolder, but I think the current behavior of opening the log is more consistent with the current dialogs.

logs.mp4

[wpmobilebot]

📊 Performance Test Results

Comparing 3c92dd1 vs trunk

site-editor

Metric	trunk	3c92dd1	Diff	Change
load	1485.00 ms	1496.00 ms	+11.00 ms	⚪ 0.0%

site-startup

Metric	trunk	3c92dd1	Diff	Change
siteCreation	7148.00 ms	7134.00 ms	-14.00 ms	⚪ 0.0%
siteStartup	4938.00 ms	4923.00 ms	-15.00 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

[katinthehatsite]

I think this looks good, and also works as expected 👍