BelKed

I believe this was resolved in https://github.com/ActivityWatch/aw-watcher-web/pull/175 and released in version `v0.5.3`. Could you please check which version of the extension you currently have installed? If possible, try updating to...

Seems that it haven't been fixed by #175, when I'll have time, I'll look into it. Thanks for reporting :)

The problem seems to be that you are using a PM account. Groundspeak must have changed something in the (premium) search again :/

Great! Just one suggestion — when you’ll be setting up the CI, you might want to generate all the necessary files directly in the pipeline. This will help keep everything...

Hi, I can't reproduce this issue on macOS. Could you please check the following? - When you click on the ActivityWatch Web Watcher extension icon, does it show **Browser:** `edge`?...

There are currently some known issues with the Chrome version of the extension due to Manifest V3 changes. I haven’t had a chance to look into it recently, as previous...

The new release will be available soon, as @ErikBjare promised. In the meantime, feel free to install it from the source if you don't see it in the web store...

We just released `v0.5.0`, feel free to install and open a [new issue](https://github.com/ActivityWatch/aw-watcher-web/issues/new/choose) if there are any bugs :)

After clicking the button it should open [**Category Builder**](http://localhost:5600/#/settings/category-builder) or just the [**Settings**](http://localhost:5600/#/settings) while scrolling down to the **Categorization** part?

That's just a limitation of the web UI, the events are very likely categorised correctly — take a look at **Category Tree** ;) You'll need to update your categorisation rules...