Skip to main content

​
Executions, output, and files

sandbox exec creates one supervised execution and prints its ID before dispatch. The sandbox execution commands address that exact (sandbox, execution) pair without starting another command.

​
Output is live-only

Aient CLI 0.7.0 does not retain command stdout or stderr for replay. attach receives only new live bytes after attachment. status, wait, and cancel return content-free execution state. An authorised child receives its process capabilities and can deliberately print a mounted environment or GitHub secret. The CLI returns stdout and stderr verbatim to the connected caller, whose terminal or agent runner may record it. Avoid env, printenv, shell tracing, and echoing GH_TOKEN; credentials are not ordinary execution metadata or replayable output. If an attached connection is interrupted, use the printed execution ID to query status first. Do not rerun an arbitrary command to discover whether it started.

​
aient sandbox execution status

Copy the execution UUID printed by sandbox exec into a shell variable:
Then read the current content-free state, repeating the original authority selectors:

​
aient sandbox execution attach

Attach to future live output from a known execution:
This is execution attachment, not command detachment. It cannot replay bytes emitted before attachment. Use one active attachment per execution.

​
aient sandbox execution wait

Wait for the terminal outcome without receiving output:
Add --json for structured state. A terminal result can report a known exit code, cancellation, or an unknown outcome; the CLI does not guess by replaying the command.

​
aient sandbox execution cancel

Explicitly cancel the exact execution:
Cancellation does not delete the sandbox.

​
Environment and repository selectors

All four execution-observation commands accept: Use the same selectors as the original environment-capable sandbox exec.

​
Explicit file commands

File commands address an existing sandbox without an environment binding and an explicit path. They are separate from exact Git workspace synchronisation. In 0.7.0, they cannot carry the selectors required to address an environment-bound customer sandbox.

​
aient sandbox files put

Upload one file or directory into an absolute remote directory:
Directory excludes support /-separated *, **, and ? globs. The CLI rejects upload of the active access-token file, including hard links to that file.

​
aient sandbox files get

Download one explicit remote file:
Directory download is not part of this command.

​
aient sandbox files ls

List an absolute remote directory:
Without a directory argument, the CLI lists /.

​
aient sandbox files rm

Remove one explicit remote path:
files rm changes the remote filesystem immediately. Verify the sandbox and absolute path before running it.

​
Workspace mutation fencing

Workspace reads and commands participate in a shared fence; sync activation and direct workspace mutation require the exclusive form. A file command against a busy workspace currently fails closed rather than waiting. If you see a workspace-busy response:
  1. Do not loop concurrent mutations.
  2. Check or wait for the known execution using its ID.
  3. Retry the file operation only after the reader or mutation has finished.
Never interpret partial transfer progress as a completed file installation.