v0.8.15 — Platform & Market Expansion

Tracking issue. Nothing is committed; everything is up for discussion and scoping.

1. Platform-aware keybinding labels (Alt → Opt on Mac)

Mac keyboards label the key "Option" (⌥), not "Alt." Everywhere we display shortcuts — README, KEYBINDINGS.md, help overlay, keybinding hints — says "Alt" which is technically correct for the keycode but semantically wrong for Mac users.

What to do:

• Detect platform at render time in the TUI
• Display "Opt" or "⌥" on macOS, "Alt" on Linux/Windows/HarmonyOS
• Update all documentation to at minimum note the mapping (Alt = Opt on Mac)
• KEYBINDINGS.md could use Alt / Opt as a compromise in the static docs

HarmonyOS uses standard PC keyboard layout with Alt keys, so no special handling needed there — Alt is correct.

2. Web search backend — make Bing primary or configurable

Current state: web_search tool in crates/tui/src/tools/web_search.rs already has a Bing scraper as fallback. It tries DuckDuckGo first; if DDG returns a bot challenge or empty results, it falls back to Bing. The Bing scraper works — it parses b_algo result blocks from the HTML search page.

Why Bing:

• Accessible inside China (DDG is slow/unreliable there)
• Better search quality in many regions
• No bot-challenge issues that DDG increasingly triggers

What to do:

• Add web_search.backend = "duckduckgo" | "bing" | "auto" to config.toml
• "auto" could try DDG first then Bing (current behavior), or geolocate
• Tool description should reflect which backend is active
• Could also add web_search.backend = "baidu" as a future option for Chinese-language queries

3. Chinese market services — what are we missing?

DeepSeek TUI already has:

• api.deepseeki.com (China endpoint) support via base_url config
• Cargo mirror instructions (TUNA) in README
• npm --registry=https://registry.npmmirror.com documented
• zh-CN README and locale = "zh-Hans" UI

Potential gaps to evaluate:

• Baidu search as a web_search backend — dominant in China, would need HTML scraper similar to the Bing one
• WeChat/Feishu/DingTalk notifications — for turn-complete alerts on platforms Chinese developers actually use
• Alibaba Cloud / Tencent Cloud sandbox backends — extend the pluggable sandbox system (already has Alibaba OpenSandbox via feat(sandbox): pluggable SandboxBackend + Alibaba OpenSandbox adapter (#516) #645)
• Gitee mirror for source installs — GitHub can be slow/unreliable in China
• Chinese model providers — e.g. Alibaba Tongyi Qwen, Baidu Wenxin, Zhipu GLM as first-class providers (currently any OpenAI-compatible endpoint works via base_url, but first-class support would mean provider-specific pricing, thinking-mode mapping, etc.)

None of these need to ship in v0.8.15 — this is a research/scoping item to figure out what would have the most impact.

4. AgentScope harness

AgentScope is Alibaba's Apache 2.0 multi-agent framework. It supports LLM backends, tool-calling, and a service-oriented architecture where agents can be deployed as services.

Opportunity: Make deepseek-tui work as an AgentScope-compatible agent. The existing serve --http runtime API is the natural foundation — AgentScope agents communicate via HTTP/SSE or stdio, which we already have.

What this might look like:

• Implement the AgentScope agent protocol on top of the existing runtime API
• AgentScope's ReActAgent pattern maps well to our Plan → Agent tool-call loop
• Could expose as deepseek serve --agentscope or a standalone mode
• Sub-agents could map to AgentScope's multi-agent orchestration

This is the biggest item and likely a multi-release effort. v0.8.15 scope should be investigation + proof-of-concept, not full integration.

5. Cost observation (note, not a bug)

User confirmed cost tracking works correctly on deepseek-v4-pro. The $0.00 issue from #754 may be specific to deepseek-v4-flash or configurations where reasoning tokens are the only output. The investigation in #754 should resolve this.

Summary