{"slug": "tracescope-0-3-6-usb-crash-capture-for-crashes-that-never-reach-the-apm", "title": "TraceScope 0.3.6: USB crash capture for crashes that never reach the APM", "summary": "A developer released TraceScope 0.3.6, an MIT-licensed plugin for DeepSeek Harness, adding Local crash capture that pulls crashes and ANRs directly from a USB-connected Android or iOS device instead of relying on APM services like Firebase Crashlytics. Captured crashes are stored locally in ~/.tracescope/crash-inbox/shared/ and fed through the same AI analysis, write-back and defect-filing flow, with Android capture using adb and iOS capture requiring macOS and libimobiledevice. The plugin is available via npm as @rebornace/dsh-tracescope and through an MCP server for clients such as Cursor and Claude Code.", "body_md": "TraceScope is an MIT-licensed plugin for DeepSeek Harness with three capabilities: functional impact analysis, design diff analysis, and crash analysis. Version 0.3.6 adds **Local crash capture**, a crash source that doesn't wait for crash reporting.\n\nGitHub: [https://github.com/rebornace/dsh-tracescope](https://github.com/rebornace/dsh-tracescope) | npm: `@rebornace/dsh-tracescope`\n\nCrash analysis already works against APM services such as Firebase Crashlytics: it lists issues, opens the details, parses the stack, and writes the AI conclusion back.\n\nEvery one of those services only knows about crashes that were reported and aggregated. A crash that never got that far simply isn't in the list.\n\n0.3.6 adds **Local crash capture**. Crashes and ANRs are pulled straight from a USB-connected device. Collection runs locally inside the plugin, with no APM dependency and no upload to an APM. Once a crash has been captured, it goes through the same analysis, write-back and defect-filing flow as the reported ones.\n\nThe sidebar's **Data source** section has a new **Local crash capture** entry. Choose Android or iOS, refresh the device, start recording. Crashes and ANRs raised during the recording are written locally and appear in the list; opening the source loads the history automatically, with the count shown next to the title.\n\nOpening an entry shows the parsed stack, plus possible matches for the files in that stack against the configured code directory. A miss is only a soft hint: the full stack still reaches the analysis.\n\nA few things worth knowing:\n\nCaptures go to `~/.tracescope/crash-inbox/shared/`. TraceScope doesn't upload them to Crashlytics or any other APM. Whether the app's own APM SDK reports anything is decided by the app's configuration and has nothing to do with this capture.\n\nAndroid capture goes through adb. If adb isn't installed, refreshing the device downloads platform-tools for you; no full SDK setup needed. USB debugging has to be on.\n\nCaptures stay on the machine that recorded them, and the list only shows entries in that machine's local directory. iOS capture needs macOS (libimobiledevice); Windows can't record iOS. Android capture works on Windows and macOS alike.\n\nCapture on its own only fetches the crash. With an entry open, analysis offers two options:\n\n| Entry | Output | Notes | \n|---|---|---|\n| **Write reproduce steps** (primary) | repro steps, environment info | symptom only, no root-cause guessing | \n| **Locate & fix** | root cause, blast radius, minimal fix | meant for changing code | \n\nBoth quietly tidy the stack and drop the prompt into the session; the conclusion shows up in the sidebar once the agent calls the write-back tool. From there it can be copied, exported as Markdown, or filed as a defect on GitHub Issues, GitLab Issues, or a generic webhook.\n\n**DeepSeek Harness desktop**: install `@rebornace/dsh-tracescope` from the plugin page, open the TraceScope sidebar, pick **Local crash capture**, connect a device and start recording.\n\n**MCP clients** (Cursor, Claude Code, Codex, or any MCP-capable agent): add this to the config:\n\n```\n{\n  \"mcpServers\": {\n    \"tracescope\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@rebornace/tracescope-mcp\"]\n    }\n  }\n}\n```\n\nRestart, then call `tracescope_open_panel` to get the same three-mode workbench the sidebar has. Local capture needs a connected device, so run it from the desktop sidebar or that workbench. Node.js 20 or newer.\n\nAll three backends sit behind extension points rather than being tied to one vendor:\n\n| Surface | Available now | Can extend to (examples) | \n|---|---|---|\n| Crash sources | Local crash capture (USB), Firebase Crashlytics | Sentry, other APM services | \n| Tracker / issue platforms | GitHub Issues, GitLab Issues, generic webhook | Jira, other issue trackers | \n| Design sources | Figma | Other design tools on request | \n\nNew crash sources will be added over time; trackers and design sources come in on request. Opening an issue with the platform name, its auth method, whether it has a public API, and the use case is the fastest way to get one prioritized. Roadmap details live in the repo docs.\n\nCrash collection now has two kinds of sources: online from APM services such as Firebase Crashlytics, and on-device over USB. Both feed the same parse / write-back / file-a-defect flow. What the plugin does hasn't changed: it automates the fetching, parsing and locating, and **lowers the barrier to applying AI analysis to app quality**.\n\nIssues and PRs are welcome.\n\n**Links**", "url": "https://wpnews.pro/news/tracescope-0-3-6-usb-crash-capture-for-crashes-that-never-reach-the-apm", "canonical_source": "https://dev.to/rebornace/tracescope-036-usb-crash-capture-for-crashes-that-never-reach-the-apm-3nb8", "published_at": "2026-11-12 02:09:25+00:00", "updated_at": "2026-11-12 02:22:10.597353+00:00", "lang": "en", "topics": ["ai-tools", "ai-agents", "developer-tools", "agent-protocols"], "entities": ["TraceScope", "DeepSeek Harness", "Firebase Crashlytics", "GitHub", "GitLab", "Figma", "Cursor", "Claude Code"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/tracescope-0-3-6-usb-crash-capture-for-crashes-that-never-reach-the-apm", "markdown": "https://wpnews.pro/news/tracescope-0-3-6-usb-crash-capture-for-crashes-that-never-reach-the-apm.md", "text": "https://wpnews.pro/news/tracescope-0-3-6-usb-crash-capture-for-crashes-that-never-reach-the-apm.txt", "jsonld": "https://wpnews.pro/news/tracescope-0-3-6-usb-crash-capture-for-crashes-that-never-reach-the-apm.jsonld"}}