See what your Skyvern agents are doing, and stop the runs that went wrong
Skyvern runs browser agents that click through websites, fill forms, and pull data back. Luumen connects with an API key and reads the whole picture: which agents exist, how they are organized into folders, and what every task and workflow run is doing right now. When a run is stuck or misfiring, Luumen proposes the cancel and waits for your approval before sending it.
10 tools: 5 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Skyvern 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 — cancel runs, create folder, delete folder, start browser task, and more — is shown as a plan and requires approval by default, including the 3 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 Skyvern — 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.