Keeping a repo current

The autopilot is a workflow in your GitHub Actions. lurq supplies the evidence — what you are behind on, and which of the symbols an upgrade removes your code actually references — and your own runner does the work.

Set up (about two minutes)

1. Sign in and get a key: npx lurqrun setup
2. Connect repositories: install the GitHub app from Repositories and pick the repos.
3. Turn it on everywhere, in one command:

# gh must be signed in, with the workflow scope: gh auth refresh -s workflow
npx lurqrun autopilot init --repo owner/api owner/web owner/worker

That sets the LURQ_API_KEY secret, commits the workflow and starts the first run in every repository you name, with no clone and no merge per repo. A protected default branch gets a pull request instead; --pr asks for one everywhere.

Or skip the typing: turn autopilot on in the dashboard and the setup step appears right under the switch. Copy setup prompt hands your agent (Claude Code, Cursor, anything with a terminal) the whole job for every armed repository that has not run yet, with a fresh key in it.

Every one of those writes is made by your own gh login. lurq's GitHub app cannot write a byte to your repository, so what grants write access is a commit you made and can revert.

Three modes

A newly armed repo gets fix. It is the mode that cannot fail for want of a credential, and it still opens pull requests — with the call sites already migrated, which is more than a version bump.

Change the mode on the repository page. Each run reads the setting when it starts, so it governs repos that already installed the workflow; only a file committed before that behaviour existed keeps its own baked-in mode.

Repository secrets

LURQ_API_KEY is required. It lets the workflow ask which upgrades are outstanding. Create one under API keys in the dashboard.

For pr mode only, add one of these:

# Already on Claude Pro, Max, Team or Enterprise:
claude setup-token

That prints a token to the terminal and stores it nowhere — copy it before you close the window, and paste it into a repository secret named CLAUDE_CODE_OAUTH_TOKEN. Anthropic documents this as the mechanism for CI, where an interactive browser login is not available.

ANTHROPIC_API_KEY from the Anthropic console works instead, and bills per token. The action also supports Bedrock, Vertex and Microsoft Foundry through workload identity federation, which stores no secret in the repository at all; the generated workflow does not wire those up, so that needs an edit to the file.

Setting both is safe: an unset secret arrives as an empty string, which the action treats as absent.

Let an agent do it

The dashboard's copy for agent button on a repository page gives your coding agent the whole job with that repo's own workflow file already in it. If you would rather start from here, paste this and fill in the repo name:

Set up lurq's dependency autopilot on <owner/repo>.

1. Ask me for a lurq API key — I create it at https://www.lurq.run/dashboard/keys.
   Never print it back to me, never write it to a file, never commit it.
2. Set it as a repository secret, reading the value from stdin so it stays out of
   my shell history:
      gh secret set LURQ_API_KEY --repo <owner/repo>
3. Get the workflow file: open the repository on https://www.lurq.run/dashboard/repos,
   use "copy file", and write it to .github/workflows/lurq-upgrade.yml exactly as
   given. Do not reformat it, do not change the cron, and do not touch the
   permissions block — that block is the trust boundary and it is deliberately
   minimal.
4. Show me the diff and stop. Do not push: committing this file is what grants
   write access to my repository, and I want to read it first.
5. Only if I say I want pr mode, ask which Anthropic credential I want and set it
   the same way as step 2 — CLAUDE_CODE_OAUTH_TOKEN from `claude setup-token`
   (Pro/Max, expires after one year with no warning) or ANTHROPIC_API_KEY from the
   Anthropic console (does not expire). comment and fix modes need neither.

Then tell me in one line what you set and what is left for me to do.

The per-repo version from the dashboard is better where you have the choice: it carries the rendered file, so the agent does not have to fetch anything, and it already knows which mode the repo is set to.

When it runs

Weekly by default, at 06:00 UTC on Monday. A repo whose policy scope is security runs daily instead, because a weekly schedule can mean seven days sitting on a known advisory.

You can also start a run by hand from the Actions tab, and lurq starts one for you when a dependency you declare ships a new major — so a breaking release reaches you the day it lands rather than up to six days later.

What it can and cannot touch

Read the permissions: block at the top of the file first; it is the whole trust model.

• lurq's GitHub app is read-only on your code. It can read your manifests and start this workflow. It cannot write to your repository, change this file, or set a repository variable.
• Every commit, branch and pull request is made by the workflow's own GITHUB_TOKEN, scoped to that one repo, limited to what the file declares.
• The agent's tool allowlist has no git and no network tool. It edits files; the workflow does version control. A prompt injection in a changelog cannot push a branch.
• Nothing lands on your default branch. Auto-merge is off unless you opt in, and it defers to your own required checks.

Turning the whole thing off is git rm .github/workflows/lurq-upgrade.yml.

If it runs but never opens anything

The dashboard flags this on the repositories list as analysing only. Two causes, and the mode tells you which:

• Set to pr — most likely the Anthropic credential is missing or the OAuth token has expired. The run reports its analysis before the credential check, so you see a completed analysis and a failed job. Check the secret first.
• Set to fix — no credential is involved, so the workflow file is the problem: it predates lurq reading the mode at run time, or pins its own. Re-copy it from the repository page.

A repo set to comment that only analyses is not flagged. That is what it was asked to do.