You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
outrider CLI: --bulk-repos, --no-cron on setup-local, install-paths docs (REMYX-147) (#43)
Three CLI improvements driven by Wave 1-3 onboarding pain:
- `--bulk-repos PATH` on `outrider init` + `outrider setup-local`: a
TSV-driven loop (`owner/name<TAB>uuid` per row). Per-row errors are
captured and reported in a summary at the end — one failure does not
abort the remaining rows. `--pace SECONDS` tunes inter-row spacing
(default 3s). Mutually exclusive with --repo / --interest /
--auto-interest.
- `--no-cron` on `setup-local`: workflow renders with the schedule
block commented-out (not removed). Re-enable later by uncommenting
three lines — no need to re-run setup-local. Engine-side `init
--no-cron` is not yet wired; deferred to a follow-up that needs
engine cooperation.
- New docs/install-paths.md covers init vs setup-local trade-offs,
the App-install dependency (and what happens if you write the
workflow manually), `--no-cron`, and the `--bulk-repos` workflow.
README gets a one-sentence pointer to the doc.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,6 +134,8 @@ Once Outrider is installed, `remyxai outrider trigger` dispatches an ad-hoc run
134
134
135
135
If the Remyx GitHub App isn't installed on the target repo yet, the command surfaces the install link.
136
136
137
+
For the no-App `setup-local` path, the `--no-cron` switch, and `--bulk-repos` onboarding across many repos at once, see [docs/install-paths.md](docs/install-paths.md).
138
+
137
139
## Command reference
138
140
139
141
Run any command with `--help` for full flag listings and examples.
There are two CLI paths to install Outrider on a target repo, plus a bulk path for onboarding many repos in one shot.
10
+
11
+
12
+
## `outrider init` — the default
13
+
14
+
Drives the Remyx engine to register the **Remyx GitHub App** (`remyx-ai[bot]`) on the target, write the workflow, set the repo's Actions secrets, and open a bot-authored setup PR. In `auto` mode it also merges the PR and fires the first run.
The App is the load-bearing piece. At runtime, the workflow asks the engine to mint a short-lived `remyx-ai[bot]` token so the action's PRs and Issues are authored by the bot — not `github-actions[bot]`. **Without the App installed on the target, that token-mint silently returns empty and the action falls back to the workflow's built-in `GITHUB_TOKEN`** — the run still succeeds but the artifacts are anonymous and skip the convention-pass enrichments that key off the bot author. Always prefer this path when the org can grant the App.
21
+
22
+
If the App isn't installed yet, the command surfaces the install link — accept it once and the engine handles the rest.
23
+
24
+
25
+
## `outrider setup-local` — when the App can't be granted
26
+
27
+
For enterprises that can't grant a third-party App yet (pending security review, restricted org policy):
Uses your own authenticated `gh` CLI to set the repo secrets, write the workflow, and (in `auto` mode) merge the setup PR. No Remyx App, nothing new to security-review. The only Remyx dependency is the `REMYX_API_KEY` the workflow uses at runtime.
34
+
35
+
The action then opens its PRs / Issues with the repo's built-in `GITHUB_TOKEN` (authored by `github-actions[bot]` rather than `remyx-ai[bot]`).
36
+
37
+
### `--no-cron`
38
+
39
+
By default the workflow ships with a scheduled cron at 14:00 UTC Mondays. For trials, cost control, or any "I'll dispatch manually" use case:
The schedule block is rendered commented-out (not removed entirely), so re-enabling later means uncommenting three lines — no need to re-run setup-local.
46
+
47
+
Engine-side `outrider init --no-cron` is not yet supported; for now, prefer `setup-local --no-cron` if you need that knob.
48
+
49
+
50
+
## Don't write the workflow file manually
51
+
52
+
Committing `.github/workflows/outrider.yml` by hand (without one of the two CLI paths above) skips the App-install / secrets-set steps. The action will deploy and run, but:
53
+
54
+
- The bot-token mint silently fails → PRs are `github-actions[bot]`-authored
55
+
- The `REMYX_API_KEY` / `ANTHROPIC_API_KEY` Actions secrets must be set manually
56
+
57
+
If you've already done this and your runs are producing 0 artifacts, run `remyxai outrider init --repo owner/name --interest <uuid>` after the fact — it's idempotent for the secrets-set step and surfaces the App install link if needed.
58
+
59
+
60
+
## `--bulk-repos` — many repos in one shot
61
+
62
+
Onboarding a portfolio of forks or installing across a team's repos:
Per-repo errors are captured and reported at the end — one failure does not abort the remaining rows. Use `--pace SECONDS` to tune the inter-repo pacing (default 3s).
80
+
81
+
`--bulk-repos` is also supported on `setup-local` with the same TSV format.
82
+
83
+
`--bulk-repos` is mutually exclusive with `--repo` / `--interest` / `--auto-interest` (the TSV is the source of truth for the per-row pair).
0 commit comments