Skip to content
Oday Bakkour
Back to Knowledge Hub
aidevelopment

AI Coding News: July 26, 2026 — OpenCode Rebrands to Anomaly and Ships v1.18.5

Oday Bakkour profile photo
Oday Bakkour
6 min read
Share
AI Coding News: July 26, 2026 — OpenCode Rebrands to Anomaly and Ships v1.18.5

After two weeks of headline launches — Claude Opus 5, Cursor Router, Copilot's metrics dashboard — July 26 is a quieter day, and that is itself useful information. The one tool that moved is OpenCode, and it moved in two directions at once: its GitHub home changed owners, and its desktop client took a first visible step toward a new server architecture.

Meanwhile OpenAI's Codex CLI is deep into a release grind that has not yet produced a stable tag. Here is everything that actually shipped, and why the quiet stretches at Claude Code, GitHub Copilot, and Cursor matter as much as the noisy ones.

OpenCode's GitHub Home Renames From sst to anomalyco

The repository that has shipped OpenCode since its debut has moved from github.com/sst/opencode to github.com/anomalyco/opencode. The old URL still redirects for now, so clones, CI jobs, and install scripts pointed at the sst org keep working — but GitHub org renames are not a permanent guarantee, and anything pinning issue links, release URLs, or raw file paths against the old namespace should be updated rather than left to redirect indefinitely.

The rename tracks a broader shift: the team behind the SST serverless framework and OpenCode has been operating under the Anomaly name, and the GitHub org is catching up to that branding. OpenCode itself keeps its name and its 160K-plus star count — this is a landlord change, not a product change.

v1.18.5: Model-Specific Bug Fixes

OpenCode v1.18.5 landed July 24 as a pure fix release, five days after v1.18.4. Every change is provider-specific, which makes it a good filter for whether this release matters to you:

  • Claude — adaptive thinking handling improved across more response shapes, so fewer edge cases drop or mishandle reasoning content mid-turn.
  • OpenAI Responses models — a phase-handling bug that could break a conversation mid-stream is fixed.
  • Mistral — prompt caching is stabilized and reasoning history now survives across turns instead of resetting.
  • MiniMax M3 — thinking-variant selection is corrected, and cache keys are now matched to the right SDK per provider instead of a shared default.
  • Search — grep results now preserve symlink paths instead of resolving them away, which matters for monorepos that lean on symlinked packages.

The Desktop App Learns to Speak Two Server Dialects

The more consequential part of v1.18.5 is on the desktop side, where the client picked up explicit support for what the changelog calls "current" servers alongside the existing "legacy" ones — terminal transport, review data, session actions, timelines, and event streaming were all extended to work against both, and the app now auto-detects which kind of server it is talking to.

That dual-support layer is the visible seam of a larger rewrite already underway: OpenCode's move from Bun to Node, a split into standalone tui, cli, server, and core packages, and a desktop shift from Tauri to Electron. Shipping legacy/current compatibility first, rather than cutting over in one release, is the safer path for a tool with an install base this large — it means existing sessions and hooks keep working while the server underneath is replaced piece by piece.

OpenAI Codex CLI Grinds Through Eleven Alpha Builds

Since Codex CLI 0.145.0 went stable on July 21, the 0.146.0 line has cycled through eleven pre-release builds — alpha.3 through alpha.10, plus a alpha.3.1 and an alpha.10.1 patch — landing as recently as July 25 at 20:29 UTC. None of them have been promoted to a stable tag.

That pace is normal for Codex CLI's release rhythm and is not itself a red flag, but it is a signal worth tracking if you build automation on top of the CLI: pin to the last stable tag (0.145.0) for anything production-facing, and treat the 0.146.0 alphas as a preview of paginated thread history, expanded /import support, and the multi-agent V2 experience that 0.145.0 introduced as experimental — features that are still being hardened, not finished.

Elsewhere in AI Coding: A Quiet Day

Claude Code — no new build since yesterday's v2.1.220 reliability pass that followed the Opus 5 default-model switch. See the full changelog if you have not upgraded yet.

GitHub Copilot — the changelog has stayed at July 24's Opus 5 rollout; no new entries today.

Cursor — the changelog still shows Cursor Router (July 22) as the newest entry.

Devin Desktop — v3.5.17 (July 19) remains current, with its Windsurf-to-Devin hooks migration command and multi-workspace Devin Local support. Full changelog here.

What to Actually Do This Week

  • If any script, CI job, or doc hardcodes github.com/sst/opencode, switch it to github.com/anomalyco/opencode now rather than relying on the redirect.
  • Running OpenCode against Claude, Mistral, or MiniMax M3? Upgrade to v1.18.5 for the reasoning and caching fixes — they are provider-specific, so check the list above before assuming it applies to your setup.
  • OpenCode Desktop users may see a legacy/current server toggle appear during this transition — that is expected, not a bug, while the underlying server architecture changes.
  • Keep Codex CLI automation pinned to 0.145.0 until a stable 0.146.0 tag appears — the current alpha stream is not meant for production pins.

The Bigger Picture

None of today's changes are dramatic on their own, and that is the point worth noting after a fortnight of default-model swaps and router launches: the unglamorous work — renaming an org without breaking clones, adding compatibility shims before a server rewrite ships, fixing reasoning-history bugs one provider at a time — is what keeps a tool with 160K stars usable while it changes underneath its users.

It is also a useful contrast to Windsurf's abrupt rebrand into Devin Desktop earlier this month, where Cascade was deprecated outright rather than run in parallel. OpenCode's legacy/current server split suggests a team choosing the slower, less disruptive migration path — worth watching as the rest of the v2 rewrite lands in the coming weeks.

References and Further Reading

Comments

Share your thoughts and join the conversation

Leave a Comment

Loading comments...
Add Oday Bakkour as a preferred source on Google
RELATED