Overview


Local FS points PipesHub at a folder on your computer so its files are searchable from chat and the knowledge base. PipesHub only reads the folder — it never moves, renames, copies, or deletes anything, and there's no login, API key, or cloud account involved. You give it a folder path and that's the whole setup.It's a personal connector: files you index are searchable by you alone, not shared with your team.


How it works


The first sync walks every file in the chosen folder, and every subfolder if that option is left on. Under 1,000 files takes a few minutes; 10,000 to 100,000 can take 30 minutes to two hours. Later syncs only look at what changed — new files are added, edited files re-indexed, deleted files removed.Documents, plain text, and code files are parsed so their contents are searchable. Images, video, audio, and archives are stored by filename and metadata only. Password-protected PDFs and Office files can't be indexed unless unlocked.


Configure
  • Confirm which machine runs the connector — under Docker or Kubernetes the folder must be mounted into the container

  • Open Workspace Settings from the profile menu, then Your Connectors under Personal, and click + Setup on the Local FS card

  • On the Authenticate Instance tab, enter a recognisable instance name — there are no credentials to paste

  • On Configure Records, set sync strategy and interval, enter the local folder path, and choose whether to include subfolders

  • Optionally add file extension or date filters under Indexing & sync filters, then save

  • Switch on the Sync Enabled toggle — the connector won't read anything until a manual sync or schedule runs

Local FS

Index files from a folder on your machine with no login required.

GitHub

…k

GitHub stars in 12 weeks.

Discord

500+

Active developers on Discord.