@soleone/factory 0.2.0 → 0.2.2

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 CHANGED
@@ -11,18 +11,22 @@ Needs node 22+, git, [workwork](https://github.com/Soleone/workwork) with `--jso
11
11
 
12
12
  ## How it works
13
13
 
14
- - **Repos** are yours on GitHub, cloned under `$SRC`, which is where workwork looks. The folder button right of the tabs lists the ones you haven't cloned yet, newest first, and clones one into a folder of `$SRC` you pick.
14
+ - **Repos** are yours on GitHub, cloned under `$SRC`, which is where workwork looks. In the Candidates tab, choose **Clone project...** from the repo dropdown to see the ones you haven't cloned yet, newest first, and clone one directly into `$SRC`.
15
15
  - **Jobs** are workwork candidates in the queue. Your picks always go first, in the order you give them; auto jobs follow. A job can name its agent, model and effort. Once an agent has started a job, the job stays with that agent.
16
16
  - **Auto mode** only fills the queue: while the factory is on, it keeps up to 5 of its jobs per agent queued, cheapest attention first, with repos taking turns. It never re-queues a candidate that already had a job. You can limit it to some levels and plays.
17
17
  - **The factory** is what works the queue, one worker per agent. With nothing to do it waits, and it picks up new jobs within seconds. Turning it on starts a **run** with its own agents, models, efforts, limit and end time, defaulting to the settings.
18
18
  - **Limits:** a limit of 1 (the default) stops an agent at its first usage-limit hit, so only the current allowance gets used. A limit of 2 waits for one reset and stops at the second hit. "None" always waits for the reset, which it logs. Once every agent has stopped, the factory turns itself off. Three quick failures in a row also count as a limit hit, so a broken login can't burn through the queue.
19
19
  - **Failures:** a failed or timed-out job gets one more try by the same agent. After that it waits for you to retry it.
20
+ - **Agents report back** through the CLI, which factory names in each prompt: `note` for what's worth knowing later, `result` for a summary with a confidence, follow-up tasks and the PR link, and `ask` for the rare decision only you can make; the prompt tells agents to decide everything else themselves and note the call. A job whose agent asked waits for your answer, on the page or with `factory answer`. Then it goes back in the queue, and the next attempt gets the earlier notes, your answer and the branch with the earlier work. Retries get the same.
21
+ - **Jobs can wait on each other:** `--after <job>` holds one until the other is done, and drops it if the other fails or is removed (a retry brings it back). **Review with** queues a review of a job's PR by another agent, which posts its findings as a PR comment.
20
22
 
21
23
  ## Reviewing results
22
24
 
25
+ Results waiting for your answer come first under **Waiting for you**; a dot marks those that ended since you last looked. **Activity** lists everything that happened, newest first, with what the agents said. The tab, filter and an opened job stay in the URL, so a link opens the same view.
26
+
23
27
  Each result links the PR or issue the agent opened. From the page you can read a PR's description and diff, merge it, rebase it onto its base when GitHub reports conflicts, or close it. Rebasing never guesses: if git stops on a conflict, nothing is pushed and the page lists the files.
24
28
 
25
- **Merge train:** select several results and merge them in one go. PRs merge one after another per repo, since each merge moves the base under the next one; repos go in parallel. The train waits for checks, rebases a PR that conflicts, and skips one it can't merge, with the reason. When a rebase stops on real conflicts, a job to resolve them goes to the front of the queue, so an agent picks it up on the next run.
29
+ **Merge train:** select several results and merge them in one go. PRs merge one after another per repo, since each merge moves the base under the next one; repos go in parallel. The train waits for checks, rebases a PR that conflicts, and skips one it can't merge, with the reason. What it did with each PR shows on the job and in Activity. When a rebase stops on real conflicts, a job to resolve them goes to the front of the queue, so an agent picks it up on the next run.
26
30
 
27
31
  ## Live Agent
28
32
 
@@ -38,8 +42,11 @@ The page and the CLI do the same things on the same state; `serve` is only an in
38
42
  factory start [run options] # turn on, in the background (factory run: in the foreground)
39
43
  factory stop # turn off; jobs in progress go back to the queue
40
44
  factory status # on or off, what each agent does, the queue
41
- factory add <id>... [--repo DIR] [--agent NAME] [--model M] [--effort E]
42
- factory remove <job> | retry <job>
45
+ factory add <id>... [--repo DIR] [--agent NAME] [--model M] [--effort E] [--after JOB]
46
+ factory remove <job> | retry <job> | answer <job> "<text>"
47
+ factory review <job> --agent pi # another agent reviews the job's PR once it's done
48
+ factory wait <job> [--timeout MIN] # block until it's done, failed or waiting for you
49
+ factory tail # follow every job event, one line each
43
50
  factory auto on|off
44
51
  factory report [--all] # the last run (or every run): outcome, agent, PR/issue link or log
45
52
  factory serve [--port 7040] [--host 127.0.0.1]