Cloud File Manager

Good to know before installing

Adds a file API to the gateway (dashboard plugin routes under the gateway's existing auth) over the agent's working folders: the configured roots, else terminal.cwd, TERMINAL_CWD or MESSAGING_CWD, else the gateway user's home with its dot-entries hidden. It lists, sorts and searches those folders, reads the files you open or preview (Markdown and .txt files up to 1 MiB in the editor; the first 1 MiB of other code and text files; images and PDFs up to 10 MiB), creates folders, and writes uploads, Drive imports and editor saves (staged as hidden .cfm-* temp files in the destination folder; a name clash keeps both files). It overwrites only an existing .md/.markdown/.txt file you open and explicitly Save in its editor (refused if the file changed since you opened it). It has no delete action: it removes only its own .cfm-* staging files and folders (aborted ones, and stale ones over a day old) and, when an upload or import fails to publish, the empty file it had reserved for it. It never follows links out of those folders, and its file API never exposes the agent's Hermes home apart from a working folder set inside it (roots, terminal.cwd, or a workspace/ folder it creates when the wo

From the plugin's catalog listing.