Adding another use case to this: keeping a CHANGELOG.md in a linked Drive folder.

My setup is a Project with a linked Proton Drive folder holding a changelog
file that I update as work progresses. I want Lumo to always work from the
current version.

The support docs say: "Whenever new assets are added to the linked Proton
Drive folder, Lumo will automatically refer to them when working on the
current Project." That wording covers new files appearing, but says nothing
about an existing file whose contents change. So it's unclear whether editing
a file in place triggers re-indexing, or whether Lumo keeps serving the
version it first indexed.

Two things would resolve this:

1. Documentation of what actually happens when an existing linked file is
modified. Does the index refresh, and if so, how quickly?

2. If it doesn't refresh, a way to force it. Removing and re-adding the file,
or re-linking the folder, is workable but tedious for something that
changes often.

As a workaround I'm considering versioned filenames (changelog-1.0.md,
changelog-1.1.md) so each update counts as a "new asset" under the documented
behaviour. Downside: old versions accumulate in Project Knowledge and may get
retrieved alongside the current one.

Related: even when a file is current, the @ mention picker doesn't always list
every file shown in Project Knowledge, so it's hard to tell whether a stale
version is being served or the file simply wasn't ranked as relevant.

Same here.
I would expect that lumo can find and read (and write) to the linked project folder.
Otherwise it makes not much sense if I still have to manually add the files in each project chat.
My usecase would be something like this:
Link a folder in a project.
Add or update files in that proton drive folder (e.g. markdown daily journal files or so)
Then chat with Lumo about the content in these files (with always the newest file versions)
Or am I missing something?

Update:

lumo seems to be able to find and pickup some files like txt or md
But e.g. jpg files do not work even if they are listed and can be referenced via "@" they are not passed to lumo and the LLM says that it only got the filename and not the jpg itself

Further- when referencing files in the linked drive folder, sometimes Lumo only sees older/cached versions of the files, rather than the updated / synced / new versions in the folder. Even though the Project settings clearly show the latest files.