See every running sandbox, then pause, extend, or tear one down
Connect E2b and Luumen can see the sandboxes your team is running: which are live, which are paused, what CPU, memory, and disk each one is using, and what the logs and lifecycle events say. When something needs to change — a stuck sandbox terminated, a timeout extended, a template built — Luumen previews the step and asks before it runs.
27 tools: 15 read, 12 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed E2b run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — connect to sandbox, create template, create webhook, delete sandbox, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to E2b — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.