You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -264,6 +264,30 @@ When a launch configuration has a `preLaunchTask` that uses input variables (`${
264
264
265
265
This is because background tasks and task dependencies require VS Code's native task orchestration.
266
266
267
+
### Go Debug Output Capture
268
+
269
+
The Go debug adapter (Delve) writes test output directly to stdout/stderr rather than routing it through the Debug Adapter Protocol. When Ignition MCP overrides `console: "integratedTerminal"` to `"internalConsole"` for output capture, this output is lost because there's no terminal to receive it.
270
+
271
+
**Symptoms**: Debug session runs successfully but no output appears in the debug console or in `get_debug_output` results, even though running the same configuration manually shows output.
272
+
273
+
**Workaround**: Disable the console override for Go launch configurations:
274
+
275
+
```json
276
+
{
277
+
"name": "Run Tests",
278
+
"type": "go",
279
+
"request": "launch",
280
+
"mode": "test",
281
+
"program": "${workspaceFolder}/...",
282
+
"console": "integratedTerminal",
283
+
"mcp": {
284
+
"preserveConsole": true
285
+
}
286
+
}
287
+
```
288
+
289
+
With `preserveConsole: true`, the terminal is created and output is visible, but Ignition MCP cannot capture it programmatically.
0 commit comments