auto-session VS persistence.nvim

The plugins are: https://github.com/goolord/alpha-nvim and https://github.com/rmagatti/auto-session

I use auto-session for session management and session-lens telescope extension for switching the sessions. When I switch to a different session, auto-session clears all buffers from my current session, including the modified ones, without warning. I'm wondering if there are any ways to prevent losing my changes. For instance, can I save the modified buffers in the session and load them on session restore, or configure auto-session to give me a warning before switching to a new session if there are unsaved changes? Alternatively, is there a way to use Telescope to display a list of recently modified buffers, so that I can review them before switching sessions and take appropriate action?

buffers: I open and close nvim instances all day long, using https://github.com/rmagatti/auto-session (or one of the many other session management plugins), it saves my buffers on a per git branch basis, so I lose nothing. nvim opens in less than a second, so this is no burden at all.

Yes, I use rmagatti/auto-session with some gnarly hacks to save a subset of window options, a per-session colorscheme, and some other wacky stuff so it stays 99.9% the same between sessions.

The correct one is : auto-session (I edited the mistake in the message above)

auto-session ?

I'm also using auto-session and nvim-tree which can both interact with the session.

Finally, to save sessions and move through them, check: auto-session

Yes, for this purpose, I'm using rmagatti/auto-session

persistence.nvim for using session management which is useful

i use persistence.nvim plugin, and i map the commands on my dashboard so i can open my last session

I've been using vim sessions for a while now. Sessions can have their own configuration files and that's what I use for projects. For this to be actually convenient you'll need plugin like persistence.nvim to handle the sessions themselves (or make your own workflow).

I like the idea of a "config" module. Plugins like persistence and mason.nvim have it, they allow you to set variables without calling the main module.

persistence.nvim: Small session manager. I use some of its functions to also manage project local configs. It is because of this plugin I can use language servers the way I want.

persistence.nvim * Automatically save active session to a configurable directory * API to load most recent or current session based on cwd * No direct support for a telescope picker but could probably be setup with vim.ui.select()

yeah, I was planning on shimming this functionality out to another plugin. sessions have little to do with a startup gui imo. i mention in the docs using something like https://github.com/folke/persistence.nvim