You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
read_file ignores offset/limit arguments and returns the whole file (v0.2.46, DXT on Windows) #686
Title: read_file ignores offset/limit arguments and returns the whole file (v0.2.46, DXT on Windows)
Body:
Environment: Desktop Commander 0.2.46 installed as DXT inside Claude Desktop (client reports local-agent-mode-Desktop Commander 1.0.0), Windows 11 x64, Node 24.18.1 (Electron 42.10.0). fileReadLineLimit is the default 1000.
Steps to reproduce:
Call read_file with path pointing to a UTF-8 markdown file of ~130 lines and limit: 3 (also tried with offset: 0, limit: 3).
Observe the response.
Expected: 3 lines (per the tool description: "Read the file in chunks using offset and limit").
Actual: the whole file is returned (130 and 134 lines in two cases). For a 1002-line file the response was cut at 1000 lines, i.e. pagination appears to follow fileReadLineLimit only and the per-call limit is not applied. Reproduced three times in one session on three different files. Reading the same line range with a small Python script returns the expected 3 lines, so the files themselves are fine.
Impact: every read_file on a large file fills the model context with the full file, defeating the purpose of offset/limit.
Happy to provide the exact request/response JSON if useful (files are private, but I can reproduce on a synthetic file).
Activity