@tamsensedev/runner 0.9.0 → 0.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -0
- package/dist/cli.js +628 -298
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -45,5 +45,6 @@ Options:
|
|
|
45
45
|
- Clones the task's repositories into `~/.tamsense/repos` and works in `~/.tamsense/work`.
|
|
46
46
|
- 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.
|
|
47
47
|
- Gets a short-lived GitHub token from TAMsense for those repositories only, and pushes the task branch. Pull requests are opened by TAMsense.
|
|
48
|
+
- When a board takes its code from a folder on your computer (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.
|
|
48
49
|
- 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.
|
|
49
50
|
- Never stops processes it did not start.
|