[PR #395] [CLOSED] fix(deepseek-tui): correct China endpoint hostname in BASE_URL guide #398

Closed
opened 2026-10-26 09:48:48 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/awesome-deepseek-agent/pull/395
Author: @kittimzhe
Created: 8/21/2026
Status: ❌ Closed

Base: main ← Head: fix/deepseek-tui-cn-endpoint


📝 Commits (1)

  • 0d09fd4 fix(deepseek-tui): correct China endpoint hostname in BASE_URL guide

📊 Changes

2 files changed (+2 additions, -2 deletions)

View changed files

📝 docs/deepseek-tui.md (+1 -1)
📝 docs/deepseek-tui.zh-CN.md (+1 -1)

📄 Description

What

The DeepSeek-TUI guide listed https://api.deepseeki.com as the China endpoint for DEEPSEEK_BASE_URL. That hostname does not exist — HTTPS connections fail (status 000), and it is not referenced anywhere in DeepSeek-TUI's own configuration.

Why

Following the guide as written would direct users to a non-existent domain for the China endpoint. CONTRIBUTING.md states that only configuration options verified to work should be documented.

The upstream config.example.toml documents deepseek-cn as a legacy alias whose official host is still https://api.deepseek.com — there is no separate deepseeki.com host.

Change

Update both the English (docs/deepseek-tui.md) and Chinese (docs/deepseek-tui.zh-CN.md) guides to state that the default host https://api.deepseek.com serves the China endpoint, and note deepseek-cn as a legacy alias for the same host. One PR, both languages — per the "one tool per PR, both languages in a single PR" rule.

How verified

  • curl https://api.deepseeki.com → HTTPS 000 (unreachable)
  • curl https://api.deepseek.com → 401 (reachable, auth-gated as expected)
  • DeepSeek-TUI/config.example.toml:27:
    # provider = "deepseek-cn" # legacy alias (official host is still https://api.deepseek.com)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/awesome-deepseek-agent/pull/395 **Author:** [@kittimzhe](https://github.com/kittimzhe) **Created:** 8/21/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/deepseek-tui-cn-endpoint` --- ### 📝 Commits (1) - [`0d09fd4`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/0d09fd4a0a1d43e49815c952a70a89827af47100) fix(deepseek-tui): correct China endpoint hostname in BASE_URL guide ### 📊 Changes **2 files changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/deepseek-tui.md` (+1 -1) 📝 `docs/deepseek-tui.zh-CN.md` (+1 -1) </details> ### 📄 Description ## What The DeepSeek-TUI guide listed `https://api.deepseeki.com` as the China endpoint for `DEEPSEEK_BASE_URL`. That hostname does not exist — HTTPS connections fail (status `000`), and it is not referenced anywhere in DeepSeek-TUI's own configuration. ## Why Following the guide as written would direct users to a non-existent domain for the China endpoint. `CONTRIBUTING.md` states that only configuration options verified to work should be documented. The upstream `config.example.toml` documents `deepseek-cn` as a legacy alias whose **official host is still `https://api.deepseek.com`** — there is no separate `deepseeki.com` host. ## Change Update both the English (`docs/deepseek-tui.md`) and Chinese (`docs/deepseek-tui.zh-CN.md`) guides to state that the default host `https://api.deepseek.com` serves the China endpoint, and note `deepseek-cn` as a legacy alias for the same host. One PR, both languages — per the "one tool per PR, both languages in a single PR" rule. ## How verified - `curl https://api.deepseeki.com` → HTTPS `000` (unreachable) - `curl https://api.deepseek.com` → `401` (reachable, auth-gated as expected) - `DeepSeek-TUI/config.example.toml:27`: `# provider = "deepseek-cn" # legacy alias (official host is still https://api.deepseek.com)` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-26 09:48:48 +00:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/awesome-deepseek-agent#398
No description provided.