hn.today

Is 'fork' missing operation in sandboxes?

avrea.com3 points2 comments
Screenshot of Is 'fork' missing operation in sandboxes?

Avrea Sandboxes are presented as full virtual machines for developers and AI agents, rather than narrowly task-focused command runners. They offer hardware-assisted isolation, non-oversubscribed CPUs, Apple M5 Max for Linux ARM64 and AMD Zen 5 EPYC for Linux AMD64 and Windows. The argument is that useful speed means reaching productive work quickly, not merely booting fast: datacenter-local Git mirrors, nearby package caches for common ecosystems, and CI build caches reduce repeated downloads and builds. Cited benchmarks show strong performance on selected CI workloads, including M5 Max leading tested ARM runner configurations and an x86 build completing faster than on GitHub-hosted runners; results depend on workload and cache state.

The central feature is making computers forkable, like source-code branches. After preparing or debugging an environment, users can pause and copy its disk and machine configuration, then try separate approaches without disturbing the original. This supports parallel agent tasks as well as human review. Forking currently requires a supported paused VM, with pause/resume and forking available on Linux AMD64; it copies disk contents, not running process memory or external effects, so credentials and access still require care. Sandboxes are billed by the second, include networking without separate bandwidth charges, and can be paused, resumed, or deleted under configurable limits and retention rules. Public HTTPS endpoints provide managed TLS for services running inside a VM, making temporary development servers and previews easier to share.

Read on avrea.com2 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Hardware

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.