Skip to content
Radient

Short-lived execution contract

Beta · Request access

Not yet available.

Run a pinned revision, not an uploaded workspace.

Remote Compute is in beta and is not yet available. Review the short-lived lop exec --remote contract, its repository and full-SHA inputs, budget, deadline, status and cancellation. Request access for your account.

Used with Local Operator

Local Operator’s lop exec command defines the client contract: repository and immutable revision in, run id and status out. Preview access is limited to approved accounts; contact us about your use case.

Read the lop exec contract (opens in a new tab)Request access

Availability

Not yet available

Beta; request access for your account

Source

Repository + full SHA

Branches and short hashes are refused

Local files

Not uploaded

The far end checks out the repository

Controls

Budget · deadline · cancel

Short-lived runs, not persistent workloads

The command is the run specification

This contract is deliberately narrower than a cloud workspace. It names the source revision, execution bounds and inspection commands without promising a persistent machine.

Current client contract / preview

Short-lived run; no working-directory upload
lop exec --remote \  --repo https://github.com/example/repo.git \  --sha <40-hex> --network home \  --max-hours 2 --budget-usd 3 \  'Run the acceptance checks'​lop exec --remote-status RUN_IDlop exec --remote-cancel RUN_ID

The budget is an example run cap, not a pricing quote. Remote Compute is in beta and is not yet available; request access for your account.

Run contract

Source
Repository URL + full 40-character commit SHA
Checkout
The far end clones; local uncommitted files are not uploaded
Deadline
--max-hours bounds execution; the server may cap it
Budget
--budget-usd caps this run; admission defaults may apply
Observe
--remote-status prints one run as JSON
Stop
--remote-cancel is idempotent and not a persistent-workload API

Mechanism

How it works

  1. 01

    Pin the source

    Provide a git repository URL and the full 40-character commit SHA. The far end checks out that revision; your working directory is not uploaded.

  2. 02

    Bound the run

    Set or accept the server’s admission budget and deadline. A run can stop when either bound is reached, so the receipt and final status matter.

  3. 03

    Submit a short-lived task

    The current client contract supports a prompt, an optional compute size and network binding where required. Local-only flags are refused rather than ignored.

  4. 04

    Inspect or cancel by run id

    Use the remote-status command to read the run as JSON and remote-cancel to request cancellation. A watch ending is not proof that the run completed.

Contract scenario

Run acceptance checks against a reviewed commit

A reviewer has approved a full commit SHA and wants an isolated acceptance run. The command points at the repository, pins that SHA, caps spend and sets a deadline. The resulting run id is the handle for later status and cancellation rather than an implied long-lived development environment.

The input is reproducible and the execution bounds are explicit. Uncommitted local edits are outside the run by construction.

Before you rely on it

Requirements, limits, security and cost

Current state

  • Beta; not yet available
  • Request access for your account
  • The client contract is preview and account-allowlisted

Input limits

  • A repository URL and full commit SHA are required
  • No working-directory upload
  • Local-only execution flags are refused beside --remote

Execution limits

  • Short-lived runs with budget and deadline bounds
  • No persistent-workload promise
  • No included monthly hours or Team-plan compute benefit

Cost

  • A budget caps a submitted run; the server admission default can apply when omitted
  • No public Remote Compute price is quoted here
  • Contact us to discuss your workload and budget

Feature questions

The details that change the decision