Scheduled triggers

A trigger is an unattended, scheduled agent run. On a cron cadence it runs /shipeasy:ops:work --pr against your project — burning down the feedback queue (bugs, feature requests, auto-filed error/alert tickets) one item at a time, committing each fix on its own branch, and opening one PR per item for review. No human in the loop.

Provision it from the CLI:

shipeasy setup triggers
shipeasy setup triggers --platform claude

--platform is one of claude, codex, cursor, copilot, gemini, jules. The command explains the trade, has you pick a platform, then opens the guided setup on the dashboard's Triggers tab preselected to it — the same surface that manages the trigger afterwards. shipeasy setup offers this as an inline step.

Three scheduler tiers

The run is identical everywhere

Whatever the provider, the scheduled run authenticates with a restricted ops key, refreshes the plugin + CLI, and follows the installed ops:work --pr workflow. Mint the key with:

npx -y @shipeasy/cli@latest keys create --type ops

The ops key can read the queue, flip item status, link the PR it opens, and create resources — but never edits or deletes existing ones, and auto-extends its 7-day expiry on each run. A leaked trigger prompt can't compromise the project. Never embed your admin login token.

Tier C — the GitHub Actions shape

For headless providers with no native scheduler, a scheduled Actions workflow is the always-on driver (Gemini shown via the official run-gemini-cli Action — swap the run step for codex exec for Codex):

on:
  schedule:
    - cron: "0 9 * * 1-5" # weekdays 09:00 UTC
  workflow_dispatch:
permissions:
  contents: write
  pull-requests: write
jobs:
  trigger:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: google-github-actions/run-gemini-cli@v0
        env:
          GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
          SHIPEASY_CLI_TOKEN: ${{ secrets.SHIPEASY_OPS_KEY }}
          SHIPEASY_PROJECT_ID: ${{ secrets.SHIPEASY_PROJECT_ID }}
        with:
          prompt: "<trigger prompt>"
          settings: '{ "approval-mode": "yolo" }'

Connector registration — Shipeasy-fired vs. platform-scheduled

A Shipeasy connector (Settings → Triggers, "Trigger now" + event auto-fire) means Shipeasy's own cron fires the run. That backend is a Cloudflare Worker, so it can only fire a provider that exposes (1) a clean HTTP "start a run" endpoint — a plain fetch(), no CLI binary, no local scheduler — and (2) a storable static token.

Four providers clear that bar and are registered as trigger connectors:

• claude — POST …/routines/<id>/fire with a per-routine bearer token.
• cursor — POST https://api.cursor.com/v1/agents with CURSOR_API_KEY + autoCreatePR.
• copilot — a GitHub coding-agent task, via the GitHub connection you already made.
• jules — a Jules session started from its API key.

Each gets a guided flow and a Trigger now button on the dashboard, plus auto-fire on new queue items. codex and gemini are platform-scheduled: they run on their own surface (Codex Automations, or a GitHub Actions schedule: job), so pause, run and inspect them there.