Harness Hub¶

SuperQode is the harness layer for coding agents. The Harness Hub is where those harnesses are discovered, built, inspected, run, evaluated, and optimized through one rich, browsable terminal experience.

The Hub brings SuperQode native harnesses, established coding agents, ACP agents, optional runtimes, model and task presets, and repository-owned custom HarnessSpecs into one browsable terminal surface. It does not replace those agents or require a separate desktop application. It gives them a consistent discovery, setup, switching, continuity, policy, and evidence layer.

Open the Hub¶

Launch SuperQode in a repository and enter:

:hub

The Hub is a full terminal screen rather than a block appended to the conversation. Use the mouse or keyboard to:

• search names, runtimes, sources, and descriptions
• filter to Ready, Needs setup, Your harnesses, or Coming soon
• inspect setup, runtime, provenance, and session-continuity details
• use an available harness or follow its setup route
• start the custom harness builder

Press / to focus search, arrow keys to move, Enter to inspect or use the selected entry, I to inspect, B to build, and Esc to return to the coding session. Buttons and rows are also mouse-enabled.

What appears in the Hub¶

An entry marked Ready is usable in the current environment. Needs setup means the catalog knows the route but a dependency, executable, authentication step, or service is missing. Integration pending marks an ecosystem entry SuperQode cannot yet run. These states describe readiness, not a security certification.

The Hub catalogs harnesses, and only harnesses. Model providers, local inference servers, memory providers, sandboxes, protocol surfaces, observability sinks, and chat channels are all real integrations, but someone opening the Hub is choosing a harness, not assembling a dependency list. Those live in the integration catalog, and models are selected with :connect once a harness is active.

In the terminal these states are measured on the machine you are using. In the published snapshot they cannot be, so --public reports the structural answer instead: harnesses SuperQode ships are Ready for everyone, and any route that wraps an external CLI, account, or optional package is Needs setup for everyone. A public catalog must never report the exporting machine's installed binaries as product truth.

Logo ownership¶

The logo identifies who owns the runnable implementation rather than the model family or upstream project associated with it. Official vendor connections, ACP agents, inference engines, and upstream runtimes use their official logos. SuperQode-built native harnesses and built-in presets use the SuperQode logo, even when they target a model family such as GLM, Qwen, Kimi, Gemma, DeepSeek, or MiniMax.

For example, the official Prime Agent connection uses the Prime Intellect logo. The prime-agent-python built-in preset uses the SuperQode logo because its host integration and HarnessSpec are maintained by Superagentic AI. The entry's provenance and Based on fields still identify the upstream runtime without implying that the SuperQode implementation is an official vendor product.

Evaluation and optimization¶

The Hub is where harnesses are evaluated and optimized, not only discovered, so every HarnessSpec entry carries the commands that measure it and improve it, next to the commands that run it.

Inspecting a native or repository-owned harness shows an Evaluate block and an Optimize block:

superqode harness test --spec harness.yaml
superqode harness eval --spec harness.yaml --tasks eval-tasks.yaml
superqode harness bench --manifest harnessbench.yaml

superqode harness optimize-omni --spec harness.yaml --tasks eval-tasks.yaml
superqode harness optimize --spec harness.yaml --tasks eval-tasks.yaml
superqode harness promote stage

Vendor and ACP entries show neither: the connected agent owns its own loop, and the Hub says so rather than implying SuperQode can tune it.

The optimizers and evaluators themselves are not Hub entries. Every one follows the same contract: start from a versioned artifact, measure it, stage a candidate, gate the candidate, and let a human adopt it. See Optimization Story for the full workflow and Running, Measuring, and Optimizing a Harness for the run/measure/optimize split.

ZCode¶

ZCode is indexed under Ecosystem watch as Z.AI's official desktop coding harness for GLM-5.3. Inspecting it in the TUI shows its agent-loop ownership, tools, supported platforms, official installation and documentation, and the current SuperQode integration boundary.

ZCode is not directly runnable from SuperQode today. Its public documentation does not currently expose an ACP server, headless CLI, or external agent SDK, so the Hub marks it Integration pending rather than presenting a false setup command. This is separate from SuperQode's supported :connect zai general-API route and the community :connect glm-cli ACP agent.

jcode¶

jcode is indexed under Ecosystem watch as an MIT-licensed terminal coding harness written in Rust, focused on low memory use, fast start, and parallel agent swarms.

It is not runnable from SuperQode today, but its entry states a different reason from ZCode's. jcode documents a headless jcode run, a TypeScript SDK, and a versioned harness API, so a SuperQode route is buildable once someone implements and tests one. The Hub distinguishes "no published integration surface" from "a surface exists but no connector has been built yet".

Results and Activity¶

Important actions no longer depend on the bottom of the transcript. Harness details, setup failures, and other consequential results open in a focused screen. Completed state changes also produce a short notification and a compact transcript receipt.

Use :activity to revisit session results and run their primary recovery or next-step action. This gives both mouse users and keyboard users a clear way to recover something they dismissed or did not notice.

CLI and catalog data¶

The noninteractive CLI exposes the same inventory used by the TUI:

sq hub
sq hub list --search codex
sq hub list --readiness ready
sq hub show codex
sq hub list --json
sq hub list --public --json

The JSON form is a versioned interface for documentation, release automation, and the SuperQode landing page. Use --public for a publication-safe snapshot that excludes repository and user-registry harnesses. Each record includes identity, category, runtime, source, readiness, integration level, continuity behavior, setup guidance, and warnings. Executable internal objects are deliberately excluded.

Inspect data also includes installation guidance, TUI and shell commands, documentation and upstream links, capabilities, tools, policies, HarnessSpec inheritance, and a curated popularity rank. Native and repository-owned HarnessSpecs derive their tool and policy details from the spec itself. Vendor and ACP entries state when the external agent owns the tool loop instead of guessing at a tool inventory.

For example, inspecting Antigravity shows its SuperQode command family:

:connect antigravity
:agy status
:agy agents
:agy models
:agy plugin list

Inspecting a native harness such as Workbench shows its declared tools, sandbox, approval profile, shell and network policy, checks, workflow, and the equivalent superqode harness run command.

The index reflects the current installation and repository. A website build can snapshot it for public discovery; the TUI overlays the current machine's actual readiness and project harnesses when opened.

Build your own harness¶

Choose Build your own in the Hub or use:

:connect build

The builder can create a native HarnessSpec, import a compatible agent or harness, or begin from a preset. Store the result in the repository when the team needs behavior that is portable, reviewable, evaluable, and versioned with the code.

Continue with Bring Your Own Harness for the authoring workflow and Harness Engineering for the lifecycle from design through evaluation and promotion.

Model search migration¶

Earlier versions used :hub as an opt-in local model-search mode. Model search now has the explicit command:

:local search <model>

During migration, :hub model <model> remains an alias. Plain :hub always opens the Harness Hub.