You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: account delete does not verify passwordΒ #3297
Hey, I'll pick this up. The main reason we didn't implement this before is because, if the user loses their password, they have pretty much no way of deleting their account.
The reasoning is that:
a) The current set-up is mostly safe, since someone can't really log in without the session token.
b) If you lose your password, you kind of have no mechanism to delete your account.
I am working on adding a new "admin " set of CLI tools to the server which will enable the person who manages the self-hosted server to delete pretty anyone, and we'll implement your request afterwards.
Thank you for looking into this. Not sure why, but I did not get a notification mail. github sometimes buggy.
You are correct. You have to know the password to login so that you can delete account. But I was a bit confused that I was asked for password and then after entering the wrong one, my account was still deleted. So something in flow not correct.
If not checking correctness of password this prompt can be changed to "Do you want to REALLY delete your account?" and only if answer is yes or y the account is deleted. Currently the account is deleted when answering anything, so prompt makes no sense.
I checked database and account really not there anymore.
doh you even mentioned it, sorry, i missed it. I'm aiming to implement this for the next release, since it seems like a security concern. investigating right now
It did not work when I only used the new client. Then I updated the server and it worked. Thank you.
But I also see another error: Error: could not ask the daemon for its status: code: 'The system is not in a state required for the operation's execution', message: "daemon is build 18.24.2+854654ec1ec6d13e0eb2468a6e57b2e2044a2162, client is build 18.24.3+4532ceacd860885c2310ab8fab92a1bc00d6d7e8"
I cannot even stop the daemon, but needed to kill it with kill PID. This seems strange to me that I cannot restart/stop the daemon or that atuin does the restart automatically. Other daemon operations make sense to not able to run, but stop/restart?
Activity
jaimep12 commentedon Mar 30, 2026
markovejnovic commentedon Jul 15, 2026
Hey, I'll pick this up. The main reason we didn't implement this before is because, if the user loses their password, they have pretty much no way of deleting their account.
The reasoning is that:
a) The current set-up is mostly safe, since someone can't really log in without the session token.
b) If you lose your password, you kind of have no mechanism to delete your account.
I am working on adding a new "admin " set of CLI tools to the server which will enable the person who manages the self-hosted server to delete pretty anyone, and we'll implement your request afterwards.
Thanks for opening the issue!
jaimep12 commentedon Sep 23, 2026
Thank you for looking into this. Not sure why, but I did not get a notification mail. github sometimes buggy.
You are correct. You have to know the password to login so that you can delete account. But I was a bit confused that I was asked for password and then after entering the wrong one, my account was still deleted. So something in flow not correct.
If not checking correctness of password this prompt can be changed to "Do you want to REALLY delete your account?" and only if answer is
yesorythe account is deleted. Currently the account is deleted when answering anything, so prompt makes no sense.jaimep12 commentedon Oct 19, 2026
Did you see my last reply? Sorry, but it was a month ago.
markovejnovic commentedon Oct 24, 2026
Just saw. That looks suspicious. I am guessing that the account didn't actually get deleted. I'll get a reproduction and a fix.
jaimep12 commentedon Oct 26, 2026
I checked and the account was deleted. It is no longer in database.
markovejnovic commentedon Oct 26, 2026
Got it, thanks for checking!
markovejnovic commentedon Oct 28, 2026
doh you even mentioned it, sorry, i missed it. I'm aiming to implement this for the next release, since it seems like a security concern. investigating right now
fix(server): check the password before deleting an account (#4572)
jaimep12 commentedon Oct 28, 2026
I will test this when the new version is available. Thank you.
jaimep12 commentedon Oct 29, 2026
It did not work when I only used the new client. Then I updated the server and it worked. Thank you.
But I also see another error:
Error: could not ask the daemon for its status: code: 'The system is not in a state required for the operation's execution', message: "daemon is build 18.24.2+854654ec1ec6d13e0eb2468a6e57b2e2044a2162, client is build 18.24.3+4532ceacd860885c2310ab8fab92a1bc00d6d7e8"I cannot even stop the daemon, but needed to kill it with
kill PID. This seems strange to me that I cannot restart/stop the daemon or that atuin does the restart automatically. Other daemon operations make sense to not able to run, but stop/restart?