claude-code - 💡(How to fix) Fix [Bug] System prompts and persona constraints not being applied during session [1 participants]

[{"error":"Error: EISDIR: illegal operation on a directory, read 'C:\Users\Admin\OneDrive\Obsidian\Daily Vault\Chief of Staff\Session Logs'\n at L4H (B:/~BUN/root/src/entrypoints/cli.js:3993:15399)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-12T16:33:25.357Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\Admin\AppData\Local\Temp\claude\C--Users-Admin-OneDrive-Obsidian-Daily-Vault\2b169b45-f6c6-4157-9e05-b275882e8dc7\tasks\a114c308ed5f6aff0.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:7823:299)","timestamp":"2026-04-12T17:22:53.545Z"},{"error":"Error: File does not exist. Note: your current working directory is C:\Users\Admin\OneDrive\Obsidian\Daily Vault.\n at call (B:/~BUN/root/src/entrypoints/cli.js:4509:7632)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-12T17:26:18.453Z"},{"error":"MaxFileReadTokenExceededError: File content (18292 tokens) exceeds maximum allowed tokens (10000). 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 KO_ (B:/~BUN/root/src/entrypoints/cli.js:4500:12874)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-12T17:26:58.317Z"},{"error":"Error: ENOENT: no such file or directory, unlink 'C:\Users\Admin\AppData\Local\Temp\claude\C--Users-Admin-OneDrive-Obsidian-Daily-Vault\2b169b45-f6c6-4157-9e05-b275882e8dc7\tasks\a385b75565d423db9.output'\n at async <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:7823:299)","timestamp":"2026-04-12T17:33:45.330Z"}]

TL;DR

Check file paths and permissions to resolve directory and file access errors.

Guidance

• Verify that the application has the necessary permissions to read and write files in the specified directories, such as C:\\Users\\Admin\\OneDrive\\Obsidian\\Daily Vault\\Chief of Staff\\Session Logs.
• Check that the file paths are correct and the files exist, as errors indicate issues with file access, such as ENOENT: no such file or directory.
• Consider using the offset and limit parameters to read specific portions of large files, as the MaxFileReadTokenExceededError suggests that the file content exceeds the maximum allowed tokens.
• Review the current working directory and ensure it is set correctly, as some errors reference the current working directory.

Example

No specific code example is provided, as the issue seems to be related to file system access and permissions rather than code syntax.

Notes

The errors suggest issues with file system access, permissions, and large file handling. Resolving these issues may require adjustments to the application's configuration, file system permissions, or handling of large files.

Recommendation

Apply workaround: Adjust file paths, permissions, and large file handling to resolve the errors, as the issue seems to be related to environment and configuration rather than a version-specific bug.