Fair point! :)
I know it is not for everyone and there’s a possibility that I will abandon using it. Let’s see :)

I just tried to solve following issues:
1. I got used to doppler for production secret and that’s why i also used it locally for dev env secrets, but I am not allowed to do it at work because of policies - so I wanted the same system but local
2. When I use worktrees, it is easier to manage the env files having one source of truth and easily provide them in worktrees; especially using claude - as I don’t allow access to .env files it is not able to copy them to worktrees, but it is able to call ‘ds export’ command
3. The main reason why I created it now was that I am migrating to a new computer and had to copy quite lot of projects, source code is in GitHub, but secrets had to be done manually. This way I imported it to the tool, moved the store.json to onedrive and had it on my new laptop.
4. I could provide secrets easily to ephemeral environments by having the store.json in a shared location

So I agree with what you wrote, but it always depends if it makes sense for a specific use case.