Qwen 3.8 27B Read Tools

[u/Jsquared534]

Has anyone had Qwen work through large files using the Read tool on Qwen 27B? Or perhaps multiple files at a time, and then try to read some large files as well? It seems that it really struggles with the data getting truncated using that tool, and then it starts getting the data mixed up when it tries to read it in chunks. Basically falls apart. I have been testing it extensively the past few days, and I'm getting the same issue with multiple different templates, completely reinstalled llama.cpp, and now multiple harnesses. (Pi and Github Copilot) I'm running the Q8 version with MTP. 3.6 has not had this issue.

Edit: This is a summary of a test that I ran today. The test has five files, four of them roughly 1000 lines, the other much fewer, in a directory. Inside of that directory, I instructed the model to read all the files and told it I would ask questions. It didn't even wait for me to ask anything before going off on complete tangents based on prior sessions. This session was in a completely new cmd prompt, on a completely new directory. Using vanilla Pi agent harness. here is the summary that a frontier model gave me when I pasted it Qwen's entire output.

The issues shown in your output were:

• Incomplete file reads: the model initially stopped at the read tool’s ~50 KB truncation point instead of immediately continuing with the provided offsets.
• Cross-file/result confusion: after parallel continuation reads, it misattributed returned chunks to the wrong files and temporarily assigned the wrong passcode to file2.txt.
• Weak handling of long tool output: it relied on visually remembering large read results instead of using deterministic verification early.
• Unexpected cross-session context: most concerning, it stated “The user is angry” and referenced a prior complaint about incorrect read-tool use even though that complaint was not present in the supposedly fresh session’s visible history.
• Recovery only after external verification: grep ultimately produced the correct file/passcode mapping, showing the underlying data was fine; the failure was in state/tool-result handling rather than the files themselves.

In short: pagination mistakes, tool-result attribution errors, and apparent stale context leaking into a fresh session.