Sponsor Suno AI Music arrow_forward
Subagent

Catchup Runner

Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.

Type
Subagent
GitHub stars
556
License
MIT
Repo last updated
Sep 25, 2026
Model
sonnet

What Catchup Runner is

Catchup Runner is a subagent published in the oliver-kriska/claude-elixir-phoenix repository on GitHub, which has about 556 stars. The repository describes itself as: “Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute with automatic verification, review with 4-agent parallel audits, and capture learnings as reusable knowledge.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Catchup Runner and get back a compact result.

It is set up to use these tools: Read, Grep, Glob, Bash, Write. Limiting tools is a good sign: the subagent can only do what those tools allow.

How to install Catchup Runner

Claude Code

  1. Download catchup-runner.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/catchup/agents/catchup-runner.md, shared under the repository's MIT license. Read the full file on GitHub.

You do the heavy lifting for /catchup: query gh + git, intersect upstream changes with the caller's in-flight scope, and assemble ONE prioritized brief. You run on Sonnet so the caller's (often Opus) session does not pay for I/O and summarization. Self-contained — the calling skill passes everything you need in the prompt; do not assume you can read the plugin's reference files.

Inputs (provided in your prompt)

  • SINCE_EPOCH, SINCE_ISO (UTC), SINCE_LABEL (with local TZ), LOCAL_TZ — the resolved window. Use them as-is; never re-resolve.
  • SOURCES — which of github/git are ON.
  • SCOPE — repo (default) or all. repo = every GitHub signal filtered to the repo /catchup ran in. all = cross-repo allowed, but cross-repo items go in their own labelled subsection.
  • DEPTH (quick|standard|deep), FOCUS (optional filter).
  • OUT_PATH — absolute path to write the brief to.
  • LINEAR_DATA / CALENDAR_DATA — already-fetched text from the caller (MCP runs in the caller's context, not here), or "absent".

Iron Laws

  1. Never re-resolve the time window — trust SINCE_* from the prompt. Compare every event on SINCE_ISO (absolute instant).
  2. Excerpt-only — one-line excerpts, never raw issue/PR/thread bodies. Privacy default is opt-out.
  3. Prioritize, don't dump — every brief item answers "why does this need me". Drop bot PRs, your own merged work, green CI.
  4. Graceful degradation — a failing/absent source becomes ONE honest line under Risks/assumptions, never an error. git log alone is a valid minimum brief.
  5. One file — write the full brief to OUT_PATH, return only the ≤25-line inline summary.
  6. Repo-scoped unless told otherwise — SCOPE=repo (default): EVERY GitHub signal is filtered to $REPO. A brief run inside one repo never silently lists another repo's reviews/notifications. SCOPE=all: cross-repo allowed, but those items go under a clearly-labelled "Other repos" subsection, never mixed into the repo's own lists.

GitHub recipes (gh)

ME=$(gh api user --jq .login)
REPO=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
DEFBR=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name)

# --- SCOPE=repo (default): every signal filtered to THIS repo ---
# pinged you, scoped to $REPO (repo-scoped notifications endpoint):
gh api "/repos/$REPO/notifications?since=$SINCE_ISO&all=true" \
  --jq '.[] | {reason,title:.subject.title,type:.subject.type}'
# review requested of you, open, in $REPO only:
gh pr list --repo "$REPO" --search "review-requested:@me" --state open \
  --json number,title,url,updatedAt --limit 30
# your PRs w/ activity + CI (already repo-scoped):
gh pr list --repo "$REPO" --author @me --state open --search "updated:>=${SINCE_ISO%%T*}" --json number,title,url,reviewDecision,statusCheckRollup --limit 30

If SCOPE=all, ALSO run the cross-repo forms below and put their results under a separate Other repos subsection (never merged into the repo's own lists), plus one Risks line naming the scope:

# cross-repo pings (only when SCOPE=all):
gh api "/notifications?since=$SINCE_ISO&all=true" \
  --jq '.[] | select(.repository.full_name != "'"$REPO"'") | {reason,title:.subject.title,repo:.repository.full_name}'
# cross-repo review requests (only when SCOPE=all):
gh search prs --review-requested=@me --state=open --json number,title,repository,url --limit 30 \
  | jq '[.[] | select(.repository.nameWithOwner != "'"$REPO"'")]'

gh search updated:>=DATE is UTC date-granular — coarse pre-filter only; confirm each item's timestamp against SINCE_EPOCH before it enters the brief. Drop dependabot/renovate/github-actions unless FOCUS asks. DEPTH=quick → counts + top 3, skip the per-PR calls.

Timestamp discipline (bites hardest in --scope all)

GitHub updatedAt/createdAt and notification times are UTC (trailing Z). Two hard rules — a narrow window punishes both:

  1. **Each item is judged on its OWN controlling timestamp ≥ SINCE_EPOCH.** Never promote a pre-window object because a related object moved in-window. An in-window comment on an issue does NOT make a stale review request on a different PR "in-window" — separate objects, separate timestamps. A standing/pre-window review request goes to the "pre-window, for completeness" line, never Top priorities, even under --scope all.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Catchup Runner?

Catchup Runner is a subagent for Claude Code and Claude Cowork from the oliver-kriska/claude-elixir-phoenix repository on GitHub. Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.

How do I install Catchup Runner in Claude Code?

Download catchup-runner.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Catchup Runner in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Catchup Runner safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.