Hi - since Tabby utilize your personal auth token for chat panel / server communication, could you verify if the auth token changed during your restart? If not, can you share the output panel logs when you getting logout?

So I checked (it is happened right now), from the avatar menu the token before writing in the chat panel and after the login it is the same.

This is what I get after login, use it a bit and I get a logout again.

Can you share your auto-start setup for Tabby?

I have this script on auto start in KDE on Linux:/[path]/tabby_x86_64-manylinux2014-cuda122/tabby serve --model Qwen2.5-Coder-7B --chat-model Mistral-7B --device cuda --port 5000 &

My best guess is that your setup initiates multiple Tabby processes, which in turn causes the SQLite database to become locked. I recommend configuring a supervisor to prevent such situations.

I can confirm that there is only one tabby process as I have just one in the process manager when I have to kill to restart it.

Depending on your process termination setup, you might not be waiting for the process to exit gracefully, which could result in the SQLite database file being locked.

checkhttps://stackoverflow.com/questions/151026/how-do-i-unlock-an-sqlite-database for a potential workaround

What is the path for the database? So I can check when happens again.

I see adb.sqlite-journal file generated but appears/disappear.
I think because it is still processing the chat reply and saving it in the meantime that I am trying again.