Local Files

Liddr indexes text files from a directory on the server's own filesystem — no upload and no external account. It walks the folder you point it at, extracts the text from each supported file, and makes it searchable in Know and available to ground Forge. It only ever reads the files; nothing is written back or sent off the server. Because it needs filesystem access, it's a SELF-HOSTED-only connector: it's shown on Liddr's managed cloud but can only be activated on a self-hosted install (set LIDDR_SELF_HOSTED=true).

What Liddr accesses

Direction	Access
Ingest (read into your knowledge graph)	Read-only
Reverse sync	None — Liddr never writes to this source

Setup

1. In Settings → Connections, add the Local Files connector.
2. Set Root directory to the absolute path of the folder on the server you want indexed (e.g. /path/to/documents).
3. Run Test to confirm the path is readable and see the supported-file count, then trigger an Ingest.
4. Re-run Ingest after the files change — edits are re-indexed and removed files are archived.

Required scopes

Filesystem access

Ingest — minimum

• The Liddr server process needs read access to the configured directory and its subfolders
• Text types indexed: .txt .md .rst .log .csv .json .xml .html .yaml .toml .ini .cfg, plus .pdf, .docx and .rtf
• Files over 20 MB, and binaries that aren't valid UTF-8 text, are skipped

TIP

There is no token or external account — access is simply the OS read permission of the account Liddr runs as. It is strictly read-only: Liddr never modifies, moves, or deletes your files. Self-hosted only: on managed cloud the connector is visible but not activatable; a self-hosted operator enables it with LIDDR_SELF_HOSTED=true.