continue icon indicating copy to clipboard operation
continue copied to clipboard

[CON-226] File watcher on config.json to catch updates from outside the currently open window

Open sestinj opened this issue 10 months ago • 5 comments

Validations

  • [X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
  • [X] I'm not able to find an open issue that requests the same enhancement

Problem

When I update config.json programmatically or from another VS Code/IDE window, the changes aren't automatically reflected as they are when I save the file within my current window.

Solution

To solve this, we need to add a file watcher that can catch all changes to config.json even from outside the current window.

CON-226

sestinj avatar Apr 18 '24 18:04 sestinj

In fact, if I change config.json in a VSCode editing pane (and not through the Continue wizard that modifies the file), I will sometimes get error messages similar to the screenshot below. In this case the codellama:13b was running on a remote server, and I provided the API URL in the config.json file, but something in Continue seemed to be assuming it was on localhost. The problem went away and Continue was able to access and use that remote model after I re-started VSCode: image So, this is primarily a feature request, but it would hopefully also fix a bug where newly added remote models were not loaded correctly.

amfred avatar Apr 19 '24 21:04 amfred

Good to know! I just made an update to add a global file watcher in this commit, and it should be in pre-release later today. Will be curious to see if this solves the URL problem

sestinj avatar Apr 19 '24 21:04 sestinj

Pre-release worked for me. The model I added (actually some ollama autodetect url) from my extension was detected/listed in the models combo. Now waiting for a solution to #1149

fbricon avatar Apr 23 '24 10:04 fbricon

You'll prolly want the IJ extension to watch the config file as well

fbricon avatar Apr 23 '24 10:04 fbricon

Absolutely. Will be making the corresponding IntelliJ update for release 0.0.46 later this week. I'll keep this issue open until that is completed

sestinj avatar Apr 24 '24 07:04 sestinj