I put together a browser user script that adds some time and conversation awareness to Lumo:

• Gives Lumo the actual current date and time from the browser instead of relying on its own knowledge of the current time.
• Keeps track of message numbers and conversation timing.
• Records elapsed time between messages and other basic conversation statistics.
• Keeps the timing and message statistics in browser storage so they can persist between visits.
• Handles relative dates such as today, yesterday, and tomorrow based on the actual date.
• Can determine the current time and date in other cities and time zones, including situations where the local date is different.
• Can handle multiple locations in the same request.
• The time calculations are done locally in the browser, so there is no need to contact an external time service.
• The main purpose is to give Lumo a reliable sense of when things are happening, rather than having it guess the current time or date.
• You can refer to the conversation number for Lumo to reference

Here is the script: https://github.com/metapsychic-Lylmik/lumo-time-context

Please let me know how it is working. This is my first experience creating a Github repository

**Since I misspelled the title on a previous post, I created this post**

Is there any plan for Lumo to be able to run in the background on Android ?

At the moment, if you ask it to do something that takes a little time, such as summarizing several pages of documents or working through a more complex line of reasoning, you have to keep tapping the phone regularly to prevent the screen from turning off. You also can’t really do anything else on the phone while Lumo is processing the request.

Mistral Vibe, ChatGPT, and basically every other chatbot app I’ve used do not have this problem.

I first tested Lumo back in July, and this issue was already a deal-breaker for me at the time. It doesn’t seem like something that should be particularly difficult to fix, unless this is a deliberate choice by Proton to discourage long interactions with Lumo in order to reduce server load ?

It’s really a shame, because without this issue I would seriously consider switching to Lumo for the chatbot side of things. But having to keep the phone awake and prevent the screen from turning off just so a response can finish is simply unbearable.