V0.10.1 BETA · APACHE-2.0

The systems language built for coding agents, and readable by humans.

Readable source. Queryable meaning. Checked changes.

Install v0.10.1 without a source checkout, create a checked project and explore the same program through readable source and compiler-derived meaning. This beta consolidates language and host profiles, repairs cross-platform source-history authentication and keeps ownership, diagnostics and refusal controls intact. Five native archives support the first-project workflow without a model account.

Explore the v0.10.1 release See what is proven Read the live English handbook

semaprax://v0.10.1beta

revision  sha256:<program-state>
query     app.main --depth 1
context   typed · bounded · stable-id
patch     expected_revision == current
verify    fail_closed
target    native | browser/wasm

What is Semaprax?

Semaprax is an open-source, agent-native systems programming language in beta. Readable .spx source stays in Git while coding agents query compiler-checked meaning and propose revision-bound changes. The published 0.10.1 toolchain combines contracts, ownership, typed runtime Agents and explicitly admitted interpreter, native and WebAssembly profiles.

// v0.10.1

What changed in v0.10.1

What is shipped and reviewed in this beta, with source-only additions and historical measurements kept separate.

A qualified release, with exact inputs

All 97 jobs passed for the published commit. Native archive, installer, signing and installed-journey checks bind the download set to that source revision.

Evidence

Cross-platform source-history repairs

Windows and Unix path handling, complete predecessor authentication and canonical identity backing retain original hostile-input and history controls. No semantic limits were raised to pass CI.

Evidence

One install path for five hosts

Pinned shell and PowerShell installers select one native archive, verify integrity and report publisher verification separately. The generated calculator checks, tests and prints 42.

Evidence

Owned-record scalar updates, narrowly scoped

The source batch adds vec_update_field<Row> for selected Copy scalar fields of flat owned-leaf records. Its specification still marks owning qualification pending; it is not general mutable-record or efficiency support.

Evidence

A private Claude repair adapter

Native Claude repair V3 has local parser, process and checked-feedback fixtures. It requires an explicitly trusted CLI host and does not establish live-provider execution or an OS sandbox.

Evidence

Reuse checked HIR with authentication

The opt-in persistent cache authenticates private entries and current source before reusing checked HIR. Stale entries fail closed; this is not portable cache trust or general incremental compilation.

Evidence

Keep tools inside their authority

Typed model proposals, selected source laws, revision-bound edits and host-supplied capabilities retain separate authorization and replay boundaries.

Evidence

Keep performance evidence honest

Earlier paid trials, compact-context regressions and LAW16 adverse outcomes stay visible. Newly authored allocation and compiler-work reductions are not measured application speedups.

Evidence

// v0.10.1

Choose your v0.10.1 archive

Five full-toolchain archives: GNU/Linux x86-64 and arm64 (glibc 2.35+), Apple Silicon macOS 11+, Intel macOS 10.12+, and Windows x64 10 1809+ / Server 2019+. musl/Alpine and Windows ARM have no archive. Each includes semaprax and semapraxd. The published manifest is authoritative; the tagged handbook’s older download table is historical.

macOS · Apple Silicon · 11+

aarch64-apple-darwin

Download archive

Linux · arm64 · glibc 2.35+

aarch64-unknown-linux-gnu

Download archive

macOS · Intel · 10.12+

x86_64-apple-darwin

Download archive

Windows · x64 · 10 1809+ / Server 2019+

x86_64-pc-windows-msvc

Download archive

Linux · x86-64 · glibc 2.35+

x86_64-unknown-linux-gnu

Download archive

Download your platform archive and select its exact line in SHA256SUMS. GitHub Source code downloads are repository snapshots, not runnable programs.
For publisher verification use gh attestation verify with the matching release-attestation-<target>.json, repository wavect/semaprax and exact tag. A checksum alone is not a signature.
Extract to a permanent directory and add it to PATH, then run the first-project commands below. For receipt-managed upgrade, downgrade or uninstall, use the installer contract; do not mix package-manager ownership.
For v0.10.1 use the pinned installers or archives above. brew install wavect/tap/semaprax still selects the separately reviewed v0.9.0 formula on Apple Silicon and Intel macOS. WinGet submission #447495 remains open as of 8 November; no v0.10.1 package-manager publication is claimed. Tagged handbook examples also still say v0.9.0. Source builds should check out d3fa1dab70a5e900e6b0c8e69c17ae3a0f51c4cd and use Git and Rust/Cargo 1.88+; standalone semaprax and semaprax-toolchain install different command surfaces.

