Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-06-19 · source-backed
For two years the pitch was that the model is the product. Cursor, the IDE built around being the best place to use frontier models, was the proof. So a model-agnostic terminal agent displacing Cursor from #1 is a real data point, not just leaderboard noise.
OpenCode, MIT-licensed and provider-agnostic, has crossed roughly 172K GitHub stars and about 7.5M monthly active developers, and topped LogRocket's June 2026 AI dev-tool power rankings, pushing Cursor out of the top spot. It supports 75+ providers from a single CLI: Claude, GPT-5.5, Gemini, DeepSeek, Grok, and local models through Ollama. The model is a pluggable dependency. The harness is the product.
I've watched my own workflow drift this exact direction. A year ago I cared which model I was using. Now I care more about the loop, the context management, the tool permissions, the file handoffs, and I want to swap the model underneath based on cost and the task. When GLM-5.2 lands at #2 on WebDev at $1.40/Mtok, the thing that lets me actually use it without rewriting my workflow is a provider-agnostic harness. OpenCode and GLM-5.2 are the same story told from two ends.
The thing to sit with: if the harness is the product and the model is a commodity input, the moat moves. It's not "we have the best model" anymore, because the best model changes every few weeks and half of them are open weights. The moat is the orchestration layer, the context engineering, the permission model, the integrations. That's good news for builders and bad news for anyone whose entire valuation rests on model exclusivity.
What to do: if you're still locked into a single-vendor IDE, try OpenCode for a week with two or three providers wired in. Even if you don't switch, the exercise of running the same task across Claude, GPT-5.5, and a local model teaches you how much of your output quality is the model versus your prompt and context discipline. My bet is you'll find it's more about the harness than you expect. That's the whole point.
Each link below shares sources, entities, or timing with this story.
Claude Code benchmarked against GPT / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Claude Code benchmarked against GPT); both cover CLAUDE, Cursor, DeepSeek, Gemini; overlapping topics (claude, cursor, provider).
Gemini competes with ChatGPT / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Gemini competes with ChatGPT); both cover Claude, Gemini, GLM, GPT; overlapping topics (best, gpt-5, moat, model, point).
Claude Code benchmarked against GPT / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Claude Code benchmarked against GPT); both cover CLAUDE, DeepSeek, Gemini, GLM; overlapping topics (claude, model).
Claude Code benchmarked against GPT / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Claude Code benchmarked against GPT); both cover CLI, Cursor, Grok, MIT; overlapping topics (best, claude, cursor).
Linked by a graph relationship (Claude Code benchmarked against GPT); both cover CLAUDE, DeepSeek, GLM, GPT; overlapping topics (claude, glm-5, model).
Claude Code benchmarked against GPT / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code benchmarked against GPT); both cover Claude, Cursor, Gemini, GPT; overlapping topics (claude, cursor, model).
Ollama supports DeepSeek / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Ollama supports DeepSeek); both cover DeepSeek, GLM, GPT, MIT; overlapping topics (glm-5, gpt-5, model, product).
Claude Code benchmarked against GPT / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code benchmarked against GPT); both cover Claude, GPT, MIT, OpenCode; overlapping topics (claude, harness, local, model, point).