Incredibuild Unveils Islo: AI Coding Agents Get Persistent Cloud Sandboxes, Ending Laptop Dependency Crisis
Incredibuild's Islo sandbox gives AI coding agents persistent cloud environments, solving lifecycle and security issues from running on developer laptops.
Breaking: Incredibuild Launches Islo - AI Coding Agents Get Dedicated Cloud Sandboxes
Incredibuild, the build acceleration platform behind development tools used by Microsoft, Take-Two, and Nintendo, today announced Islo—a sandbox that gives every AI coding agent its own persistent, isolated cloud environment. The move directly tackles a pressing emergency: developers are being forced to keep their laptops half-open just to prevent AI agents from shutting down, creating security nightmares and workflow chaos.
“Coding agents are capable of doing real work now, but they all run on the developer’s laptop. That means they die when the lid closes, and they have access to everything on the machine,” said Adam Gold, Director of Product Engineering at Incredibuild, in a press release. “We built Islo because we believe that every AI agent needs its own computer—not an ephemeral container, but a long-running dev environment with its own running services, scoped credentials, and a lifecycle that doesn’t depend on human supervision.”
The Crisis: Agents Running Wild on Developer Machines
The current one-developer-one-machine model is fundamentally broken for AI agents. Agents run continuously, not on human schedules—meaning developers are reportedly walking around with laptops half-open so agents keep working. Incredibuild flatly calls this “not a workflow.”
Security risks are equally dire. Agents inherit every credential a developer has accumulated—SSH keys, AWS profiles, browser cookies—with none of the judgment about when to use them. This creates an enormous blast radius if an agent misbehaves or is compromised.
Furthermore, agents need warm, persistent environments with running services, databases, and build caches. Ephemeral containers throw these away on every run, making them unsuitable for sustained AI-driven development.
Background: Why Every Agent Needs Its Own Computer
The industry’s standard cloud dev environments—GitHub Codespaces, Daytona, Coder—were built for humans. They assume an IDE is attached, idle out automatically, and trust the developer’s judgment. AI agents break all those assumptions.
Islo addresses three core failures:
- Lifecycle mismatch: Agents don’t sleep; humans do. Islo environments persist beyond laptop closures.
- Uncontrolled blast radius: Islo scopes credentials per agent, preventing broad access to developer keys and tokens.
- Ephemeral vs. persistent: Islo’s environments maintain running services, caches, and databases across sessions.
“We built Islo because we believe that every AI agent needs its own computer—not an ephemeral container, but a long-running dev environment with its own running services, scoped credentials, and a lifecycle that doesn’t depend on human supervision,” Gold reiterated.
What This Means
For enterprise engineering teams, Islo promises to unlock continuous AI agent operation without the security and governance headaches of running agents on developer laptops. Developers can close their laptops at night without killing agent tasks—a simple but transformative change.
IT departments gain explicit policy governance per agent, ensuring that no agent has access to credentials it doesn’t need. This reduces the risk of credential leakage and simplifies compliance audits.
The announcement signals a paradigm shift: AI coding agents are evolving from human-supervised assistants to independent, autonomous actors that require dedicated infrastructure. Islo positions Incredibuild at the forefront of this transition, offering a purpose-built solution that existing tools cannot match.
Early access to Islo is available now, with general availability expected later this year. Incredibuild plans to integrate with CI/CD pipelines and version control systems, making it a seamless addition to modern developer workflows.