I appreciate the feedback, but this appears to be a positive testimonial in French rather than a bug report for Claude Code. The message praises the tool overall but mentions a concern about Claude not reading entire files and potentially missing informati
Bug Description
y'a pas photo c'est excellent. je code depuis plus d'un an et demi avec un forfait max et il n'y a eu que du mieux. la suele chose en ce moment qui me derange c'est : incroybale parcours du code pr comprendre mais apres il par desuite dans la correction sans proposer se qu'il conte faire ou en fin je ne sais pas expliquer mais trop sur de lui ? genre maintenant j'ai de sfichiers qui commence a etre costaud et en lisant que 100 lignes ou en refusant de lire le fichier en entier i rate des infos et on dupplique des def ou ce genre d echose. c'est vraiment le seul point depuis le tout début qui me dérange cette faculté à ne pa slire en entier les fichiers mais juste en grep ou cherchant une def. pas sur au final qu'il utilise moins de contexte en faisant psk si il se trompe on a est bon pr recommencer lui dire de relire et sa revient au meme sauf que si on voit pas qu'il a mal lut on peut se faire avoir. voila en tout cas vous etes les best et claude <3
Environment Info
- Platform: win32
- Terminal: vscode
- Version: 2.1.45
- Feedback ID: b138e860-f195-4c3c-af11-c095ac251498
Errors
[{"error":"Error\n at nb (B:/~BUN/root/claude.exe:42:1144)\n at <anonymous> (B:/~BUN/root/claude.exe:43:10097)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:861:50)\n at processTicksAndRejections (native:7:39)\n at request (B:/~BUN/root/claude.exe:45:2149)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-18T14:01:12.137Z"},{"error":"MaxFileReadTokenExceededError: File content (36865 tokens) exceeds maximum allowed tokens (25000). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n at fYD (B:/~BUN/root/claude.exe:1304:7592)\n at async IYD (B:/~BUN/root/claude.exe:1308:2464)\n at async call (B:/~BUN/root/claude.exe:1313:5924)\n at async gME (B:/~BUN/root/claude.exe:3325:14119)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-18T14:02:28.699Z"},{"error":"Error: Failed to create shell snapshot: Command failed: C:\\Program Files\\Git\\bin\\bash.exe -c -l SNAPSHOT_FILE='C:\\Users\\lucpa\\.claude\\shell-snapshots\\snapshot-bash-1771423362925-akkqd5.sh'\n # No user config file to source\n\n # First, create/clear the snapshot file\n echo \"# Snapshot file\" >| \"$SNAPSHOT_FILE\"\n\n # When this file is sourced, we first unalias to avoid conflicts\n # This is necessary because aliases get \"frozen\" inside function definitions at definition time,\n # which can cause unexpected behavior when functions use commands that conflict with aliases\n echo \"# Unset all aliases to avoid conflicts with functions\" >> \"$SNAPSHOT_FILE\"\n echo \"unalias -a 2>/dev/null || true\" >> \"$SNAPSHOT_FILE\"\n\n echo \"shopt -s expand_aliases\" >> \"$SNAPSHOT_FILE\"\n\n \n # Check for rg availability\n echo \"# Check for rg availability\" >> \"$SNAPSHOT_FILE\"\n echo \"if ! (unalias rg 2>/dev/null; command -v rg) >/dev/null 2>&1; then\" >> \"$SNAPSHOT_FILE\"\n \n echo ' alias rg='\"''\\''C:\\Users\\lucpa\\.local\\bin\\claude.exe'\\'' --ripgrep'\" >> \"$SNAPSHOT_FILE\"\n \n echo \"fi\" >> \"$SNAPSHOT_FILE\"\n \n\n # Add PATH to the file\n echo \"export PATH=\\$PATH\" >> \"$SNAPSHOT_FILE\"\n \n\n # Exit silently on success, only report errors\n if [ ! -f \"$SNAPSHOT_FILE\" ]; then\n echo \"Error: Snapshot file was not created at $SNAPSHOT_FILE\" >&2\n exit 1\n fi\n \n at <anonymous> (B:/~BUN/root/claude.exe:1217:137)\n at exitHandler (node:child_process:109:27)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:778:16)\n at #handleOnExit (node:child_process:532:72)…
Note: Content was truncated.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