Hjarni
for LuumenAI
Search, link, and maintain your Hjarni notes from the terminal
Connect Hjarni and your notes become working context. Luumen reads containers, tags, trashed items, and full Markdown bodies on request, so you can find the runbook you half-remember without leaving the terminal. Changes — new notes, retags, moves, restores — are previewed and approved before they land. Luumen connects with an API key.
The Hjarni toolbox
15 tools: 6 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Account StatusReturn the connected Hjarni identity, token scope, plan, teams, and current resource usage and quotas.
- ReadGet NoteGet one Hjarni note by ID with its Markdown body, tags, container, attachments, links, and optimistic-lock version.
- ReadList ContainersList Hjarni containers as active roots, archived roots, or all active containers in a flat view.
- ReadList NotesList and filter personal Hjarni notes, including active, inbox, archived, or favorited notes.
- ReadList TagsList all Hjarni tags and their note counts.
- ReadList Trashed NotesList recoverable trashed Hjarni notes with their deletion and scheduled purge times.
- WriteCreate ContainerCreate a root or nested Hjarni container for organizing notes. Approval by default
- WriteCreate NoteCreate a Markdown note in the inbox or a container. Approval by default
- WriteCreate NotesCreate 1-25 Markdown notes in order and return one result per input. Approval by default
- WriteCreate TagCreate a Hjarni tag for organizing notes. Approval by default
- WriteRename TagRename an existing Hjarni tag without changing its note associations. Approval by default
- WriteRestore NoteRestore a note from Trash before its scheduled purge and return the active note. Approval by default
- WriteMove Note to TrashMove a note to recoverable Trash. Approval by default
- WriteUpdate ContainerUpdate a Hjarni container's name, description, parent, position, or container-specific AI instructions. Approval by default
- WriteUpdate NoteUpdate note metadata, placement, tags, or body. Approval by default
One prompt, start to finish
What a governed Hjarni run looks like inside Luumen.
Questions
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 container, create note, create notes, create tag, and more — 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 Hjarni — 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.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Hjarni to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.