Read Hex projects, runs, and sharing — change access as an approved step
Connect Hex and Luumen can read your workspace the way an analyst would: which projects exist, who is in which group, what a scheduled run did last night, and which cells make up a draft. When something needs to change — sharing a project with a group, creating a collection, canceling a stuck run — Luumen shows the change first and waits for your approval. Auth is by API key.
32 tools: 13 read, 19 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Hex 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 run, create cell, create collection, create group, and more — is shown as a plan and requires approval by default, including the 4 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 Hex — 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.