Context Issues in Chat

I have added one of many of my conversations here, but I am not sure I understand fully why this is happening. I have shared files directly as the entire file or pasted the lines of code into the chat window where I can see it in the chat, yet the model, in this case, Claude-3.5-sonnet, is admittedly unable to see it. While this is annoying, a more significant issue is wasting my prompts in my subscription, going round and round on questions and debugging that should be solved in one iteration if it were to see the file(s)/code as it should.

I’m not sure if there is some timeout hardcoded for sync, as I didn’t see this in the settings for context, but if I close out the app and resync the folder, the chat will see the files I have shared.

You have also failed to allow me to properly articulate the issue as I can only add 1 image/screenhot here. How is that helpful to anyone?

What am I missing here?? Should this be a bug report?


  • Version: 0.44.5
  • VSCode Version: 1.93.1
  • Commit: 1d610252e6812bf33245763f0742a534fd0f1d90
  • Date: 2024-12-20T00:02:28.554Z
  • Electron: 30.5.1
  • Chromium: 124.0.6367.243
  • Node.js: 20.16.0
  • V8: 12.4.254.20-electron.0
  • OS: Darwin arm64 23.6.0

Thank you,

-garotm

Not sure what happened when I posted this but it cut most of what I was saying out… I ended up opening a bug here Context Issues in Chat Mode

same issues and worse.
Cant copy paste anything. Absolutely drunkard behaviour from the bots again.
It is like you converse with a competent assisent for 2h only for him to turn drunkard midwork…absolutely pathetic performance

1 Like

oddly, this has [de]volved into directory unawareness as well.

Hey, do you still have this issue if you start a new composer session? We’ve had a few reports of this, but we think it’s currently only seen on certain, long running composer sessions.

Regardless, we are looking at this and hope to fix it very soon.

No, the issue is resolved [until it happens again] in a new composer session. While that is a “solution,” you lose context from the previous conversation. I also find that I have to “remind” the AI to review shared files or the entire directory structure more often than I would expect; e.g., in every exchange, I have to remind it to look at the .eslintrc.json file, for example, otherwise the linting “claims” it passes on the composer side, but when I run actual linting tests, it’s a mess.

Yeah, makes sense, but good to know on our end that it’s solved by a new session! We are working on getting this resolved in the meantime.

1 Like

Appreciate the effort :slight_smile: