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
Rework outrider into two paths: engine/App init + no-App setup-local
Replaces the single gh-only `outrider init` with two flows that both end in
the same Outrider Action but differ in who provisions it:
- `outrider init` — thin client over the engine's provision-action endpoints
(REMYX-60 / remyx#337). The Remyx GitHub App provisions the workflow,
secrets, and a bot-authored setup PR server-side; --mode auto|review|off.
New API clients (remyxai/api/github_app.py, integrations.py, and
provision_action/poll/status in interests.py), with App-install and
model-provider preflights.
- `outrider setup-local` — self-provisions with the customer's own gh (no
third-party App, for orgs under security review): sets the repo secrets,
writes the workflow, opens (auto: merges + dispatches) the setup PR, and
enables the repo's Actions-can-create-PRs setting so the built-in
GITHUB_TOKEN opens recommendation PRs. Reversible-first ordering with
branch/PR rollback; Contents-API sha handled on update.
Neither path stores a GitHub token as a repo secret — only REMYX_API_KEY and
ANTHROPIC_API_KEY.
Also: drop the bundled workflow template + package_data (both paths render
inline now); log_api_response treats all 2xx as success (provision-action
returns 202).
Validated live end-to-end against salma-remyx/FFMPerative-test: engine path ->
remyx-ai[bot] recommendation PR; setup-local -> github-actions[bot]
recommendation PR. 50 unit tests across tests/cli/test_outrider_actions.py,
tests/cli/test_outrider_local.py, tests/api/test_outrider_api.py.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Install [Outrider](https://github.com/remyxai/outrider) — the recommendation-driven implementation agent — into a GitHub repository. The command opens a PR that adds `.github/workflows/outrider.yml`, then writes `REMYX_API_KEY` and `ANTHROPIC_API_KEY` to the repo's Actions secrets.
182
+
### Outrider — weekly arXiv → draft PR for your repo
183
+
184
+
[Outrider](https://github.com/remyxai/outrider) is a GitHub Action that, on a weekly schedule, finds the most implementable recent paper for your repository and opens a draft PR wiring it into a real call site. `remyxai outrider` sets it up for you.
185
+
186
+
There are two ways to install it — both end with the same Action running in your repo; they differ in **who provisions it**:
187
+
188
+
||`outrider init`|`outrider setup-local`|
189
+
|---|---|---|
190
+
|**Best for**| Most users | Teams that can't grant a third-party GitHub App yet (e.g. a pending security review) |
191
+
|**How it works**| The **Remyx GitHub App** provisions it server-side; PRs are authored by `remyx-ai[bot]`| The CLI uses **your own `gh`** to provision it; PRs authored by `github-actions[bot]`|
192
+
|**You provide**| The Remyx App installed on the repo (the command links you to it) | An authenticated `gh` with admin on the repo |
193
+
194
+
Either way you'll need a **Remyx API key** (from engine.remyx.ai → Settings) and an **Anthropic API key** (from console.anthropic.com). Set the Remyx key once:
184
195
185
-
* cli command:
186
196
```bash
187
-
# Auto-detect repo from the current git remote
188
-
$ remyxai outrider init --auto-interest
197
+
export REMYXAI_API_KEY=... # from engine.remyx.ai → Settings
-`gh` (GitHub CLI), authenticated with `repo` + `admin:repo_hook` scopes (the latter is what GitHub requires for writing Actions secrets)
199
-
-`REMYXAI_API_KEY` and `ANTHROPIC_API_KEY` in the local environment — these are read once and written to the target repo's Actions secrets via `gh secret set`
210
+
If the Remyx App isn't installed on the repo yet, the command prints an install link and waits. Then the engine provisions the workflow, repo secrets, and a setup PR, and — in the default `auto` mode — merges it and starts the first run. Connect your Anthropic key once on the engine's Integrations page, or pass `--anthropic-key` (or set `ANTHROPIC_API_KEY`) and the CLI connects it for you.
211
+
212
+
`--mode`: `auto` (default — set it up and start the first run), `review` (open the setup PR for you to merge), `off` (just create the research interest).
213
+
214
+
#### Option B — `outrider setup-local` (no GitHub App)
215
+
216
+
For teams that can't install a third-party App yet. The CLI uses your own authenticated `gh` to do everything — nothing new to security-review.
217
+
218
+
```bash
219
+
$ export ANTHROPIC_API_KEY=... # stored as a repo secret by the CLI
Using your `gh` credentials, the CLI sets the `REMYX_API_KEY` + `ANTHROPIC_API_KEY` repo secrets, writes `.github/workflows/outrider.yml`, opens a setup PR, and — in `auto` mode — merges it and dispatches the first run. So the Action can open its recommendation PRs, the CLI enables the repo's *"Allow GitHub Actions to create and approve pull requests"* setting; the Action then uses the repo's built-in `GITHUB_TOKEN` (no GitHub token is stored as a secret — only `REMYX_API_KEY` and `ANTHROPIC_API_KEY`).
225
+
226
+
Requires `gh` authenticated (`gh auth login`, or `$GITHUB_TOKEN` with `repo` + `workflow` scopes) and admin on the target repo.
227
+
228
+
#### Common options
229
+
230
+
-`--repo owner/name` — target repo (or a GitHub URL); defaults to the current directory's git remote.
231
+
-`--interest <uuid>` / `--auto-interest` — use an existing research interest, or create one from the repo.
232
+
-`--mode auto|review` (`init` also has `off`) — how far to take setup.
233
+
-`--dry-run` — print the plan (and, for `setup-local`, the rendered workflow) and exit without making changes.
234
+
-`-y` / `--yes` — skip the confirmation prompt.
235
+
236
+
Preview either path safely before committing to it:
**Credential model (v1):**the operator's own`REMYXAI_API_KEY` is copied into the target repo's Actions secrets. Anyone with write access to the repo's workflows can therefore consume Remyx credits attributed to that key. This is acceptable for repos you control end-to-end; for shared or third-party repos, prefer provisioning a scoped key in the Remyx dashboard before running `outrider init`. A first-class scoped-token flow is tracked in REMYX-76.
242
+
**A note on credentials:**with `setup-local`, your`REMYXAI_API_KEY` is stored as the repo's `REMYX_API_KEY` secret so the Action can fetch recommendations — anyone with write access to the repo's workflows can consume Remyx credits on that key, so use it on repos you control. With `outrider init`, the Remyx App provisions a scoped key for you. In both paths your Anthropic key is stored as a repo secret to run the agent.
0 commit comments