Runlog docs

Start building

A plan buys a weekly allowance, sized for steady work.

Start

Desktop app

The desktop app is the web app in a window (the same screens, the same project, the same threads) with the one surface a browser cannot give: a folder on your disk that stays read. Web or desktop is a choice about that folder, not about features.

01

What it adds

WebDesktopCLIthe CLI does the same from a terminal

Link. One press opens a native folder picker. The folder is bound to the open project, the cost of reading it is quoted before anything uploads, and once you agree the folder is read and then watched: a file that changes on disk is part of the next answer. Watches resume when the app reopens. Behind the button is the shipped runlog binary, so a folder linked here and a folder linked from a terminal are the same kind of thing, and the terminal, the window and the web page show one set of numbers for it.

Everything else (the thread, Ro, uploads, the site, the account) is the web app, loaded live. A change shipped to the web is the desktop’s the moment the window reloads.

SeeAfter Link: the quote, a y/n, then progress by file in the status line, then the documents in the project. Ask something only that folder answers and the citation opens the file.

02

Where it lives

Installed by the one line on the install page: ~/Applications/Runlog.app on macOS, %LOCALAPPDATA%\Programs\Runlog with a Start Menu entry on Windows, ~/.local/opt/runlog with a menu entry on Linux. The folder bindings live in each folder’s own .runlog/, git-ignored; the app keeps only the list of folders it was granted. No key is written to disk: the app mints one from your signed-in session and it lives as long as the process.

03

Unsigned, for now

The build is unsigned while the store signatures clear. Through the install line that costs nothing: a curl-fetched archive carries no quarantine attribute, so macOS opens the app without a Gatekeeper prompt and Windows runs it without SmartScreen. A build fetched through a browser instead meets right-click → Open on macOS and “More info” → “Run anyway” on Windows, once.

04

On the way

Two things the desktop will do that the web cannot: live in the tray with the folders still read and Ro’s opening arriving as a notification, and run the coding loop in its own window. Neither ships today; what ships is the same product, sitting on your desk instead of in a tab. A terminal has the coding loop now: a turn in the terminal.