When we launched SuperQode, we built it as a harness layer for coding agents. The first optimisation was agent experience: CLI surfaces, A2A, ACP, UHP, MCP, and the other protocol seams that let agents run with policy, tools, sessions, and evaluation. The terminal UI was there from the start, but it was secondary. We expected most serious use to go through those agent-facing paths.
Developers kept praising the TUI anyway. People were already using it as a daily coding surface: connect a provider or an agent, work in a repository, approve tools, resume a session. That feedback changed the priority. If humans were going to live in this interface, it needed the same care we put into the harness and protocol layer.
This release makes that decision concrete. We polished the terminal experience so developers can use SuperQode as a coding agent: connect to a harness, an external coding agent, or a model provider, and keep the loop readable. The product position does not change. SuperQode remains the harness layer for coding agents. The TUI is how that layer becomes comfortable for people as well as for agents.
From agent-first protocols to a developer-ready terminal
SuperQode already opens connections across different kinds of coding agents and different protocol layers. You can use built-in harnesses, bring an ACP agent, talk to providers through BYOK or local models, or build your own harness when the stock paths are not enough. That breadth is intentional. The missing piece for many developers was not another protocol. It was a terminal that made those choices easy to see, easy to switch, and easy to resume.
So this release focuses on developer experience in the TUI: connection menus, themes, multiline input, tool output, approvals, and sessions. Opening SuperQode, picking a route, and getting work done should feel ordinary, not like configuring a stack before you can ask a question about a repository.
What we polished in the TUI
The visible work is the screen:
- Clearer connect menus for BYOK, local models, ACP, and supported account routes
- Themes and a multiline composer that stay usable on longer prompts
- Tool output that stays collapsed until you need detail
- Approvals, cancellation, and retry that stay understandable while a turn is running
- Session list, resume, and harness switching that keep the selected harness and model
That is the core of the release story: a terminal people can demonstrate and use without fighting the chrome. Full detail lives in the docs and on superqode.dev.
Connect any harness, agent, or provider
The connect surface is meant to match how teams already work. Use a SuperQode harness such as Core or Workbench when you want the native loop. Connect an ACP coding agent when that agent is the right runtime. Use BYOK or local models when you want a provider you already pay for or host. Build or customise a harness when you need a different control path.
This release does not invent that matrix. It makes the matrix easier to enter from the TUI so the same SuperQode install can serve as the place you start coding work.
Pi launched features people noticed; PiPy already had depth to show
While we were polishing the TUI, the Pi coding agent shipped new features that drew attention across the ecosystem. Looking at that wave, we recognised a familiar pattern. Several of the capabilities people were reacting to already existed on our Pi-inspired path, but they had not been given a clear surface or a clear announcement. The work stayed under the hood while attention stayed on protocols and harness plumbing.
CodeMode, WorkOrders, and MCP were already part of SuperQode. Shared MCP configuration and client controls were already in the product. What we did now is polish that surface, wire PiPy into the latest TUI behaviour, and bring the quieter pieces into view: images through the provider gateway, OAuth identity and refresh hardening, plus optional Monty programs and coding WorkOrder recovery for teams that opt in.
So we gave PiPy, SuperQode's Pi-inspired Pythonic harness, the same polished treatment as the rest of the TUI and made those existing strengths easier to find and use.
PiPy and Pi remain distinct integrations. Connect PiPy with :connect harness-pipy. Connect the Pi coding agent, where supported, with :connect acp pi. PiPy covers a tested subset of pi-shaped behaviour. This release does not include a live Pi cost or speed comparison. When you show the product, connect each path on its own so the difference stays obvious. See the PiPy docs and the product overview on superqode.dev.
Herdr integration
We also added Herdr host integration. When the SuperQode TUI runs inside a Herdr pane, Herdr can show idle, working, and blocked status for approvals and questions. SuperQode detects Herdr automatically. Outside a Herdr pane, that reporter stays inactive.
For developers who already orchestrate agents in Herdr, the status line is the practical win: the host reflects whether SuperQode is waiting on you or still working.
Try this release
Install:
curl -fsSL https://superqode.dev/install.sh | sh
sqAlready installed:
superqode update
# or: uv tool upgrade superqodeOpen the TUI on SuperQode, connect the harness, agent, or provider you want, and run a task against a real repository. For PiPy use :connect harness-pipy. For the Pi coding agent use :connect acp pi. Shared MCP controls are available in the TUI and through sq mcp list, login, logout, and reconnect. More setup detail is in the docs.
What comes next
This release sets the terminal up as a place developers can stay. Next we are extending that surface in a few concrete directions.
We are releasing deeper title and subscription integration with the harnesses you already use inside SuperQode, so account-backed routes sit beside BYOK and local models in the same connect flow. We are continuing to invest in the protocols that make those connections reliable: ACP, A2A, MCP, UHP, and the seams that keep harnesses interchangeable without forcing a rewrite.
We are also bringing the strongest announced capabilities from across the harness ecosystem into SuperQode itself, so you spend less time switching tools to get a feature you already need. And we are pushing the developer experience further so you can build and refine your own harness from the terminal interface, not only consume the ones we ship.
The through-line stays the same: SuperQode as the harness layer, the TUI as the daily way in, and protocols as the way agents and providers stay connected.
What we want to hear now
Tell us where the terminal already feels like a coding agent you would keep open all day, and where connect, sessions, PiPy, Pi via ACP, or Herdr status still get in the way. This release treats the TUI as a first-class product surface without walking away from the harness and protocol work SuperQode was built for.
Release: v2.5.0
- Product: superqode.dev
- Docs: docs.superqode.dev
- PyPI: superqode 2.5.0