SHA256SUMS · Checksums and signed provenance · Release manifest · Release record

Install the full toolchain: macOS and GNU/Linux

Pinned v0.10.1 per-user installer. No Rust, Cargo, checkout or model account is required. It selects one archive, checks its checksum and manifest, smoke-tests it and records activation in a receipt. With GitHub CLI available it also verifies the publisher attestation; without it the receipt explicitly says checksum-only. Add --require-publisher-verification to refuse that fallback. Open a new terminal after installation.

curl -fsSL https://github.com/wavect/semaprax/releases/download/v0.10.1/install.sh | sh -s -- --version v0.10.1

Installer options, verification and uninstall

Windows PowerShell, then your first project

On Windows use the pinned command below with PowerShell 5.1 or 7, then open a new terminal. On macOS/Linux continue with the semaprax commands after the shell installer. Pick a destination that does not exist. The bundled calculator includes source, manifest, tests and AGENTS.md; its final run prints 42. Clang is needed only when you select native compilation.

powershell -ExecutionPolicy Bypass -c "& ([scriptblock]::Create((irm https://github.com/wavect/semaprax/releases/download/v0.10.1/install.ps1))) -Version v0.10.1"

semaprax --version
semaprax new first-semaprax
semaprax check first-semaprax/semaprax.toml
semaprax test first-semaprax/semaprax.toml
semaprax run first-semaprax/semaprax.toml

Give your coding agent a precise starting point

Inside the generated first-semaprax directory, start with its AGENTS.md and a focused language topic. Read small source files directly; use bounded semantic context for a precise question and inspect truncation. The full graph can be much larger than the source. The optional development harness and a source-defined runtime Agent are different surfaces.

cd first-semaprax
semaprax help language lists
semaprax query --capabilities
semaprax check .
semaprax test .
semaprax help diagnostic SPX-T208

One program, three connected surfaces

People edit readable source, tools query checked meaning, and supported targets execute the admitted program. Each target and integration states which language features it accepts.

Readable sourceCanonical .spx files, stable declaration IDs, contracts, laws and explicit ownership. Ordinary check and run commands need no model account.
Checked meaning for toolsCompiler-derived context, impact, candidate review and proof obligations. The harness can add selected retrieval, skills and model providers around that semantic core.
Controlled executionInterpreter, admitted C11/Clang and Core Wasm profiles, plus typed runtime Agents whose model proposals pass deterministic authorization before effects.

Semaprax semantic program graph: Semaprax checks readable .spx source and resolves it into HIR, its typed compiler representation. Source and semantic identities bind queries, law obligations, candidate changes and execution to the program that was inspected. Coding agents can use the harness around this core; runtime Agents separately decode proposals, authorize effects and reduce state under explicitly supplied host capabilities.

Make every proposed change easier to check

Stable identities let an agent target a declaration. Bounded context explains its role. Contracts and separately selected laws constrain the implementation, while candidate review and replay check the change before application. The harness records actual usage and task outcomes so efficiency claims can be tested against evidence.

MEASURE THE OUTCOME Less repair ambiguity, with task cost and correctness checked separately

Follow the question you need to answer

Use the handbook for practical steps, architecture for the programming model, evidence for implemented profiles, benchmarks for measurements and interoperability for the boundary with your existing stack.

Architecture

Source laws, semantic graphs, Agents and harness

Evidence

What v0.10.1 implements and where it stops

Benchmarks

Measured tokens, task cost and performance

Interoperability

Target and ecosystem evidence matrix

Roadmap

Milestones, objectives, and open gaps

// STATUS

Repository status at the audited snapshot

