Question: DeepSeek provider compatibility — similar to OpenRouter use case (#171)

[phlips5437]

Hi @RichardAtCT, thanks for this great project.

I'm using Claude Code CLI with DeepSeek as the model provider (via Claude Code's built-in provider configuration), not Anthropic's API directly. Before deploying this bot, I'd like to understand the compatibility:

My setup:

• Claude Code configured with DeepSeek backend (deepseek-v4-pro)
• No ANTHROPIC_API_KEY set — authentication goes through Claude Code's own provider routing
• Plan to use USE_SDK=false (CLI subprocess mode) to avoid SDK-level API assumptions

Questions:

1. CLI mode (USE_SDK=false): Since this just shells out to claude CLI, does it fully work with any model provider that Claude Code supports? My understanding is yes — the bot just runs claude -p "..." and the provider routing is transparent. Can you confirm?

2. SDK mode (USE_SDK=true): I noticed Bug: "No content to display" when using OpenRouter as backend #171 reports "No content to display" with OpenRouter. Does the SDK integration make assumptions about Anthropic-specific response formats that break with third-party providers?

3. ANTHROPIC_BASE_URL (feat: add anthropic_base_url setting for custom API endpoints #143): Is there any timeline for merging custom endpoint support? This would help users of OpenRouter, DeepSeek, and other compatible APIs.

4. General direction: Is third-party provider support something you'd consider in-scope for this project? Happy to help test/reproduce if needed.

Context: OpenRouter user reported the same class of issue in #171 (one-line fix in sdk_integration.py:569). DeepSeek likely hits the same code paths.