Ask your files

WebDesktopCLI

Open Explore and drop files, or a whole folder. Every file lists at once with a moving bar and a phrase saying what is happening to it: reading, resolving, done. A CSV becomes rows with its columns as fields; a PDF page, a sheet range, a call recording each keep their place. In the thread beside Explore, ask a question only those files answer.

SeeEach file reads Done within minutes and the findings panel fills as files finish. The answer carries source chips; each chip opens the finding, and the finding names the file. Every assistant message carries chips, not only the first.

WebDesktopCLIa folder that stays read

Press Link, pick a folder. The cost of reading it is quoted before anything uploads; agree, and the folder is read, then watched while the app is open. Edit a document and only that document re-reads; delete one and it stops being cited. What the desktop app adds.

WebDesktopCLI

runlog link ~/Clients            # binds the folder to a project; writes .runlog/, asks nothing else
runlog sync                      # quotes the cost, waits for y, reads the folder, reports the percentage as it goes
runlog watch                     # keeps sending changes as they happen

SeeBefore anything uploads, one line quoting the reading against your weekly allowance and a y/n. Then progress by file and a count of what was read. The percentage it reports is of the tightest rolling window: when the window fills up the next file is not started, and an in-flight file runs to completion. Run sync again with nothing changed and it says so in under a second, with no quote.

.env, keys, anything your .gitignore names, files over the size ceiling and symlinks out of the folder are skipped by name in the output, with how to include one deliberately. The binding lives in .runlog/, which hides itself from git and carries no secret: a copy of it on another machine grants nothing. A folder that moves resolves to the same project; a copy of a folder whose original is still bound is refused, naming the original.

WebDesktopCLI

Export your ChatGPT or Claude history (each vendor’s settings has an export control; the zip arrives by email) and drop the zip on Explore. It lands as your own documents, one per conversation, under .runlog/Connection/ChatGPT or .runlog/Connection/Claude, named by date and title. A pasted share link lands beside them. Ask a question you once asked the other assistant.

SeeA line saying how many conversations landed; dropping the same export twice reports every conversation as already present. The answer cites the imported conversation and the citation opens it at the turn: you did not start over.