@tamsensedev/runner 0.13.0 → 0.18.0

package/LICENSE

@@ -1,5 +1,5 @@
-Copyright (c) 2026 TAMsense. All rights reserved.
-
-This package is provided to TAMsense customers to connect their computers to TAMsense. No license is granted to copy, modify or redistribute it outside that use.
-
-The skills and agents in the `library` folder adapt open source work under their own licenses. See `library/THIRD_PARTY_NOTICES.md`.
+Copyright (c) 2026 TAMsense. All rights reserved.
+
+This package is provided to TAMsense customers to connect their computers to TAMsense. No license is granted to copy, modify or redistribute it outside that use.
+
+The skills and agents in the `library` folder adapt open source work under their own licenses. See `library/THIRD_PARTY_NOTICES.md`.

package/README.md

@@ -1,57 +1,61 @@
-# @tamsensedev/runner
-
-Connects your computer to [TAMsense](https://my.tamsense.com), so the steps of your tasks run in Claude Code on your own machine, on your own Claude subscription.
-
-## Requirements
-
-- Node.js 22 or newer
-- Claude Code, signed in (`claude` works in your terminal)
-- Git
-
-## Connect this computer
-
-```
-npx @tamsensedev/runner@latest login
-```
-
-It shows a code and opens TAMsense in your browser. Confirm the code there, and the computer appears in your account under Computers.
-
-## 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
-
-```
-npx @tamsensedev/runner@latest status            show the connection
-npx @tamsensedev/runner@latest logout            disconnect this computer
-npx @tamsensedev/runner@latest browser           install the headless browser for interface checks
-npx @tamsensedev/runner@latest browser remove    delete that browser
-```
-
-Options:
-
-- `--name <name>` how this computer is called in TAMsense (login)
-- `--server <url>` TAMsense address, default https://my.tamsense.com (login)
-- `--parallel <n>` how many tasks to work on at once (start)
-- `--no-browser` do not install the headless browser for interface checks (start)
-
-## What it does on your computer
-
-- 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.
+# @tamsensedev/runner
+
+Connects your computer to [TAMsense](https://my.tamsense.com), so the steps of your tasks run in Claude Code on your own machine, on your own Claude subscription.
+
+## Requirements
+
+- Node.js 22 or newer
+- Claude Code, signed in (`claude` works in your terminal)
+- Git
+
+## Connect this computer
+
+```
+npx @tamsensedev/runner@latest login
+```
+
+It shows a code and opens TAMsense in your browser. Confirm the code there, and the computer appears in your account under Computers.
+
+## 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 found folder joins the project by itself when one of its agents chose that repository, or when another computer in the project already has it; otherwise the site offers it with one click under this computer in Settings > Account. To add more, start the program from another code folder, or add a path there.
+
+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.
+
+When you write to Sense in a task chat, Sense decides on this computer with the Claude signed in here, for free, next to the tasks it works on. It gets the task as you see it on the site and no files or commands. Questions about analytics or visitor sessions it asks TAMsense cloud, which answers in plain words and charges your AI credits for that answer. The terminal shows one line per answer, `Sense answered on task #12`, never your words. If this computer does not answer in time, the cloud answers instead.
+
+Routines can run here too: a job that repeats on a schedule, such as finding stuck orders every morning. A routine run makes tasks and asks people on TAMsense. When its routine may fix things, every action that changes something goes through the safety rules of the project and waits for a person to allow it, just like a task step. A test run changes nothing and asks nobody.
+
+## Other commands
+
+```
+npx @tamsensedev/runner@latest status            show the connection
+npx @tamsensedev/runner@latest logout            disconnect this computer
+npx @tamsensedev/runner@latest browser           install the headless browser for interface checks
+npx @tamsensedev/runner@latest browser remove    delete that browser
+```
+
+Options:
+
+- `--name <name>` how this computer is called in TAMsense (login)
+- `--server <url>` TAMsense address, default https://my.tamsense.com (login)
+- `--parallel <n>` how many tasks to work on at once (start)
+- `--no-browser` do not install the headless browser for interface checks (start)
+
+## What it does on your computer
+
+- 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 an agent takes its code from a folder on your computer (found at start, or added in Settings > Account under this computer), 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.