lexicon-tui

Terminal client for Lexicon — a personal knowledge base. Read topics and posts as rendered markdown, manage a shared todo list, and write posts or journal entries without leaving the terminal. Layout inspired by OpenCode: content in the center, context + todos in a right rail, a command bar at the bottom.

Install

npm install -g lexicon-tui

or run it without installing:

npx lexicon-tui --server https://your-lexicon-instance.com

Usage

lexicon-tui [--server <url>]

The server URL and tokens persist in ~/.lexicon/config.json, so flags are only needed once.

Keys

| Key | Action | | --- | --- | | j / k, arrows | move / scroll | | Enter | open the selected item | | / | search everything | | : | command mode (:open, :journal, :new post, :todo <text>, :server <url>, :token <value>, :quit) | | Ctrl+P | command palette | | Tab | cycle focus: content → todo rail → command bar | | Esc | back / cancel |

In the todo rail: space toggles, a adds, d deletes. Reading a post: e edits. Reading a journal note: a appends an entry.

Composing

The composer mirrors the Lexicon website: your note builds up as rendered markdown on top, you type in the box pinned at the bottom, and Ctrl+Enter sends the draft up into the note (posts flow into one document; journal chunks become separate entries). Ctrl+S saves, including anything still in the draft box.

Auth

Reading is public. Writing needs a token from your Lexicon instance:

• :token <value> — a 24h edit token (journal + todos), requested and approved via the website's /edit-access flow.
• :token admin <value> — the instance's ADMIN_API_TOKEN (publishing posts; also grants edit access, so it's the only token an admin needs).

Requirements

Node 20+, and a running Lexicon instance to point at (defaults to http://localhost:3002 for local development).

License

MIT