The distinguishing choices here are small and practical: copies and moves take a backup first, deletes run behind safety checks, and named collections give an assistant a way to hold on to a set of files it keeps coming back to. On Windows it reaches further than most, into drives and special folders. The author's own known-issues list, which names deletion as unreliable, is worth taking at face value before letting an assistant remove anything.
A local file-system server: reading and writing file contents, copying and moving with a backup taken first, deleting behind safety checks, searching by name pattern, listing a directory or walking it as a tree, and reporting sizes and timestamps. It also answers questions about the machine itself — operating system, CPU, memory, disk usage, and a directory's file count and total size. Depth differs by platform: Windows gets drive listing, special-folder access and detailed system information through pywin32 and WMI, while macOS and Linux get the file and directory operations with basic system information. The repository is archived, and its own known-issues list records that file deletion and drive listing are both unreliable.
- File contents read and written, and files copied, moved or deleted, with a backup taken before destructive operations
- A file's own record — size, creation time, modification time
- Files found by name pattern, and directories found the same way
- A directory listed, created or deleted, or walked recursively as a tree
- Named collections that group related files, stored in a location you choose
- The machine's operating system, CPU, memory and disk usage, and a directory's file count and total size