Filesystem capabilities
Newt uses the same pane interface for every filesystem, but each backend exposes the operations its storage model can support.
| Filesystem | Read | Write | Rename | Links | Metadata | Trash | Free space |
|---|---|---|---|---|---|---|---|
| Local | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| S3 | ✓ | ✓ | ✓¹ | — | Object metadata | — | — |
| SFTP | ✓ | ✓ | ✓ | ✓ | Unix metadata | — | — |
| Remote agent | ✓ | ✓ | ✓ | Target-dependent | Target-dependent | Target-dependent | Target-dependent |
| Archive | ✓ | — | — | Read existing² | Read existing | — | — |
| Disc image | ✓ | — | — | Read existing² | Read existing | — | — |
| Search results | Source-dependent | Source-dependent | Source-dependent | Source-dependent | Source-dependent | Source-dependent | Source-dependent |
¹ S3 renames are implemented as copy followed by delete because object storage does not have a native rename operation.
² Links stored in supported archive and image formats are resolved while browsing; the read-only mount cannot create new ones.
Local and remote-agent filesystems
Section titled “Local and remote-agent filesystems”The local filesystem provides full platform-native access, directory watching, ownership and permission changes where supported by the operating system, and free-space reporting.
A remote-agent mount uses the target’s local filesystem through SSH, Docker, Podman, Kubernetes, or a custom transport. Its capabilities therefore follow the target filesystem. A client-local mount exposed inside a full remote session also provides normal read and write operations through Newt.
S3 supports object reads, multipart writes, copies, prefix creation, deletion, and metadata. Directories are simulated from /-separated object keys. It has no trash, Unix links, permissions, or filesystem statistics. Deletes are permanent after confirmation.
SFTP supports ordinary reads and writes, directory creation, rename, deletion, links, and common Unix metadata through the server. It does not provide trash or filesystem free-space statistics to Newt. Deletes are permanent after confirmation.
Read-only locations
Section titled “Read-only locations”Archives and disc images are read-only. Files can be viewed or copied out to a writable location, but cannot be modified in place.
Search results are aliases for the original entries rather than copies. Operations act on each source file and inherit the source filesystem’s capabilities.
Refresh
Section titled “Refresh”Local and remote-agent panes refresh when the application regains focus, and local panes also react to filesystem changes. Automatic focus refresh is disabled for S3, SFTP, and archives because their listings may be expensive. Run Refresh File List from the Command Palette when needed.