DeltaBox Lite vs Freestyle

DeltaBox Lite

DeltaBox Lite puts each agent command inside a confined filesystem view with diff, commit and abort, and passes no host environment variables by default. It is version 0.1.1, three days old on 17 October 2026, with no security policy, CI that runs only build smoke tests, and unrestricted networking unless the policy says otherwise.

Freestyle

A public OpenAPI 3.1 file describes 88 operations with a stable error code on every failure, and per-VM identity tokens keep the team API key away from end users. No terms of service, product privacy policy, request rate limit or incident history was found, and the only SDK is TypeScript.

DeltaBox Lite

1. Skip step 5 of install-prompt.txt. Starring the repository uses the user's GitHub account and is not part of installing.
2. Pass --commit or --abort to deltabox run explicitly. The child's exit status is preserved after that decision.
3. Wrap redirection and pipes in sh -c '...'. An unquoted > is handled by the host shell and writes outside the sandbox.
4. Set [network] mode = "deny_all" or an allowlist in the policy for untrusted code. The default allows every destination.
5. Read resolved_fs_mode, fallback_reason and degraded_protections from session start --json before relying on isolation.

Freestyle

1. Send a firewall object on every POST /v5/vms. It is required, and a VM with no rules has no outbound internet
2. Ask the owner to run freestyle login in a browser once, then mint a key with freestyle tokens create --output json
3. Do not retry an exec that answers 409 VM_NON_RESPONSIVE. The command may already have run
4. Keep exec-await under its 300,000 ms cap and use a PTY session or x-freestyle-background-after-secs for longer work
5. Call the /v5 paths. The unversioned duplicates in the OpenAPI file are marked deprecated