Read, sort, and file your Readwise Reader library from the terminal
Your Reader library becomes something you can query and tidy from the terminal. Luumen lists documents, filters by location or tag, and reads the tag list for context. Saving a link, retagging a batch of articles, or moving something to the archive is a previewed step you approve first. Connects with an API key.
6 tools: 2 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Readwise Reader 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.
This connection exposes write actions such as bulk update documents, delete document, save document, update document. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Readwise Reader — 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.