Linkhut
for LuumenAI
Keep the team's runbook and reference links current from the terminal
Operations teams collect links: runbooks, vendor status pages, postmortems, internal wikis. Connect Linkhut and Luumen can read your bookmarks and tags for context during an incident, then add or correct entries as approved steps. Authentication is handled over OAuth2, so the agent acts as your Linkhut account.
The Linkhut toolbox
5 tools: 2 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet all tagsRetrieves a list of all tags and their usage counts for the authenticated user.
- ReadGet bookmarksRetrieves bookmarks from the user's Linkhut account with optional filtering.
- WriteAdd bookmarkAdds a new bookmark to LinkHut. Approval by default
- WriteDelete bookmarkThis tool allows users to delete a bookmark from their Linkhut account by providing the bookmark URL. Approval by default
- WriteUpdate BookmarkThis tool allows users to update an existing bookmark in LinkHut. Approval by default
One prompt, start to finish
What a governed Linkhut run looks like inside Luumen.
Questions
Authorize once with OAuth 2.0. 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 bookmark, delete bookmark, update bookmark — is shown as a plan and requires approval by default, including the 1 action 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 Linkhut — 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.
Put Linkhut to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.