TraceScope 0.3.6: USB crash capture for crashes that never reach the APM

TraceScope is a free plugin for the DeepSeek Harness development platform. Version 0.3.6 introduces Local crash capture, a new feature that captures crashes and ANRs (application not responding) directly from a USB-connected device without needing to report the crash to an APM service.

The Local crash capture feature appears in the sidebar under the Data source section. To use it, choose Android or iOS, refresh the connected device, and start recording. Crashes and ANRs captured during the session are saved locally and displayed in the list. Opening a crash entry automatically loads the stack trace, which can be analyzed further.

Crash captures are stored in the ~/.tracescope/crash-inbox/shared/ directory on the machine where the recording was made. Android devices require USB debugging to be enabled, while iOS capture requires macOS with the libimobiledevice library installed. Windows users cannot currently record iOS devices.

Once a crash is captured, it undergoes the same analysis, write-back, and defect filing process as crashes reported to an APM service. The plugin automatically parses the stack trace, matches it against the configured code directory, and generates a write-back report. This report can be copied, exported as Markdown, or filed as a defect on various issue tracking platforms such as GitHub Issues, GitLab Issues, or a generic webhook.

DeepSeek Harness desktop users can install the TraceScope plugin from the plugin page and start using Local crash capture by connecting a device and initiating a recording. MCP clients, such as Cursor, Claude Code, Codex, or any other MCP-capable agent, can add the plugin to their configuration and then call tracescope_open_panel to access the Local crash capture functionality.