[BUG] Status column is preserved with the session

[AllergicMushroom]

Describe the bug
If you update the statuscolumn and open a saved session, already open buffers will still have the old statuscolumn.

To Reproduce
Steps to reproduce the behavior:

1. Set a statuscolumn in config files.
2. Create and save a session with at least one open buffer.
3. Change the statuscolumn.
4. Load the session and open a new buffer.

Expected behavior
All buffers have the new statuscolumn. In practice, the previously opened buffers will have the old one, while the new opened buffer will have the new statuscolumn.

Checkhealth

auto-session: ✅

Setup ~

• ✅ OK setup() called

Lazy.nvim settings ~

• ✅ OK Lazy.nvim support is enabled
• ✅ OK auto-session is not lazy loaded

Config ~

• ✅ OK No config issues detected

Current Config ~

• {
  auto_create = false,
  auto_delete_empty_sessions = false,
  bypass_save_filetypes = { "dashboard" },
  log_level = "error",
  session_lens = {
  buftypes_to_ignore = {},
  load_on_setup = true,
  picker_opt = {
  border = true
  },
  previewer = false
  }
  }

Baseline (please complete the following information):

• Result of set sessionoptions?: sessionoptions=blank,buffers,curdir,folds,help,tabpages,winsize,winpos,terminal,localoptions
• OS. e.g uname -a: Linux everfrost 6.18.2-arch2-1 Error in clean install #1 SMP PREEMPT_DYNAMIC Thu, 18 Dec 2025 18:00:18 +0000 x86_64 GNU/Linux
• Neovim version nvim --version:
  NVIM v0.11.5
  Build type: RelWithDebInfo
  LuaJIT 2.1.1765228720
  Run "nvim -V1 -v" for more info

[rmagatti]

statuscolumn can be saved to the session file if you do vim.o.sessionoptions:append("options").

Note however that this will save a lot more than statuscolumn, things you might not want saved. I've personally found that adding options to sessionoptions can lead to undesired states, which is why we don't recommend it in the project's README.

[AllergicMushroom]

Can we decouple statuscolumn and "options"?

[rmagatti]

That would be more of a question for neovim/neovim. Auto Session can't really decouple these without re-implementing Neovim's mksession. We rely on the builtin session functionality already available.

That being said, auto-session offers you good control, so you should be able to do something like this:

require("auto-session").setup({
    save_extra_data = function(_session_name)
        return vim.fn.json_encode({
            statuscolumn = vim.o.statuscolumn,
        })
    end,

    restore_extra_data = function(_session_name, extra_data)
        local ok, data = pcall(vim.fn.json_decode, extra_data)
        if ok and type(data) == "table" and type(data.statuscolumn) == "string" then
            vim.o.statuscolumn = data.statuscolumn
        end
    end,
})

Give it a shot and let me know if it works for you?