Windows PowerShell flickering workaround: try Windows Terminal

[kunpeng-ai-lab]

I tested DeepSeek TUI on Windows and ran into a small terminal rendering issue that may help other Windows users.

Symptom

The installation completed successfully, and authentication was not the problem. However, when I launched deepseek inside the traditional PowerShell console, the TUI kept flickering and was hard to use.

What worked

Launching the same command inside Windows Terminal fixed the issue for me.

My workaround was:

1. Open Windows Terminal.
2. Start a PowerShell tab inside Windows Terminal.
3. Run:

deepseek --model auto

After that, the TUI rendered normally.

Why I am posting this

At first this looked like an install or API-key problem, but it was actually related to the terminal host. For Windows users, it may be worth documenting Windows Terminal as the recommended terminal before they reinstall the package or rotate credentials.

This may also apply to other older console hosts that do not handle TUI rendering cleanly.

Thanks for the project. The terminal-agent workflow is promising, especially with file operations, shell execution, Git context, MCP, LSP diagnostics, session resume, and workspace snapshots in one interface.

[richardchen874-sys]

Thanks for documenting this. This is useful for Windows users because it looks like a terminal host / TUI rendering issue rather than an install or API-key problem.

For DeepSeek TUI workflows, the terminal environment still matters a lot. If the UI flickers or fails to render properly, users may think the model/API is broken even when the request is actually working.

It may be worth adding a short Windows note recommending Windows Terminal over the legacy PowerShell console host, especially for longer DeepSeek sessions where streaming output, refresh behavior, and terminal stability affect the whole experience.

This could save users from reinstalling the package or changing API credentials when the real issue is only the terminal environment.