Skip to content

Fix for issue #308 The "chat with AI" is not reading the given file and fires an exception#312

Closed
stefanofornari wants to merge 1 commit into
jeddict:mainfrom
stefanofornari:ste/fix/308_chat_not_reading_the_given_file
Closed

Fix for issue #308 The "chat with AI" is not reading the given file and fires an exception#312
stefanofornari wants to merge 1 commit into
jeddict:mainfrom
stefanofornari:ste/fix/308_chat_not_reading_the_given_file

Conversation

@stefanofornari
Copy link
Copy Markdown
Collaborator

@stefanofornari stefanofornari commented Mar 21, 2026

I wasn't able to reproduce the issue, it may be due to additional extensions given to the configuration. However, the bug is there and this PR proposes the fix.

In looking at the code and doing some experiments, though, I believe we should not send all files in Ask mode neither: if you do open a chat in ask mode with Jeddict-ai project you saturate the context window right away.

Copy link
Copy Markdown
Member

@jGauravGupta jGauravGupta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previously agentEnabled determined behavior (agent mode sent only file paths for lightweight context, ask mode included full file content), but this change removes that branching and now always processes and sends file content, which may impact performance and alter expected agent-mode behavior.

@stefanofornari
Copy link
Copy Markdown
Collaborator Author

Uh... yes you are right, as it is, it does not make sense. I will fix it. What do you think of the most general question about sending everything in ask mode? It seems still dangerous to me...

@stefanofornari stefanofornari deleted the ste/fix/308_chat_not_reading_the_given_file branch April 6, 2026 10:52
@stefanofornari
Copy link
Copy Markdown
Collaborator Author

I have created #319

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants