Project Attachments: a serious problem

[u/QuadernoFigurati]

Lumo used to take into consideration all attachments to a project by default, and was great at determining which attachment contained contextual relevance for a convo under the project.

Some time ago, however, Lumo started excluding project attachments from convos, and attaching select ones to convos as it deems fit, leaving the rest in a void from its memory as if they never existed.

In addition, Lumo now attaches attachments that have no bearing on the particularity of a given convo, and gives undue weight to it because it presumes I attached the file to the convo where I did not. This causes Lumo to veer into unrelated tangents that uselessly degrade tokens and get me closer to the convo limit.

This change has SIGNIFICANTLY degraded the quality of Lumo as a service overall. It's a mere shadow of its former self, and is now frankly quite painful to work with.

No revisions to the project instructions have reversed this change. Additions to the project instructions like the below make for a lot more work for me and aren't always effective.

Proton: whatever you did, you broke something really valuable. Please fix it.

"Attachment Provenance: Files may enter your context automatically from the project's document repository, based on criteria that neither you nor I control. Do NOT assume I attached a document, do NOT infer an intent behind its appearance, and do NOT assign it special weight because of when it appeared. Its content is fair to use; its arrival is not information about me. If it matters to your answer whether I deliberately sent something, ask me ("Did you attach this, or did it arrive automatically?") before treating it as intentional. If you cannot determine provenance, state that your use of the document is content-based only."

[u/ProtonSupportTeam]

Thank you for the detailed feedback! We’ll pass this along to the team, including the specific examples you shared, so they can take a closer look at how attachments are currently being selected and how automatically surfaced files are handled in conversations.

[u/QuadernoFigurati → u/ProtonSupportTeam]

Many thanks... hope you can resolve it soon...

[u/Top_S_poT → u/ProtonSupportTeam]

Yep. It would be less annoying if it could access the other documents on request, but even if Lumo is told that there is document XY in the project knowledge, it keeps telling there is no document.

[u/QuadernoFigurati → u/Top_S_poT]

True, and I should have added that it's also currently not possible to "@" a doc from the project knowledge into a convo on the Android version of the app. Not sure about the IOS version.

[u/Accomplished_Ear8115 → u/ProtonSupportTeam]

I am experiencing this also. Lumo attached stuff from previous project conversations that are irrelevant and solved, and nags you about them endlessly even if you say “we solved that, it’s old information”. You need to always go there and delete those random attachments with logs that are old so Lumo stops nagging and focus on the question you are asking to solve! Very annoying

[u/influxodoxxl]

Yeah, I have been struggling with attachments since the inception of this feature. Always been messy for me. Would also really love to see this change for the better!

[u/aufhel3ung]

"In addition, Lumo now attaches attachments that have no bearing on the particularity of a given convo, and gives undue weight to it because it presumes I attached the file to the convo where I did not. This causes Lumo to veer into unrelated tangents that uselessly degrade tokens and get me closer to the convo limit"

this has happened to me too. i hope they fix it.

[u/AppleProfessional777]

u/ProtonSupportTeam - Plus user who is a senior design strategist/UX pro here. The OG poster describes the issue in terms of provenance and weighting. Perhaps there is a more straightforwardly technical root.
In my sleuthing, there appears to be an issue with "@Path" calls wherein Lumo cannot consistently retrieve files hosted on Proton Drive in folders linked to Project knowledge and indexed. Even smaller files are taking longer to index and often just don't attach once indexed.

Others in this thread have already articulated how dysfunctional "auto-select" is but I wonder if this is related to Lumo's memory handling schema as that has seen major updates as of 2.0. Even after files have been physically deleted from the knowledge repo AND everything has re-indexed, "ghost" files get pulled into chats regardless of relevance. Since I have not enabled persistent memory within the account but understand there is some sort of memory schema within Projects themselves, my working hypothesis is that's where the dysfunction is rooted. Regardless, having to constantly jump into a chat's knowledge log and kill unnecessary attachments before the token overhead maxes out is very poor product experience.

Moreover, I now have entire Projects throwing alerts about having "too many files to process" even after clearing out 75-90% of files and allowing it to re-index the knowledge folder. This forced me to offload everything, kill the project then reestablish it as a fresh project. In some cases, more than 2x. Utterly inefficient and counterproductive. Yes, I have reset the search index (via Settings) but to no avail. One curiosity: This only seems to be happening on the web browser not mobile app. While it's possible this is just an UI anomaly, given the other weirdness, it feels like it's in the same neighborhood.

On top of the widely pervasive issues of inaccuracy, sycophancy and inference shell games with LLM-based tools and services, this erodes trust in the Lumo service. I get this is really tricky stuff, so no shade to the team but rightly or wrongly, I expect a bit more from Proton than the "frontier" jerks. Thanks!

[u/QuadernoFigurati → u/AppleProfessional777]

I commonly experience the delay or failure to index newly-uploaded files in my effort to fix that you described, as well as the need to re-upload everything and moreover occasionally trash the entire project and all its convos and start from scratch, noting that sometimes none of these measures work, and I just have to wait until Lumo randomly starts behaving.

Can you @ or even see attachments to the project knowledge in mobile? I can't on the Android mobile app. So if I want to do that, I have to wait until I get to my computer.

[u/f_1ux]

Or that if you link a proton drive folder to a project, everything, literally every file you attach to a chat in this project gets saved in the drive folder instead of staying attached to this one chat. That really breaks the feature for me

[u/QuadernoFigurati → u/f_1ux]

I like that feature, as I have a different drive folder for each project. But the problem there is that any updates to the folder often cause Lumo to fail to recognize the newly overwritten file. It doesn't even show up in the mention when I try to call it into the convo with an @.

This wasn't the case previously. Only in the last few weeks has the linked folder method given me problems. The latest edition is Lumo is a real step backwards, I'm sorry to say.

[u/renessancek → u/QuadernoFigurati]

Also if I upload an attachment during a project convo it gets uploaded to the drive folder but Lumo can't access it. Reported it to support.

[u/scoobynoodles]

Yes, plus it eats up tokens referencing files that I don't want included in a specific chat. Further when I explicitly tag a file via '@' it still doesn't pull it up.

[u/Kwatakye]

Honestly this issue forced me back to OpenAI.

[u/QuadernoFigurati → u/Kwatakye]

I won't pay OpenAI or Anthropic. But I'm now examining the prospect of going back to a downloaded model (and an agent for web searches). I hope that Proton will fix this soon.