Here's a summary of all user-facing changes on Superconductor from May 24-30:
Major changes
Opus 4.8 support
Claude Opus 4.8 is now available as a Claude Code agent in Superconductor. You can select it when launching new implementations, and automatic best available agent fallbacks now prefer Opus 4.8 over older Opus models when your Anthropic account or API key is connected.
Other changes
Benchmarks are available on every project
Benchmarking is now out of beta and is available in all projects by default. The Benchmark action is now available by default from the project header.
Gemini CLI profiles have been retired
Gemini CLI profiles are no longer offered when configuring agent credentials or launching new implementations. You can still use Gemini models in Superconductor through OpenCode, and you can still add a Gemini API key in Project Settings when you want to use Superconductor-provided Agent Skills such as image generation, video understanding, or audio understanding.
Agent profile lists are easier to scan
Agent selection menus are more consistent across Superconductor. The agent dropdown on new tickets, the default-agent selector in Account Settings, and other implementation launch controls now group providers in the same order, so configured agents are easier to find.
OpenCode naming is more consistent
OpenCode is now styled consistently across settings, work logs, legal copy, and agent labels.
Fixed issues
Diff comment actions fit narrow panes
The Add to Message and Cancel buttons in diff comments now wrap cleanly in narrow diff panes, so long button text no longer overflows the comment widget.
Clearer Claude Code failure messages
Claude Code runs now report invalid API keys, overloaded Anthropic API responses, and non-JSON Anthropic API errors more clearly, making failed runs easier to diagnose.
OpenCode errors are surfaced more reliably
OpenCode runs that return no JSON stream or provider error output now show a useful failure message instead of failing silently or hiding the upstream error.
Sandbox failures use clearer language
When a cloud sandbox — the VM where an implementation runs your repo, tools, and live preview — is no longer available, Superconductor now says that directly instead of referring to the underlying cloud instance.
Other News
We published a new engineering post on teaching coding agents to debug Rails memory issues with derailed_benchmarks. It walks through how we used background agents, benchmark artifacts, and Guided Review on Superconductor to reproduce a production memory leak, verify the fix, and send an upstream PR for the affected gem.
Have feedback or ideas for things you'd like to see on Superconductor? Let us know!