Description
VS Code crashes or unexpectedly exits while the YOLO Agent is autonomously executing test scripts in the background using DeepSeek v4-pro and v4-flash models.
Steps to reproduce
- Open a project in VS Code and launch the DeepSeek-TUI in the integrated terminal.
- Configure the tool to use
deepseek-v4-pro or deepseek-v4-flash.
- Switch to YOLO Agent mode.
- Assign a task that requires the agent to run local test scripts (e.g., "Fix the failing tests and run them until they pass").
- Let the agent run autonomously in the background without active monitoring.
Expected behavior
The YOLO Agent should complete the test execution and code modifications without affecting the stability of the host editor (VS Code).
Actual behavior
After a period of background execution, the VS Code process either completely disappears (crashed) or becomes entirely unresponsive, requiring a force kill. This seems to occur regardless of whether v4-pro or v4-flash is used.
Impact
This happens frequently during automated workflows. It is a major blocker because it interrupts the research/development cycle and causes the loss of the current session's terminal state.
Environment
- OS: Windows 11 (WSL2)
- DeepSeek CLI version: v0.8.28
- Install method: npm
- Model/provider: deepseek-v4-pro / deepseek-v4-flash
- Terminal app: VS Code terminal
- Shell: bash
Logs, screenshots, or recordings
Because this crash occurs during background execution, I have not been able to capture the exact error log at the moment of failure.
Note to other users: If you are experiencing similar crashes while using v4 models, please supplement this issue with your logs (from VS Code's "Developer Tools" console) or mention if you noticed a sudden spike in CPU/RAM usage before the exit.
Description
VS Code crashes or unexpectedly exits while the YOLO Agent is autonomously executing test scripts in the background using DeepSeek v4-pro and v4-flash models.
Steps to reproduce
deepseek-v4-proordeepseek-v4-flash.Expected behavior
The YOLO Agent should complete the test execution and code modifications without affecting the stability of the host editor (VS Code).
Actual behavior
After a period of background execution, the VS Code process either completely disappears (crashed) or becomes entirely unresponsive, requiring a force kill. This seems to occur regardless of whether v4-pro or v4-flash is used.
Impact
This happens frequently during automated workflows. It is a major blocker because it interrupts the research/development cycle and causes the loss of the current session's terminal state.
Environment
Logs, screenshots, or recordings
Because this crash occurs during background execution, I have not been able to capture the exact error log at the moment of failure.
Note to other users: If you are experiencing similar crashes while using v4 models, please supplement this issue with your logs (from VS Code's "Developer Tools" console) or mention if you noticed a sudden spike in CPU/RAM usage before the exit.