Skip to main content

Feature status

This page is the public source of truth for what EvalGate ships today. It describes release maturity, not aspirations. The current-behavior manuals explain how each surface behaves, fails, and exposes evidence.
EvalGate is currently offered as a controlled beta. A route, screen, or test by itself does not make a feature generally available. Features remain Beta or Experimental until their full acceptance evidence passes on the released commit.
The understand-first authoring path is Experimental in the current source tree. Local TypeScript and Python CLIs have quick and deep preview modes plus explicit apply to the canonical evalgate.product.json. This is not a released-availability claim: REST, mounted web authoring, marketplace distribution, controlled coding-agent compatibility proof, and package and release-environment evidence remain pending.

Status definitions

The Evaluate your subagents workflow is Experimental in the current source tree. It extends the local TypeScript and Python harness record and harness optimize commands with bounded delegation evidence, an independent expected-root frame, whole-task resource accounting and exploratory comparisons. The deterministic recipe exercises synthetic metadata, not live native fork behavior. It requires a build containing the extension; package distribution, automatic host instrumentation and live empirical validation are not claimed. These reports cannot authorize mutation or promotion. Status is reviewed against the released commit. If documentation and runtime behavior disagree, treat the more restrictive behavior as authoritative and report the mismatch.

Current inventory

Current released identities: 3.10.0 application and 3.10.0 SDK (TypeScript), anchored to tag sdk/v3.10.0. This minor release ships the credential-free local gate (init --local) for cloud coding agents, hardens release-evidence honesty, and keeps the OpenAPI contract at 7.0.0. Complete governed release evidence (OIDC publish + Required Test Lanes) remains open. The Python package remains governed separately. The latest fully executed Required Test Lanes evidence remains the 3.7.1 artifact at merge commit 46d7fe6c58dadefa58fd5a5e2ac6edfa82ef6919 (PR #241). Owners are accountable teams, not guarantees of support response time. The released 3.10.0 TypeScript package includes the activation-compression workflow from 3.9.0 plus credential-free local start: device-flow login, whoami, remote-revoking logout, auto-detecting link, unified status, control-plane open, TTY-aware init, and init --local for sandboxes without account, browser, GitHub remote, or network. Durable organization/repository/root linkage remains stored in non-secret version 2 project context separately from the exact target SHA and immutable manifest of the last cloud activation. status derives local-gate readiness from the same preflight as gate and reports link, checkout, cloud snapshot, local-gate readiness, and cloud-target readiness separately. Python package-release parity, a live OAuth/repository journey, and exact-head required-lane proof remain open; hosted baseline/gate/trace fields remain unavailable when the activation API cannot supply them.

How to read client gaps

The released 3.7.1 application contract covers every reviewed public API operation and generates compile-checked TypeScript contract types. Exact-head release verification passed, but that does not imply a dedicated convenience method in the TypeScript SDK, Python SDK, or CLI. Missing high-level client workflows are stated explicitly; use the API reference when only the typed REST contract is available.

Maintenance policy

A status change requires all of the following in the same released commit:
  1. A supported UI or public API workflow with documented permissions and failure behavior.
  2. OpenAPI coverage for every public route and generated-client parity where promised.
  3. Tests at the appropriate unit, route, database, and end-to-end layers.
  4. Observable evidence semantics, incomplete-state behavior, and operator recovery guidance.
  5. An owner review of this inventory and the matching current-behavior manual.
Roadmap documents may explain direction, but they do not override this inventory.