Skip to content

docs(cli): DeepSeek's own API is now walked through OpenCode - #2349

Merged
lilyshen0722 merged 1 commit into
mainfrom
docs/cli-opencode-deepseek-walked
Oct 19, 2026
Merged

lilyshen0722 merged 1 commit into
mainfrom
docs/cli-opencode-deepseek-walked

Conversation

@lilyshen0722

Copy link
Copy Markdown
Contributor

The guide's DeepSeek note said DeepSeek's own API hadn't been called through OpenCode yet. It has now been walked: 2026-10-19 at 21:13Z, with a non-admin account, CLI 0.1.108, OpenCode 1.19.3, provider baseURL https://api.deepseek.com/v1 and model deepseek-v4-flash.

An @mention got the right answer in about 16 s, posted through the Commonly tool. The key was read into a 0600 file and deleted afterwards, and the agent was detached.

The note now gives the exact values walked and says they were walked. Docs only, one paragraph.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Wkz5axAzCvoLEFkZ5KtkKG

Walked 2026-10-19 21:13Z: a non-admin attach of OpenCode 1.19.3 on CLI
0.1.108, provider baseURL https://api.deepseek.com/v1, model
deepseek-v4-flash. The agent answered an @mention and posted through the
Commonly tool. The note no longer says the direct route is untried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wkz5axAzCvoLEFkZ5KtkKG

@lilyshen0722 lilyshen0722 left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Docs gate on #2349 at d60781a935515c9414a2c489ff231c72ea1223a3. main (e94e2abb) is an ancestor; one file, five lines; CI 13 pass / 2 skipping.

The note claims no more than the walk. Clause by clause against the five facts you stated:

  • The two values it tells a reader to set — baseURL https://api.deepseek.com/v1, model deepseek-v4-flash — are the ones you walked, and "with your DeepSeek API key in the key file" matches the 0600 key file.
  • "We walked exactly this against DeepSeek's own API on 2026-10-19" carries the date, and "exactly this" is the pair of values plus the key, which is what you ran.
  • "the agent answered an @mention and posted through the Commonly tool" is precisely what your evidence shows, and I checked that the evidence means what it says rather than taking the quoted line on trust: agent posted via tool this turn is emitted at cli/src/commands/agent.js:1768, inside the agentPostedItself branch — the wrapper saw a post the agent made through the Commonly tool and suppressed its own echo. That is the claim, not a weaker one.
  • The header's scope still matches the walk: macOS, CLI 0.1.108, OpenCode 1.19.3, Linux and Windows unwalked. 0.1.108 is main's cli version and opencode-ai is at 1.19.3 on npm today.
  • Nothing widens. It does not say DeepSeek works generally, does not extend to other models or platforms, and keeps failure open with "If DeepSeek refuses your request…". The following paragraph's "None has been walked yet" is still true read as other providers.

One thing the edit drops from the record, non-blocking. The previous text recorded a second verified fact: the same model walked through an OpenAI-compatible endpoint that serves it. That walk is now gone from the file, and the paragraph underneath — "Other OpenAI-compatible providers use the same file with their own baseURL and model. None has been walked yet." — reads, to someone pointing OpenCode at a proxy or gateway rather than at DeepSeek, as though no such endpoint has ever been walked. It is an under-claim, so it doesn't offend the property I was asked to check; it costs a reader on a stand-in endpoint the one statement that covered them. A clause noting that a DeepSeek-serving OpenAI-compatible endpoint was also walked would keep both facts.

What I could not check, stated rather than implied. Your fourth fact — that the key came from a deployment route setting no api_base, so the call reached DeepSeek rather than a stand-in — rests on deployment configuration I don't read from here. The note's own claim survives that limit, because where the request goes is decided by the baseURL in the environment file, and that value is in the text and in your report. The key's provenance is yours to vouch for; the endpoint claim stands on the config either way.

Written by Vera, a Commonly agent — https://commonly.me/pods/6a8f6dc7a1dccf2e02f31015

GATE: PASS

@lilyshen0722
lilyshen0722 added this pull request to the merge queue Oct 19, 2026
Merged via the queue into main with commit 11920e8 Oct 19, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant