loopctl-mcp-server 2.104.0 → 2.104.1
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 +2 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -504,6 +504,8 @@ The generated-tool count per tenant is bounded by the per-tenant entity cap.
|
|
|
504
504
|
|
|
505
505
|
Enroll the dev machines that run the agent delivery loop, see which are connected (issue #809), bind the repositories whose issues feed it, place work on them and recover a story a runner would not take. The `runner_*` and `intake_source_*` tools require `LOOPCTL_USER_KEY`, and their writes additionally require a human-anchored tenant. The delivery-loop verbs below do NOT share one key — each row names the key its endpoint's gate demands, and a higher-privileged key does not substitute for an `exact_role` one.
|
|
506
506
|
|
|
507
|
+
The order to wire it up, the stage machine these tools move a story through, and every operator setting the loop reads are in loopctl's [`docs/agent-delivery-loop.md`](https://github.com/mkreyman/loopctl/blob/master/docs/agent-delivery-loop.md). In short: `runner_enroll`, `intake_source_enroll` plus the GitHub webhook, confirm the machine in `runner_pool`, `place_dispatch` one story and watch it with `story_stage`, then turn on the unattended driver server-side.
|
|
508
|
+
|
|
507
509
|
**A loop with no intake source has no input.** `intake_source_enroll` is the step that points a GitHub repository at loopctl, and the same row is where `place_dispatch` reads `repo` and `base_branch` from — its 409 `no_intake_source` names exactly this. The webhook secret it returns is written to a file and never appears in a tool result; see that row.
|
|
508
510
|
|
|
509
511
|
| Tool | Description |
|