Repository snapshot	`d3fa1da` · 2026-11-08. The v0.10.1 tag resolves to the pinned source commit. Its exact-tag CI completed successfully. This does not establish blanket production or security assurance.
Full product status	55 Partial · 0 Implemented · 0 Missing
Graph and project contract	Canonical source, stable IDs and checked compiler representations connect laws, semantic queries, edits and execution. Feature-selected graph and Project schemas preserve their own admission, compatibility and host-authority contracts.
Published beta release	`v0.10.1` · Published 8 November 2026 at 13:43 UTC. All 97 jobs in the exact-tag release workflow passed, including six native installer journeys across five targets. Five archives and two installers ship with SHA256SUMS, five archive attestations and independently verified signed aggregate provenance. This is beta qualification, not notarization, reproducible-build assurance or a current revocation check. Exact-tag CI.
Package and API previews	The release includes useful language, law, harness and host-integration profiles. Generated Rust/npm packages, public generic ABIs and broader platform support retain separate publication and support decisions.

Capability evidence ledger

Current status	Evidence state	Scope	Evidence
Canonical source and stable identity	Partial	Readable `.spx` remains the canonical Git representation. Explicit `@id` values identify declarations independently of supported display-name changes. The revision binds canonical source and the compiler-owned implicit prelude, not incidental source spans or a graph wire format.	GitHub repository
Bounded context and compact projections	Partial	Select exact graph or task context with depth, direction, node and byte bounds. Model-text v2 reduces tokens on selected large inputs and grows on small ones; reports preserve the tokenizer and comparison boundary.	GitHub repository
Semantic edits, not arbitrary rewrites	Partial	Inspect context, derive a candidate, preview impact, review, replay checks, then explicitly authorize application. The operation families now extend beyond renames to bounded expression replacement, structural changes and specified rebase/merge composition. Each protocol keeps its own revision, identity and operation limits.	GitHub repository
Managed publication is a separate boundary	Partial	Managed workspace generations, candidate evidence, Project revision storage and MCP workflows retain explicit write and publication authority. Validation of multiple files is not an atomic update to arbitrary raw paths, Git or editors. The Rust embedding API supplies capped inputs, cancellation and opaque sessions, not unrestricted host access.	GitHub repository
Replayable semantic evidence	Partial	Evidence binds checked facts and candidate changes to source and revisions. A receipt can support review or rejection; it does not grant execution, mutation or publication authority.	GitHub repository
Multi-module projects and offline scaffolding	Partial	Manifests define declared source, entries, tests and exports. Bundled calculator, library and service templates have their own profiles. new creates a fresh project from compiled-in files; source checking, interpreted tests and target builds follow the selected manifest contract.	GitHub repository

// DOCS

Open the Semaprax handbook

The online handbook is the English guide published from main and may cover changes after 0.10.1. Use the pinned snapshot when reproducing this release.

Live handbook

The current English learning path, published from main.

0.10.1 handbook snapshot

The handbook files at the exact reviewed release commit.

Build your first project

Current English guide to the calculator manifest, checks, tests and builds.

Learn the language essentials

Current English introduction to values, functions and source structure.

Work with a coding agent

Current English guide to semantic context and safe change workflows.

CLI reference for 0.10.1

Pinned command forms and the standalone/full-toolchain boundary.

VS Code extension

Pinned setup, semantic navigation, review and development controls.

Runnable examples

Pinned examples for the language, projects, laws, Agents and host integrations.

// REF

Primary sources for this page

Reviewed on 8 November 2026 against the published v0.10.1 commit, asset manifest and successful release workflow. The tagged handbook and channel registry still contain v0.9.0 examples; use the pinned v0.10.1 commands here. Historical benchmark results keep their original scope. The live handbook follows main and may describe later work.

// FAQ

Questions and practical answers

Is Semaprax production-ready?

Version 0.10.1 is an Apache-2.0 beta published on 8 November 2026 after all 97 release-workflow jobs passed. Five host archives and two installers are available. The full-goal matrix remains 55 Partial requirements; release qualification does not establish production or safety-critical readiness.

Is Semaprax only for AI agents?

You can write, check and run ordinary .spx programs without an AI model or account. Coding agents use semantic context and supported changes through the tooling; source-defined runtime Agents are a separate typed programming abstraction. The English handbook walks through both.

Need this level of evidence-first engineering in your AI product?

See Wavect’s AI engineering work.

Created by Wavect as an open-source systems research project. GitHub repository. Reviewed on 8 November 2026 against the published v0.10.1 commit, asset manifest and successful release workflow. The tagged handbook and channel registry still contain v0.9.0 examples; use the pinned v0.10.1 commands here. Historical benchmark results keep their original scope. The live handbook follows main and may describe later work.