old config erased by update

[working-name]

Before submitting your bug report

• I believe this is a bug. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: macOS
- Continue version: 1.1.45
- IDE version: 1.100.2
- Model: n/a
- config:
  
n/a, default stuff you put in?
  
  OR link to assistant in Continue hub:

Description

updated from an older version which had the JS version of the config. Stuff didn't port over, file was removed from $HOME/.continue.

To reproduce

1. have an old version with custom js based config
2. update to whatever above
3. select to manage locally rather than the in-your-face-login crap
4. open the config to find default llama 3.1 et al config.
5. look for your old config, fail to find it. Be upset. Kick the table. Grab the foot. Ouch! Cuss a bit. Wait what? I can only type 3...

Log output

🤷‍♂️ nothing's there