DeepSeek TUI Updates Upgrade, Docker and Safety Guidance

What changed upstream

• Upgrade commands are now spelled out by install path: the current README tells users to update with deepseek update for release-binary installs, npm install -g deepseek-tui@latest for the npm wrapper, brew update && brew upgrade deepseek-tui for Homebrew, and forced Cargo reinstalls for Rust users.
• Docker persistence is documented as a real setup step: the README now creates a named deepseek-tui-home volume and mounts it to /home/deepseek/.deepseek, which makes auth, config, and session data survive container restarts instead of behaving like a throwaway demo.
• Download-safety guidance is explicit: the same install section warns users to fetch manual binaries only from the official GitHub Releases page, verify the published SHA-256 manifest, and avoid look-alike repositories or search-result mirrors.
• The default DeepSeek Platform route is more clearly documented: the current README says the default provider base URL is https://api.deepseek.com/beta so beta-gated API features work without extra setup, while users can set base_url = "https://api.deepseek.com" to opt out.

Practical setup guidance

This is more than a minor README refresh. It changes what a technically trustworthy DeepSeek TUI install page should teach:

1. Upgrade advice should match the install method instead of telling every user to reinstall from scratch.
2. Docker examples should preserve the user's DeepSeek TUI state, not silently discard credentials and sessions.
3. Manual-download instructions should include the official artifact location and checksum verification, not just a naked binary link.
4. Teams debugging provider behavior should know when the TUI is intentionally targeting the beta DeepSeek base URL by default.

Sources

• DeepSeek TUI GitHub repository README
• DeepSeek TUI releases
• DeepSeek TUI install docs
• DeepSeek official Claude Code integration guide
• DeepSeek Anthropic API compatibility docs
• DeepSeek V4 Flash Hugging Face page