@tamsensedev/runner 0.9.0 → 0.13.0

package/README.md

@@ -18,12 +18,19 @@ It shows a code and opens TAMsense in your browser. Confirm the code there, and
 
 ## Work on your tasks
 
+Open a terminal in your code folder, then start the program there:
+
 ```
+cd <your code folder>
 npx @tamsensedev/runner@latest start
 ```
 
+It looks for code where you started it. If that folder is a git repository, it uses it. If not, it looks one level down, so starting in `C:\code` with `platform` and `wms` inside finds both. It does not look deeper, skips hidden folders and `node_modules`, and does not follow links. Each folder it finds is listed in the terminal (`Found code: platform (C:\code\platform)`) and on the site for this computer. A board whose repositories match a found folder uses it on this computer; a board without code offers it with one click. To add more, start the program from another code folder, or add a path in Board settings > Code.
+
 The computer takes the steps you own on the task board (questions and specs, code, review, tests) and works on them until you press Ctrl+C. You see everything Claude does live in the task chat, and you can message it or stop it there.
 
+When a task waits for something slow, such as a local stand that takes half an hour to start, the agent can set up a schedule: a short check on a timer, run by a cheap model on this computer for free. Each check writes one line in the task chat. While the computer sleeps or the program is stopped, its checks are skipped, not saved for later.
+
 ## Other commands
 
 ```
@@ -45,5 +52,6 @@ Options:
 - Clones the task's repositories into `~/.tamsense/repos` and works in `~/.tamsense/work`.
 - Installs a headless browser for interface checks into `~/.tamsense` when `start` finds none, about 150 MB, without asking. If that fails, it says why and tasks still run without it.
 - Gets a short-lived GitHub token from TAMsense for those repositories only, and pushes the task branch. Pull requests are opened by TAMsense.
+- When a board takes its code from a folder on your computer (found at start, or added in board settings, Code tab), it reads only the git details of that folder to check it. Steps work in a git worktree of it in `~/.tamsense/work` on branch `task/<id>`: your working folder and its current branch stay as they are. If the folder has a remote, it fetches and pushes the task branch with your own git login; it never pushes the main branch. Without a remote the branch stays in the folder and you merge it yourself.
 - Records the browser Claude drives during a task (a replay of each page, and a video when asked) into `~/.tamsense/recordings`, attaches it to the task and deletes the local copy when the step ends. Requests from the tested site to the TAMsense tracker are blocked during these runs, so they never reach your analytics, and so are requests that change data (anything but GET, HEAD and OPTIONS) to addresses outside your computer.
 - Never stops processes it did not start.