Read Doppler configs and change logs, then roll back a bad config with approval
Connect Doppler and Luumen can answer questions about your projects without anyone opening the dashboard: which configs exist in an environment, who changed one and when, which webhooks and integrations are wired up. When something needs to change — a rollback, a new branch config, a lock — Luumen shows the plan first and waits for your approval. Authentication is by API key.
61 tools: 32 read, 29 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Doppler 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 — add webhook, rollback config log, clone config, create config, and more — is shown as a plan and requires approval by default, including the 9 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 Doppler — 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.