{"version":"2.1.55","anchor":"simplified-file-open-operations-for-better-symlink-compatibi","canonical_anchor":"simplified-file-open-operations-for-better-symlink-compatibi","heading":"Simplified file open operations for better symlink compatibility","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.55\/e\/simplified-file-open-operations-for-better-symlink-compatibi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.55","markdown":"### Simplified file open operations for better symlink compatibility\n\nFile operations for log files and session tracking previously used low-level POSIX flags including `O_NOFOLLOW`, which prevents opening files through symbolic links. This has been replaced with standard file mode strings (`\"a\"` for append, `\"w\"` for write). Users whose `~\/.claude` directory or log paths involve symbolic links (e.g., pointing to a different disk or partition) should experience fewer file operation errors.\n\n**Evidence**\n\nRemoval of `O_NOFOLLOW` flag usage \u2014 previously set via `R46.O_NOFOLLOW ?? 0` in the old version; zero occurrences remain in v2.1.55. Affects the log writer class (search for `\"local_bash\"`) and session file creation."}