Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-17 · high
Its first tagged release landed four days after launch, with GitHub stars already past 145,000.
Why now: The tag posted August 17, four days after the repo appeared and its star count first crossed 33,000.
DeepSeek shipped dsh-v0.1.0-rc.7 for its Harness runtime at 12:01 UTC on August 17, the first tagged release since the repo appeared August 13.
The runtime manages Codex and Claude Code as subagents through a Job Panel. That means a team's agent choice and its orchestration choice no longer have to be the same decision.
Its GitHub star count went from about 33,000 hours after launch to 145,439 four days later. I don't know how much of that growth is organic, and wouldn't read star velocity alone as a quality signal.
SeemSeam's claude_codex_bridge shipped v8.6.9 the same day, adding DeepSeek Harness as a Developer Preview provider key, dsh. That's separate from the existing deepseek key, which still points at Deep Code CLI.
dsh-market, an in-app plugin marketplace, went from creation on August 14 to 791 stars and 55 forks. awesome-dsh-plugin sits at 7,257 stars, dsh-web-ui at 3,977, dsh-context at 177. Discovery moved from a curated README to an in-app marketplace in under a week.
The bridge's release notes hold the sharpest engineering detail of the day. DSH completion requires three things together: an exact durable source.rpcId, a committed non-empty assistant reply from the same turn, and a native turn/end(completed) event.
The terminal pane is demoted to a lifecycle and log carrier, with no authority to declare a prompt, reply, or completion. Restore only observes, so it never reposts a prompt. It's the clearest public admission I've seen that scraping terminal text can't tell you when an agent turn actually finished.
Credentials, skills, memory, and caches stay inside an agent-private DSH_HOME, copied one direction only.
Whether this holds depends on Anthropic and OpenAI tolerating third-party wrappers instead of locking down their APIs.
Each link below shares sources, entities, or timing with this story.
Claude Code uses MCP / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude Code uses MCP); both cover Claude Code, Codex, GitHub, MCP; reported by the same outlet (github.com).
DeepSeek released DeepSeek Harness / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (DeepSeek released DeepSeek Harness); both cover August, DeepSeek, DeepSeek Harness, DSH; reported by the same outlet (github.com).
Claude Code partners with Telegram / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code partners with Telegram); both cover August, Claude Code, Codex, MCP; reported by the same outlet (github.com).
Claude Code uses Kimi K3 / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses Kimi K3); both cover Claude Code, Codex, DeepSeek, MCP; reported by the same outlet (github.com).
openclaude uses DeepSeek / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (openclaude uses DeepSeek); both cover Claude Code, Codex, DeepSeek, GitHub; reported by the same outlet (github.com).
Vercel uses DeepSeek / Shared entities / Same source domain / Shared topic
Linked by a graph relationship (Vercel uses DeepSeek); both cover August, Claude Code, Codex, GitHub; reported by the same outlet (github.com).
OpenCode competes with Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (OpenCode competes with Claude Code); both cover August, Claude Code, Codex, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (OpenCode competes with Claude Code); both cover Claude Code, Codex, GitHub, MCP; reported by the same outlet (github.com).