Aient CLI v0.11.28

Aient CLI 0.11.28 — recover interrupted workspace transfers

Workspace synchronization automatically retries supported transient network failures and incomplete responses while keeping the originally captured source bytes. Each attempt obtains fresh authorization for the same target, operation and immutable content.

Candidate uploads replay the captured artifact. Numbered Git-cache uploads replay only the affected part, so one lost response does not restart the whole pack. Retries are bounded; cancellation and authorization failures remain terminal. Partially streamed downloads and generic mutations are not automatically replayed after an ambiguous failure.

An established IPv6 route failure gives that host a temporary IPv4 preference while preserving ordinary dual-stack fallback. Normal requests add no extra authorization call or wait.

Use the existing sandbox sync and workspace-backed sandbox run or exec commands; no new flag is required. Selected-file Agent sync and experimental --live behavior retain their existing limits.

Aient CLI v0.11.27

Aient CLI 0.11.27 — selected-file sync into an Agent checkout

Send explicitly selected local files to an Agent's current primary checkout on a compatible runtime:

aient --profile "$PROFILE" agent worktree sync THREAD /absolute/local/repository \
  --repository OWNER/REPO --path apps/frontend/src/App.tsx --json

Repeat --path for up to 128 existing regular files, each at most 64 KiB. Each confirmed write atomically replaces an existing remote file and preserves its mode. The Agent keeps the same runtime, incarnation and lease. Native runtimes and a repository other than the current primary checkout are rejected.

JSON reports confirmed writes separately from the cooperative path-change notice asking the Agent to reread. Confirmation requires the exact path, byte count, SHA-256 acknowledgement and successful command completion. Failed or ambiguous writes send no success notice; earlier confirmed writes remain applied. If only notification fails, retry its returned exact text and operation ID with agent message --immediate, without repeating the writes.

Whole-file updates use last completed write wins; the model's existing line-hash edit checks still apply. This release adds a one-shot selected-file batch, without continuous Agent watching, a multi-file transaction, or a guarantee that the running application reloads. See the Agent checkout sync guide for source selection and limits.

Aient CLI v0.11.26

Aient CLI 0.11.26

Opt into selected-file live updates for a compatible running sandbox with --live --live-transport exec. Start the watcher before the application, and select existing files with --live-path. This experimental transport supports up to 64 KiB per captured write and preserves the remote file mode. Exact acknowledgements and successful command completion confirm delivery; an unconfirmed write stops the watcher and requires reconciliation. See the live-sync guide for setup and limits.

Workspace synchronization now finishes correctly for archives with trailing tar padding. Shell programs use Bash by default; exact command arguments remain literal.

This release uses the protected v1.0.2 provenance builder. The installation guide selects its verification identity for 0.11.26 and later while retaining the existing identity for earlier releases.

Aient CLI v0.11.24

Aient CLI 0.11.24

Clearer sandbox creation failures

A confirmed sandbox creation rejection no longer reports an unknown outcome or
asks you to reconcile a sandbox that was never created. Uncertain outcomes
retain their existing recovery guidance. This change adds no retries.

Aient CLI v0.11.23

Aient CLI 0.11.23

Experimental selected-file live sync

sandbox sync --live-stream --remote-dir PATH --live-path FILE uploads explicitly
selected existing local regular files into an already running, attested native V3
sandbox, then watches ordinary atomic saves over one authenticated shell stream.
Repeat --live-path for up to 128 files, at most 32 MiB each. Initial publication
overwrites the selected files; each later file is replaced atomically and its
exact byte count and SHA-256 are acknowledged. The separate experimental --live
mode uses the files upload API instead.

The stream holds a shared workspace fence, blocking full sync and exclusive file
uploads until verified shutdown. Ctrl-C requests STOP; missing acknowledgement or
terminal completion prints termination UNVERIFIED. The helper and fence may
remain active and continue blocking those writes. Starting another watcher does
not recover an unverified session.

These modes do not synchronize Git metadata, protect concurrent edits, propagate
deletions/renames/new unselected files/mode changes, or provide multi-file
consistency or reconnect recovery. Delivery does not prove application readiness
or browser HMR, and there is no universal subsecond latency guarantee. Existing
sandbox lifetime limits still apply.

Aient CLI v0.11.22

Aient CLI 0.11.22

Reuse Git history when syncing an existing sandbox

sandbox sync and sandbox exec --workspace reuse the shared Git cache on eligible native V3 workspaces. Interrupted preparation keeps its original captured files and operation; rerunning the command can continue that transfer even after you make further local edits. Commands start only after workspace activation succeeds.

Workspace recovery, lease refresh and cleanup now remain bound to the original allocation and workspace identity. A replacement sandbox with the same name is rejected before mutation. New retained Git-cache operations save this original authority. Older retained Git-cache captures without the allocation UUID remain readable, but mutating resume is rejected and their saved bytes are preserved.

Aient CLI v0.11.21

Aient CLI 0.11.21

Create native sandboxes with Billing admission

Upgrade to this release to create native customer sandboxes or claim a ready
repository sandbox with the current Aient service. The CLI binds each request
to its exact allocation identity before Billing admission. A transport retry
reuses that identity and its existing admission rather than allocating another
sandbox or reserving another hold. Older clients cannot start a new native
allocation through this admission contract.

New native sessions cost €0.15/hour for small, €0.60/hour for medium, and
€1.20/hour for large. Billing measures actual occupancy in whole seconds and
rounds the final session amount once to the nearest cent. The initial €5
reservation counts against spending limits; it is not a session cap. Sessions
continue while the user and organisation limits allow, within their finite
lease. Historical sessions keep their existing terms.

A Billing denial stops before allocation and reports that no sandbox was
created. An ambiguous create retains the exact sandbox name and recovery
command so it can be reconciled safely.

Aient CLI v0.11.20

Aient CLI 0.11.20

Clearer sandbox creation recovery

Sandbox creation keeps the requested name when recovering from a confirmed
capacity rejection. If the outcome is uncertain, the CLI prints the allocation
ID and exact recovery command so you can check it without creating another
allocation. Confirmed creation denials no longer suggest reconciling a sandbox
that was never created.

Read updated MCP connection status

MCP connection reads accept the server's versioned, credential-free OAuth
configuration summary while continuing to accept legacy profile status. This
release does not add a new provider-setup command.

Aient CLI v0.11.19

Aient CLI 0.11.19

Maintenance release with no new public commands.

Aient CLI v0.11.18

Aient CLI 0.11.18

Run commands in an Agent-owned sandbox

From aient agent chat THREAD, a ! COMMAND can use the Agent's existing
sandbox without creating a second sandbox or transferring its ownership.
The CLI authorizes the exact server-selected workspace and sandbox incarnation
before starting the command. Reconnect to a detached command with
aient agent execution attach EXECUTION; the same execution ID also works
with status, wait, and cancel.

An ambiguous Start response does not dispatch the command again. Native Agent
sandboxes keep their existing execution behavior. This release does not change
the separate aient sandbox run allocation and workspace-sync flow.