Fresh install
vs code 1.100.2 (also completely deleted it and reinstalled while debugging)
Cody extension: (auto updated) 1.94.2
(i did try multiple older versions but still no change)
error:
mainThreadExtensionService.ts:79 TypeError: models2.localModels is not iterable
at c:\Users\schie.vscode\extensions\lib\shared\src\models\modelsService.ts:392:59
at Object. (c:\Users\schie.vscode\extensions\node_modules.pnpm\observable-fns@0.6.1\node_modules\observable-fns\dist.esm\map.js:30:46)
at Generator.next ()
at c:\Users\schie.vscode\extensions\node_modules.pnpm\observable-fns@0.6.1\node_modules\observable-fns\dist.esm\map.js:7:71
at new Promise ()
at __awaiter (c:\Users\schie.vscode\extensions\node_modules.pnpm\observable-fns@0.6.1\node_modules\observable-fns\dist.esm\map.js:3:12)
at c:\Users\schie.vscode\extensions\node_modules.pnpm\observable-fns@0.6.1\node_modules\observable-fns\dist.esm\map.js:29:50
at AsyncSerialScheduler. (c:\Users\schie.vscode\extensions\node_modules.pnpm\observable-fns@0.6.1\node_modules\observable-fns\dist.esm_scheduler.js:30:19)
at Generator.next ()
at fulfilled (c:\Users\schie.vscode\extensions\node_modules.pnpm\observable-fns@0.6.1\node_modules\observable-fns\dist.esm_scheduler.js:4:58)
Im seeing a model issue and its because its not set im pretty sure, as im only on a pro account and not looking to do custom models. There seems to be a visual ui issue as I cannot see the prompts or model dropdown in the text box. I also cant see the context menu when right clicking a file to add to context. Sorry for the inconvenience, I use Cody with work and am setting up a personal account, am I doing something wrong bc all set up states to just auth with GitHub or google, then it should just work.
**
**
continuation due to post limitations:
@JustinSchieck Have you changed something in the settings.json file which might infer with the Cody settings?
Thanks for the quick response!
attached my settings, this is from years of use so there may be another extension that is fighting back, but no only thin should be my settings sync as I dont want it syncing with my work laptop and verbose debugging for this chat.
Based on the file, there are no settings that should interfere with the IDE. Try to re-install Cody to the latest version.
Sorry @PriNova but ive done that 15 times now. Ive also reinstalled VScode twice out of sheer stubborness lol. Same issue persists
If you are using any kind of VPN or proxy services?
What you can do as a last resort, is to generate an access token in your Sourcegraph client portal, logout from Cody and use the Sourcegraph URL method. Use https://sourcegraph.com URL and paste your access token in the field. Then restart the IDE.
This should resolve the issue
ill try that this evening thanks!
1 Like
Sorry just getting back to this thanks to being super busy with work. I have done the access token login option and it has not changed anything. Cody only stopped working once i started a paid account. It still logs me in but doesn’t generate a response when I ask a question.
output in cody by sourcegraph teriminal =
ClientConfigSingleton refreshing configuration
█ ClientConfigSingleton refreshed: {“codyEnabled”:true,“chatEnabled”:true,“autoCompleteEnabled”:true,“customCommandsEnabled”:true,“attributionEnabled”:false,“attribution”:“none”,“smartContextWindowEnabled”:true,“modelsAPIEnabled”:false,“latestSupportedCompletionsStreamAPIVersion”:9}
█ telemetry-v2 recordEvent: cody.editChatButton/clicked: {
“parameters”: {
“version”: 0,
“metadata”: [
{
“key”: “tier”,
“value”: 1
}
],
“billingMetadata”: {
“product”: “cody”,
“category”: “billable”
}
},
“timestamp”: “2025-06-15T16:42:19.715Z”
}
█ ChatController: postError Failed to edit prompt
█ telemetry-v2 recordEvent: cody.humanMessageEditor/submit: {
“parameters”: {
“version”: 0,
“metadata”: [
{
“key”: “isFirstMessage”,
“value”: 1
},
{
“key”: “isEdit”,
“value”: 1
},
{
“key”: “messageLength”,
“value”: 4
},
{
“key”: “contextItems”,
“value”: 0
},
{
“key”: “intent”,
“value”: 0
},
{
“key”: “tier”,
“value”: 1
}
],
“billingMetadata”: {
“product”: “cody”,
“category”: “billable”
}
},
“timestamp”: “2025-06-15T16:42:19.727Z”
}
█ siteVersion Failed to get site version from https://sourcegraph.com/: AbortError: This operation was aborted
I also seen this one with a similar post error but checked it wasnt folder structure as I moved everything to my C:dev folder so it only had one layer to drill into and had the same issue : Failed to retrieve search context: EvalError: symf failed: Error: spawn ENAMETOOLONG
I did find the log file for the network calls photo attached
while using cody in web, its stating that the missing model dropdown from the ui is a failing part of the intialization process thats critical. if that helps at all
Hey @JustinSchieck Is see from your logs, that you are in “Edit” mode instead of the “Chat” mode. Did you click that mode?
chat was default selected when i opened it just now and i switched them back and forth to no change on the ui, if the model doesnt initialize, does cody say its in edit mode but not show it in the ui? Im seeing in the parameters from the cody.humanMessageEditor/submit object, isEdit is 0 so we may have (somehow) conflicting values between functions?
one issue i am seeing is this, but its just a file under a Z: drive. not sure how its grabbing this link but looks like its causing the brackets to fail closing.
This should typically not affect the model syncing process even the path for the symf runner looks suspicious. For the empty model, are you in any enterprise network environment or any non-direct network?
no network related change or enterprise connections. this is a personal pc and i dont run a vpn or anything currently on my home network
the only log issue im seeing is the brace issue on the Symf runner, im not sure how to fix the Z: drive location being parsed but the curly brace opener is being commented out. you can see the formatter shows it as red meaning there might be an object not being utilized properly
@JustinSchieck How many chat histories are listed. Some users are reporting that when a specific threshold exceeds, a deletion of the chat history may help here. Maybe there is a corrupt entry in the indexing.
there is no history as its never worked. seeing as its getting sunset, im just going to delete the extension. Thanks for trying.
You are welcome. It is a pleasure to help. Give Amp a try as we move forward.
