| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
All checks were successful
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (pull_request) Successful in 6s
wai-quantum command line / does this change touch it (pull_request) Successful in 9s
WAI energy receipts / does this change touch it (pull_request) Successful in 10s
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 13s
wai-quantum contract / does this change touch it (pull_request) Successful in 7s
wai-quantum docs, course and locales / does this change touch it (pull_request) Successful in 9s
wai-quantum editors / does this change touch it (pull_request) Successful in 9s
wai-quantum for Python / does this change touch it (pull_request) Successful in 8s
wai-quantum studio and desktop / does this change touch it (pull_request) Successful in 9s
wai-quantum views in agent hosts / does this change touch it (pull_request) Successful in 10s
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (pull_request) Successful in 41s
wai-quantum contract / the policy is linked, and the deprecations page reads (pull_request) Successful in 6s
wai-quantum command line / command line · macos (pull_request) Successful in 1m16s
wai-quantum command line / command line · linux (pull_request) Successful in 2m16s
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (pull_request) Successful in 2m47s
wai-quantum docs, course and locales / the Studio's words in every locale · linux (pull_request) Successful in 9s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 3m39s
wai-quantum contract / schemas and the committed tool lists · linux (pull_request) Successful in 3m30s
wai-quantum docs, course and locales / the course and the command line's languages · linux (pull_request) Successful in 1m50s
wai-quantum contract / API compatibility · linux (pull_request) Successful in 5m1s
wai-quantum editors / editors · linux (pull_request) Successful in 2m13s
wai-quantum for Python / python · linux (pull_request) Successful in 2m36s
wai-quantum studio and desktop / studio · browser (pull_request) Successful in 3m35s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 7m31s
WAI energy receipts / energy receipts · macos (pull_request) Successful in 7m53s
wai-quantum views in agent hosts / views · the page and its engine (pull_request) Successful in 2m50s
wai-quantum views in agent hosts / views · a scripted host (pull_request) Successful in 3m11s
wai-quantum editors / editors · macos (pull_request) Successful in 1m13s
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 8m59s
WAI energy receipts / energy receipts · linux (pull_request) Successful in 11m6s
wai-quantum for Python / python · macos (pull_request) Successful in 1m57s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 11m22s
wai-quantum studio and desktop / desktop app · macos (pull_request) Successful in 4m20s
wai-quantum docs, course and locales / every command and snippet in the docs · linux (pull_request) Successful in 18m34s
0.2.1 carried `mcp-name: science.transaction.wai/quantum` in an HTML comment. The registry's cargo check reads the README as crates.io renders it (static.crates.io/readmes/...html), and the rendering drops comments, so the token was not there to find. 0.2.2 shows the line as inline code. crates.io keeps code spans as written: 0.2.1's page has <code>science.transaction.wai/quantum</code>, and the registry ends the name at the `<` after it. - README.md (and its translation): the comment goes, and the line is shown as code beside the sentence about server.json. - The registry-manifest test now also holds the README to that line, shown and not commented. - 0.2.2 in Cargo.toml, server.json (both versions), the desktop app's requirement and both lockfiles. The changelog says 0.2.1 went to crates.io only, and the binaries and package managers go from 0.2.0 to 0.2.2. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| capabilities | ||
| icons | ||
| src | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| README.md | ||
| tauri.conf.json | ||
Quantum Studio for the desktop
Quantum Studio as an app. The interface is the browser's. The engine underneath is the quantum job service's engine (wai_quantum::engine), built natively: it uses every core, holds as much memory as the machine has, and works offline.
- Each job runs in a process of its own, this binary run as
worker, so a large job cannot take the app's memory with it, and Cancel ends it. - The worker plans and runs; the app seals. It signs the answer with this user's key, the command line's (
~/.config/wai/quantum-key), which never leaves the app. - Step through and editing by the drawing run natively here: the debugger steps a program and lists its branches off the window's thread, and a drawing's edits, its SVG and LaTeX, and its description in words answer at once.
- Saved jobs, programs and drawings go to
~/Documents/Quantum Studio/.wai-quantum verifychecks a saved job. - The job service is one switch away, as in the browser.
- Your own hardware: the providers you listed with
wai-quantum providers addare under Your hardware. A run asks the provider for its estimate first and shows a dialog before one that is not free; the app reads the credential from the keychain and seals the counts with your key, and the page never sees the credential. - Memory: a job may take
$WAI_QUANTUM_MEMORY_GB(16 by default). The plan says when a job needs more.
What is stable
The app is an application. What it promises is the engine's, through what it saves: a job is the engine's job JSON, which follows its schemas, and its receipt verifies with wai-quantum verify in every later version. What each WAI Quantum version promises, and how a change is announced: the policy; what is deprecated: the deprecations.
Building
The app embeds the Studio's build, so build the Studio first:
(cd ../quantum-studio && npm ci && node build.mjs)
cargo build --locked --release # add --features metal for the GPU state vector on macOS
./target/release/wai-quantum-desktop # the app
./target/release/wai-quantum-desktop check # a job through the worker, sealed and verified, with no window
It draws with the operating system's own web view, so the app carries no browser of its own. Installers for macOS, Windows and Linux come from cargo tauri build.