---
title: "Test builds"
summary: "Internal test builds of Hypervibe, each named by its digest and source revision, with how far it gets. None is a release."
standing: "unavailable"
release: "No public release yet"
verified: "2026-11-13"
---

# Test builds

Internal test builds of Hypervibe, each named by its digest and source revision, with how far it gets. None is a release.

> Standing: Unavailable. A known missing requirement or an unsupported combination. Release: No public release yet.
>
> Hypervibe has no public release yet. Until one exists, no page here is Qualified and nothing can be installed from these docs. Every page states its standing, so you can tell an approved plan from something you can run.
>
> This is the Markdown copy of https://hypervibe.app/docs/releases/test-builds/

> **Unavailable** A test build is unsigned, and it is not a release. The newest test build, C2, installs and starts its services, then stops at step 5. Testers follow the [install page](https://hypervibe.app/docs/start/install/), which says what each step does on the newest test build.

## A test build is one set, named by one digest

A test build is one installable set of Hypervibe's programs, built together and named by the SHA-256 digest of its manifest, and numbered C0, C1 and so on. C0's set holds six builds of four programs; a local install uses three of them: `hyper`, `hv-agent` and `hv-inferenced`. Each test build runs the same thirteen steps, from building the set to a paid run inside a spending limit. The first step that fails is the test build's frontier, and how far the frontier moves is how progress is measured.

A test build is unsigned and carries no support promise. It is not a release: [Releases](https://hypervibe.app/docs/releases/) lists those, and there are none yet. Each test build's programs are built for Linux on x86-64.

## Test builds so far

| Test build | Digest | Source revision | Target | Frontier | Label |
|---|---|---|---|---|---|
| C0 | `sha256:6a86148e7d107f36905634df8742c86464f66fe8564bc37068a97c8cf9d19256` | `98914dd044ec75d76268f0c78f316e984d3df023` | Linux x86-64 | Step 2, setup | Internal test build, unsigned, not a release |
| C1 | `sha256:a73be86cc24e63d457507354db2a5478e50232b44d88b4ea7efe736643c9736f` | `8245cdcabcf932d3ffc3657975e1f45e61c31706` | Linux x86-64 | Step 2, setup | Internal test build, unsigned, not a release |
| C2 | `sha256:7db7dea6f87f40fefe51e4ba156453661333db8965f5f5f0bf47e2dfdb2519a2` | `4ddf76c07d77fae09b1ddd6ca358a4c2cfb941a8` | Linux x86-64 | Step 5, connect a recording | Internal test build, unsigned, not a release |

No test build is published for download yet. When one is, this table gives its download beside its digest, and the install page says how to check the digest before anything runs.

## C0, step by step

| Step | What it checks | C0 |
|---|---|---|
| 1 | The set builds and its digest is recorded | Passed |
| 2 | `hyper setup` installs the set into an empty home folder | **Unavailable** Setup refuses with `state_owner_migration_not_composed`: this build's setup cannot yet run the stored-state migrations of the programs it installs. Nothing is changed, and setup ends with exit code 3 |
| 3 | The installed services start and the model service is ready | Not reached: nothing is installed |
| 4 | `hyper setup status` reports a healthy installation | **Unavailable** It reports that nothing is installed, and ends with exit code 4 |
| 5 | A model account or a recording is connected | **Unknown** The test connected no account and no recording, so this build's connection was not tried |
| 6 | `hyper exec` runs one task on a test repository | **Unavailable** This build doesn't have it. It says so in one sentence and ends with exit code 69 |
| 7 | `hyper session attach` shows the session | **Unavailable** There is no session to attach to without step 6 |
| 8 to 10 | Recovery after an interruption, an approval bound to its exact change, and a receipt with the run's cost | Not reached: they need a run from step 6 |
| 11 | An update that fails its health check goes back to the earlier version | Not tried: it needs a second test build |
| 12 | `hyper uninstall` removes the installation | Not reached: nothing is installed |
| 13 | One paid run with a real account, inside its spending limit | Not tried: no real account is used for a test build yet |

## What this build serves

C0's `hyper` serves 17 of its 415 named commands: `hyper version`, `hyper completion`, `hyper setup`, `hyper setup status`, `hyper update`, `hyper uninstall`, `hyper inference account connect`, `hyper session attach`, `hyper build recipe`, `hyper build run`, and the build-job commands `hyper job status`, `logs`, `wait`, `fetch`, `cancel`, `list` and `explain`. Serving a command does not mean it succeeds on C0: the steps above say what each install step does.

The other 398 are not in this build. Run without arguments, 69 of them say so in one sentence, "`hyper …` is planned but not available in this build", and end with exit code 69. The other 329 stop sooner in C0: they print a usage error for the missing argument and end with exit code 2. Later test builds are planned to reach the sentence for every command that isn't in the build.

## Where to go next

- [Install](https://hypervibe.app/docs/start/install/) gives the tester steps and what the newest test build does at each.
- [Releases](https://hypervibe.app/docs/releases/) lists public releases, which test builds are not.
- [Standings](https://hypervibe.app/docs/reference/standings/) explains Unavailable, Unknown and the other standings.