Semantic search over your runbooks and docs, with indexing changes held for approval
Needle keeps your runbooks, postmortems, and vendor docs in searchable collections. Luumen queries them during an incident and cites the source files, so an answer comes back with something you can open and check. Adding or removing files from a collection is a previewed step you approve. Luumen connects with an API key.
16 tools: 10 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Needle 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 files to a collection, add files to local connector, create collection, create local connector, and more — is shown as a plan and requires approval by default, including the 2 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 Needle — 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.