Answer: Starting in VS Code Extension 1.10.0, you can download the Extension Diagnostics via the Settings page, which collects relevant logs and parameters into a text file. For full output logs, open the Command Palette, type "Show logs" and select `Developer: Show Logs`, then change the dropdown to "Windsurf" and export or copy the logs. Status: Confirmed Entry: tool/devin/troubleshooting/gather-vscode-extension-logs Revision: 2 Digest: sha256:98421548f666d34e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:14:25Z Last changed: 2026-11-17T12:57:18Z (Final step: — → Export or copy the logs) Last verified: 2026-11-20T12:45:10Z Next check: 2026-11-21T12:45:10Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Minimum version for Settings download | 1.10.0 | [1] | 2026-11-20 Command Palette shortcut | Ctrl/Cmd + Shift + P | [1] | 2026-11-20 Command to select | Developer: Show Logs | [1] | 2026-11-20 Dropdown option to select | Windsurf | [1] | 2026-11-20 Final step | Export or copy the logs | [1] | 2026-11-20 Sources: [1] Cognition. "Visual Studio Code (VSCode) Troubleshooting". https://docs.devin.ai/desktop/troubleshooting/plugins-enterprise/vscode.md Role: primary. Accessed: 2026-11-20T12:45:10Z Quote: "Starting in VS Code Extension 1.10.0, the Extension Diagnostics are accessible for download via the Settings page." (Supports: Minimum version for Settings download) Quote: "Go to the Command Palette (`Ctrl/Cmd + Shift + P` or go to View > Command Palette)" (Supports: Command Palette shortcut) Quote: "Type in "Show logs" and select the option that reads `Developer: Show Logs`" (Supports: Command to select) Quote: "Change the dropdown in the top right that reads "Extension Host" and select "Windsurf"" (Supports: Dropdown option to select) Quote: "Export or copy the logs" (Supports: Final step) Published: 2026-11-20T12:45:16Z Snapshot SHA-256: 2421133b279e2eac561c4b83c2cb034ea90cdf453ca21856165f1c059324d9af (captured 2026-11-16T12:29:57Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-16T12:29:56Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:45:10Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:45:10Z Last attempt: 2026-11-20T12:45:10Z Notes and limitations: Extracted automatically from a single official source (section "Gathering extension logs"). Related: https://latestn.com/tool/devin/troubleshooting/incompatible-extensions Which extensions are incompatible with Devin Desktop? https://latestn.com/tool/devin/troubleshooting/inotify-limit-values What inotify limit values should I set for Devin Desktop on Linux? https://latestn.com/tool/devin/troubleshooting/insights-troubleshooting How do I troubleshoot when no insights are available or analysis takes too long in Devin Session Insights? https://latestn.com/tool/devin/troubleshooting/gather-plugin-logs-jetbrains How do I gather Windsurf plugin logs in JetBrains IDEs? https://latestn.com/tool/devin/troubleshooting/gather-plugin-logs-visual-studio-neovim How do I retrieve Windsurf plugin logs in Visual Studio or NeoVim? https://latestn.com/tool/devin/troubleshooting/gather-plugin-logs-vscode How do I collect Windsurf plugin logs in VS Code? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T12:57:18Z | changed | Final step: — → Export or copy the logs | [1] 2026-11-17T12:57:18Z | changed | Minimum version for Settings download: — → 1.10.0 | [1] 2026-11-17T12:57:18Z | changed | Diagnostics download location: Settings page → — | [1] 2026-11-17T12:57:18Z | changed | Minimum extension version: 1.10.0 → — | [1] 2026-11-13T03:14:25Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/devin/troubleshooting/gather-vscode-extension-logs/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/devin/troubleshooting/gather-vscode-extension-logs POST: https://latestn.com/dispute/tool/devin/troubleshooting/gather-vscode-extension-logs with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/devin/troubleshooting/gather-vscode-extension-logs?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I gather extension logs for the Devin VS Code extension? Revision 2, last verified 2026-11-20T12:45:10Z. https://latestn.com/tool/devin/troubleshooting/gather-vscode-extension-logs (accessed 2026-11-21T10:03:42Z). @misc{LatestN_tool_devin_troubleshooting_gather_vscode_extension_logs_r2, title = {How do I gather extension logs for the Devin VS Code extension?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/devin/troubleshooting/gather-vscode-extension-logs}}, note = {Revision 2; digest sha256:98421548f666d34e; last verified 2026-11-20T12:45:10Z; accessed 2026-11-21T10:03:42Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/devin/troubleshooting/gather-vscode-extension-logs