All stories
Nexus-CLI Launches Community reports

Nexus-CLI brings a DeepSeek web account to coding agents and Ollama clients

The new Go bridge advertises Claude Code launchers and familiar API formats without a paid DeepSeek API key, but its compatibility and free-access promises need careful reading.

By AITrending2 min read
Sources (3)

Why now The author submitted Nexus-CLI to Hacker News on October 21 at 04:37 UTC; the inspected repository commit is dated the same morning. This is a community introduction, not a new DeepSeek model release.

Nexus-CLI wants a DeepSeek web login to become a common backend for coding agents and Ollama-compatible apps. Introduced by its author on Hacker News on October 21, the community Go project advertises a local API bridge to DeepSeek’s hosted chat service without requiring an official paid DeepSeek API key.

The attraction is reusing familiar clients. The English README lists OpenAI Chat Completions, Anthropic Messages, OpenAI Responses and native Ollama-style routes, alongside launch commands for Claude Code, Codex, OpenCode, Goose and Aider. Its model names are deepseek-chat and deepseek-reasoner, described by the author as V3 and R1. Those labels are not evidence of a newly released model or checkpoint.

A bridge above the provider

This is a standalone executable and proxy, rather than a plugin installed inside those assistants. The documented route is cloning the repository, building with go build -o bin/nexus ., linking a DeepSeek web account and starting nexus serve on port 9655. The author also offers nexus launch claude and other launchers that start the proxy for a selected harness.

Authentication uses a web-session token, entered manually or captured through the project’s Chrome login flow. That means trusting the bridge with account credentials. Prompts still go to DeepSeek’s hosted service: an Ollama-shaped endpoint does not turn this into local model inference.

The README presents web-account access as free, but does not establish an unlimited service guarantee. Its account-pool feature is advertised as rotating accounts around rate limits; that should not be read as proof that upstream limits disappear.

Compatibility remains a claim

The author’s blanket Claude Code compatibility language and advertised proof-of-work timing have not been independently validated here. The README does not specify tested version ranges for the listed coding harnesses, so the integration list should be treated as advertised support rather than a verified compatibility matrix.

There is also a concrete installation mismatch: the README says Go 1.20+, while the inspected go.mod declares Go 1.26.1. Builders should check the manifest before relying on the README’s minimum. The code is MIT-licensed; that software license does not establish rights, pricing or availability for DeepSeek’s upstream service.

For developers exploring alternative backends, the news is the proposed connection between a web account and existing agent workflows. It is not a demonstrated replacement for every supported API or a promise of unrestricted model access.

Related reading