Read v0 chats, projects, and deployment logs, then ship a version with approval
Connect v0 and Luumen can see the work in flight: which chats exist, which project they belong to, what a given version contains, and why a deployment failed. Reads come back right away. Changes like deploying a chat version, creating a project, or setting environment variables are previewed and approved first.
44 tools: 24 read, 20 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed V0 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 — assign chat to project, v0 chat completions, create webhook, create v0 project, and more — is shown as a plan and requires approval by default, including the 5 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 V0 — 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.