Life-automation batches that run Anthropic's Claude Code Action as scheduled / manual GitHub Actions, authenticated with a Claude Max subscription (so model usage is covered by your plan — no separate API or Copilot billing).
nix developProvides claude-code, git, gh, jq.
.github/workflows/resolve-conflicts.yml— auto-resolve merge conflicts on your open PRs (daily + manual). Seedocs/resolve-conflicts.md..github/workflows/suggest-issues.yml— open improvement issues on your own repos that you've starred, skipping duplicates (manual only). Seedocs/suggest-issues.md.
Each batch is a normal workflow file — edit the YAML directly and push (no compile step).
| Secret | Purpose |
|---|---|
CLAUDE_CODE_OAUTH_TOKEN |
Claude Max subscription token for the model. Generate locally with claude setup-token (needs Claude Code logged in to your Max account); valid ~1 year. |
GH_TOKEN |
PAT with repo scope on the target repos (forks included). gh/git use it to read your PRs/stars/issues and to clone, push, open PRs, comment, and create issues across repos. |
Set both under Settings → Secrets and variables → Actions.
- GitHub Actions compute: free on this public repo (standard runners).
- Model usage: drawn from your Claude Max subscription via
CLAUDE_CODE_OAUTH_TOKEN— no per-token API charge. Heavy automated runs consume your Max usage limits (5-hour / weekly windows), which can compete with your interactive Claude usage; there is no monetary overage.
Each workflow caps work with --max-turns and a job timeout-minutes. resolve-conflicts
uses --model sonnet (mechanical), suggest-issues uses --model opus (analysis); both
are easy to switch in the workflow's claude_args.
These batches previously ran on gh-aw. gh-aw's Claude engine only accepts an
ANTHROPIC_API_KEY (pay-per-token API) and explicitly ignores CLAUDE_CODE_OAUTH_TOKEN,
so a Claude Max subscription can't be used there. Running the official Claude Code Action
in a plain workflow is the only way to put Max to work in Actions — and it drops gh-aw's
firewall / safe-output / lock-compile machinery we don't need for a trusted, self-owned,
scheduled task.