Release notes

An ax release is identified by its version string. The version is derived from the commit history (<major>.<minor>.<patch>, where the patch number counts first-parent commits from the point the VERSION file landed); docs-only commits keep the version. ax --version reports the version of the executable you are running, and ax update --check reports whether a newer signed release exists.

Entries below describe changes that alter observable behavior in the current line. A draft interface that is not yet runnable is labeled Proposed experience where it appears; everything else listed here runs in the installed build.

Current line

Messaging

• The mailbox is backed by durable v1 records: send, reply, inbox and fetch exchange signed envelopes, a receipt proves durable acceptance, and only a recipient fetch marks pickup. See Agent messaging.
• Session discovery is local. ax agent sessions [HOST] --format json reports sessions on this node; a remote host fails closed with an unavailable error instead of an empty listing. A remote recipient is addressed by mailbox name with ax send HOST/AGENT "TEXT".
• Terminal sender and receiver history is pruned in bounded maintenance passes with a mailbox retention bound, so per-tick forwarding and observation work does not grow with retained terminal records.

Execution

• Exec jobs stay supervised across caller and session loss, with separate connection, wait and execution deadlines. Status and retained output remain available after the client exits. See Tasks and results.
• The native Windows host runs the supervisor as a logon task and serves retained job output through the shared Exec spool. See Windows host.

Deployment

• ax deploy ssh user@host --name host provisions Unix and Windows hosts from the owner machine. A saved runner name that points at another identity is refused before any host configuration is written.
• The provisioning-lock protocol is shared by the deployer and the native Windows removal script, and one fixture pins the names and bounds both sides implement.

Reporting a problem

Include the output of ax --version, the command you ran, and the platform of the host involved. See Security model for reporting a security issue.