Btw, before installing on your server, you can try to use demo at https://demo.will-be-done.app/

Hey! Yep, it’s planned. I already have openapi - so server already have capabilities. Also, CLI support is planned too, so agent also will be able to use CLI

Hey! Yep, thanks for the kind words. I’m fully responsible for the architecture and system design. I spent a lot of time thinking this through, and how to build good local-first apps was on my mind even before AI (I built a note-taking app called Harika before and worked at RemNote).

Nah, it will very hard to do. I wanted it to be fast from the start, so I was playing with sync and how I store data in browser.

I actually agree with you. I was avoiding making doc the whole time, but as amount of features growth, readme is not enough. I will introduce a good doc soon. Thanks!

You still need to sign up to sync between devices. With the self-hosted version, you also create an account, but authentication and all synced data stay on your own server.

Offline-first means the app works without an internet connection; it doesn’t necessarily mean that no account is required. After sign up/sign in, you can use it offline without any problems.

It is just LWW per column. On each client I track last change of each field with current time(actually sysytemTime-counter-clientId to make time uniq). Then, when changes arrive to server, I compare previous clock time with new clock time from client. If client win, it overwrite server column time + value. No tracking causality for now, just current system time of the client.

Fixed. Thanks for the hint!