The desktop app is the web app in a window, plus Link: it keeps a folder on your computer in step with a project.
Pick a folder. It joins the open project, or becomes a new one named for the folder. runlog link does the same from a terminal; either way the folder shows in both.
SeeThe status line reads Linked after the first sync. Ask something only that folder answers; the source opens the file.
Codebases and document folders both work. Code is read function by function, so answers cite lines. A git repository is read with its branch; nested clones and submodules are read through, each under its own .gitignore.
Secrets (.env, keys, credentials), files past the size limit, links out of the folder and whatever .gitignore names are skipped; the output names each. The link lives in .runlog/, which holds no secret and which git never sees.
A moved folder keeps its project. A copy of a linked folder is refused until you link the copy itself. runlog unlink ends the link; your files stay.
Linked folders do not nest. Your plan sets how many you link: pricing.
Not yet: living in the tray, and the coding loop in a window of its own.