Read bots, CMS entities, and attributes in BotStar, then change them with approval
Connect BotStar and Luumen can read your bots, their CMS entities and items, and every bot attribute without leaving the terminal. When something needs to change — a new entity item, an updated attribute, a publish to live — Luumen shows the exact call first and waits for your approval by default. Authentication is by API key.
31 tools: 16 read, 15 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Botstar 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 — create bot, create bot attribute, create cms entity, create entity fields, 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 Botstar — 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.