DeltaBox Lite vs Offscreen

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.

Offscreen

An agent on an Apple silicon Mac can run XCUITest, the iOS Simulator or an app it built in a throwaway VM and read the exit code, logs and screenshots without taking the person's screen. The project is six days old at v0.0.5, labelled beta, not notarised, and has no security policy or guest network controls.

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.

Offscreen

1. Read .offscreen.toml before running anything and use its project key and task names. Don't guess them
2. Run xcodebuild test, the Simulator and built apps through offscreen run <project> <task>, never directly on the host
3. Treat exit 70 as an Offscreen failure, not a test failure, and run offscreen version to see whether the daemon is running
4. Ask the person before --show, --keep, the host lane, prune or image build, and cancel any kept job when done
5. Read screenshots and .xcresult bundles from the directory offscreen artifacts <job> prints