Problem
The Reference external source flow currently supports managed sources such as Feishu knowledge bases and Unity engine docs, but it does not support importing files or folders from the local machine.
This makes it hard to use local project notes, Markdown docs, text references, or other local documentation as searchable Reference material inside Locus.
Expected behavior
Users should be able to:
- Choose a local file or folder as a Reference external source.
- Import supported text documents as a read-only Reference snapshot.
- Keep imported content aligned with existing external-source behavior:
- managed read-only content
- searchable-only by default, without L1/snippet injection
- external source metadata recorded on directories and documents
- Optionally remember the source path so additions, edits, and removals can be synced manually later.
Design direction
A snapshot import model is preferred over live-linking arbitrary local files.
This keeps the Reference index stable, avoids depending on local filesystem state at query time, and aligns better with the current managed external-source model used by Feishu knowledge bases and Unity docs.
Problem
The Reference external source flow currently supports managed sources such as Feishu knowledge bases and Unity engine docs, but it does not support importing files or folders from the local machine.
This makes it hard to use local project notes, Markdown docs, text references, or other local documentation as searchable Reference material inside Locus.
Expected behavior
Users should be able to:
Design direction
A snapshot import model is preferred over live-linking arbitrary local files.
This keeps the Reference index stable, avoids depending on local filesystem state at query time, and aligns better with the current managed external-source model used by Feishu knowledge bases and Unity docs.