Qoder IDE encounters critical issues when handling multi-line Python f"""...""" strings that include special prompt tokens such as <|im_start|>, <|im_end|>, etc. Specifically, it fails to generate or continue code after the f-string, hallucinates irrelevant content, or becomes unresponsive. This behavior breaks workflows when working with LLM prompt engineering, especially in projects using formats like ChatML (e.g., Qwen, LLaMA models).Steps to Reproduce
Expected Behavior
-
Qoder should parse multi-line f-strings normally.
-
Code completion and editing should function smoothly after the string block.
-
Special tokens like
<|im_start|>and<|im_end|>should not disrupt parsing or generation.
Actual Behavior
-
Code completion halts or behaves incorrectly.
-
The IDE sometimes generates unrelated or malformed code (“hallucinates”).
-
Editor freezes or becomes unresponsive after this point.
-
Entire class or file may not load properly after encountering the f-string.
Screenshots / Screen Recordings
Operating System
windows 10 pro
Current Qoder Version (Menu → About Qoder → Copy)
Qoder version 0.2.6
and has anyone else experienced this issue or found a fix?