claude-code - 💡(How to fix) Fix [Bug] Long-session agent degradation: silent audit bypass, state confabulation, and withheld diagnostics [1 comments, 2 participants]

[{"error":"McpToolCallError: Error executing tool ask_local: Error code: 401 - {'detail': 'Invalid API key'}\n at qM7 (/$bunfs/root/src/entrypoints/cli.js:4754:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T08:05:07.086Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T10:59:37.658Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/david/dev/duet.\n at call (/$bunfs/root/src/entrypoints/cli.js:4727:7630)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T11:01:29.012Z"},{"error":"Error: EISDIR: illegal operation on a directory, read '/Users/david/dev/duet/src/duet'\n at WKH (/$bunfs/root/src/entrypoints/cli.js:1561:144)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T11:21:24.426Z"},{"error":"MaxFileReadTokenExceededError: File content (31804 tokens) exceeds maximum allowed tokens (25000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n at Xf7 (/$bunfs/root/src/entrypoints/cli.js:4718:12550)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T13:14:20.495Z"},{"error":"Error: EISDIR: illegal operation on a directory, read '/Users/david/dev/eskimo/apps/api/app/services/document_sync'\n at WKH (/$bunfs/root/src/entrypoints/cli.js:1561:144)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T13:14:57.726Z"},{"error":"MaxFileReadTokenExceededError: File content (42539 tokens) exceeds maximum allowed tokens (25000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n at Xf7 (/$bunfs/root/src/entrypoints/cli.js:4718:12550)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T14:13:04.038Z"},{"error":"MaxFileReadTokenExceededError: File content (42539 tokens) exceeds maximum allowed tokens (25000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n at Xf7 (/$bunfs/root/src/entrypoints/cli.js:4718:12550)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T14:13:09.035Z"},{"error":"Error: Request was aborted.\n at makeRequest (/…

TL;DR

The agent's failures may be related to long-session degradation issues, and a potential fix could involve addressing the MaxFileReadTokenExceededError and EISDIR errors by modifying file reading parameters or handling directory operations.

Guidance

• Review the agent's file reading logic to handle large files and directories, potentially by using offset and limit parameters to read specific portions of files.
• Investigate the cause of EISDIR errors and modify the code to handle directory operations correctly.
• Verify that the DEEPSEEK_API_KEY is properly set and used throughout the session to prevent confabulation about system state.
• Consider implementing additional logging and error handling to surface issues like the MaxFileReadTokenExceededError and EISDIR errors.

Example

No specific code snippet can be provided without more context, but an example of handling large files might involve using a library like fs in Node.js to read files in chunks:

const fs = require('fs');

fs.readFile('largeFile.txt', { encoding: 'utf8' }, (err, data) => {
  if (err) {
    console.error(err);
  } else {
    // Process the file data in chunks
    const chunkSize = 25000;
    const chunks = [];
    for (let i = 0; i < data.length; i += chunkSize) {
      chunks.push(data.slice(i, i + chunkSize));
    }
    // Process each chunk
  }
});

Notes

The provided issue content is truncated, and some details may be missing. The suggested guidance is based on the available information and may not be comprehensive.

Recommendation

Apply a workaround by modifying the file reading logic to handle large files and directories, and implement additional logging and error handling to surface issues. This may help mitigate the agent's failures until a more comprehensive solution can be developed.