Read versioned prompts from PromptHub and run a committed project on request
Your prompts live in PromptHub with versions, branches, and model settings attached. Connect it and Luumen can tell you which projects a team owns, what the latest committed prompt and model configuration look like, and what a run actually returns. Execution is an approved step, with the generated text, token usage, cost, and timing reported back.
4 tools: 3 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed PromptHub 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.
This connection exposes write actions such as run project. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 PromptHub — 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.