{"version":"2.1.290","anchor":"linux-fd-anchored-file-ops-list-directories-through-libc-via","canonical_anchor":"linux-fd-anchored-file-ops-list-directories-through-libc-via","heading":"Folder listing on Linux and macOS can return file names that aren't valid text","tier":"notice","area":"File Paths","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/linux-fd-anchored-file-ops-list-directories-through-libc-via","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Folder listing on Linux and macOS can return file names that aren't valid text\n\nOn Linux and macOS, Claude Code can list folders through the system library so unusual file names come back exactly as stored\n\n**Unclear.** It is not clear whether this listing is used anywhere besides removing worktrees.\n\n**What**\n\nOn Linux, Claude Code can now list a folder's contents by calling the system's C library directly. File names come back as raw bytes, so names that are not valid UTF-8 (the usual text encoding) are kept exactly as stored. This only works when Claude Code finds exactly one copy of glibc or musl (the two common Linux C libraries) loaded; otherwise it reports that it cannot. macOS gets a similar way of listing folders.\n\n**Why**\n\nThis lets Claude Code safely remove files whose names are not valid text.\n\n- Area: File Paths\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}