assura

Changelog

Release evidence, not just release notes.

Assura is pre-1.0. Version v0.4.1 is the latest published release, live-verified on 2026-10-01 from source commit 7ab1d82 by release workflow run 36799421108.

Start with your agent Open GitHub releases

Authored summary; not raw CLI output.

release status 
latest release     v0.4.1 (2026-10-01)source commit      7ab1d82release workflow   36799421108status            pre-1.0 betaplatforms         Linux, macOS, Windowsevidence          release-live + performance

Published v0.4.1

Review, Explain, onboarding, bounded event feedback, managed host activation, deterministic content checks, and local context surfaces are available in the latest release.

Previous releases

Earlier published versions and their release notes remain available in the GitHub release archive.

Roadmap boundary

Automatic broad repair, hosted orchestration, semantic inference as policy, and public third-party plugin APIs are not part of the supported core contract.

01

0.4.1 release

Published on 2026-10-01 from source commit 7ab1d82; the release workflow verified all five platform archives and checksums.

02

Compatibility policy

Before 1.0, Assura favors direct replacement of superseded internal contracts over long-lived compatibility shims.

03

Installation evidence

Release readiness verifies public install scripts and platform assets before a version is presented as current.

04

Performance evidence

Checked cold and warm reports retain their environment, fixture cohort, and version instead of carrying numbers forward manually.

Continue

Follow the signal into the details.

Agent setup

Set up this project with Assura.

Copy one instruction to the coding agent already working in your project. It will establish the baseline, define the expected shape, and verify it.

Agent goal Inspect, constrain, verify
Published v0.4.1. The installer provides the published release. This source checkout may contain newer changes. Keep assura and assura-full together, confirm the selected version, and follow any installer PATH correction.
First command assura agent onboard .
  1. Inspect manifests, tooling, generated output, and the intentional layout.
  2. Define project-owned rules for the expected stack. Close stable scopes so unexpected paths fail; preserve legitimate paths and ask only where evidence is ambiguous.
  3. Verify with assura review and assura check --format agent.
Installation details published release pair
curl -fsSL https://assura.dev/install.sh | sh

The copied setup instruction includes this command and the mandatory checks below.

assura --version && assura-full --version