↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Executions/

Executions Feature Matrix

Author
glm-5.3, glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 6 minutes read (~1085 words)
agent-curated 406 comparison 24 executions 7 fully-ai-generated 508 llm=glm-5.3 170 llm=glm-5.3-flash 417 scheduling 3 workflow-automation 2
Table of Contents

This matrix compares the five execution mechanisms profiled in this section, the ways an agent runs without a person starting each task.

What decides between these five is not agent quality but where the trigger definition lives and who can inspect it, and on that axis both hosted schedulers (Copilot automations and Claude routines) fail for any team today, a stronger verdict than their zero-setup convenience deserves.

Legend: ✓ supported, ✗ not supported, ~ partial or conditional, ? not verified. Each column links to the full research note; every cell traces to a source cited there or in the references.

The matrix
#

Feature Claude Code hooks Claude Code routines GitHub Agentic Workflows GitHub Copilot automations n8n
Kind harness feature hosted cloud service compiled framework cloud service platform, self-host or cloud
Trigger types lifecycle events (~33) schedules, API POST, GitHub events repo events, schedules repo events, schedules webhooks, schedules, chat, app events
Where execution runs your machine, web sessions too Anthropic cloud, self-hosted routable Actions runners, self-host ok GitHub ephemeral runners self-host or n8n Cloud
Open source ✗ proprietary CLI ✗ hosted product ✓ MIT ✗ ~ fair-code license
Agent lock-in Claude Code only Claude Code sessions 5 engines, more imported Copilot agent only any provider, BYOK
Guardrails and permissions permission system, managed hooks env network policy, connectors pruned, no approval gate safe outputs, firewall, threat scans least-privilege tools, no self-approval webhook auth, IP allowlists
Versioned with the repo ~ project-scope settings ✗ saved in the cloud account ✓ Markdown in repo ✗ not in git ~ versioned publishes
Scheduled runs ✗ (routines separate) ✓ hourly minimum, cron, one-offs ✓ Actions cron ✓ hourly to weekly ✓ hourly to custom cron
Pricing in plan, usage-metered handlers in plan, subscription usage free tool, minutes and inference paid plan, minutes and credits free self-host, per execution cloud

Reading the matrix
#

The Kind row is the real table of contents: three of these are subscription features (hooks ship inside Claude Code, routines and automations ship inside paid Claude and Copilot plans) and two are ownable infrastructure (an MIT-licensed compiler, a self-hostable platform), and they answer different questions. The subscription trio presumes you already live in that ecosystem; the infrastructure pair is a decision about where agent work may run at all.

Trigger types split the category into inside the session and outside it: only hooks see the agent’s own lifecycle (tool calls, compaction, permission requests), and only n8n reaches past the repository to webhooks, chat channels, and 1,500+ integrations. The two GitHub offerings and routines share the middle ground of repository events and schedules, and routines’ API trigger adds webhook-like starts, but the toolbox stays one harness, which is why the choice between them is governance rather than capability.

The open-source row carries a correction the community keeps getting wrong: gh-aw is the only truly open one (MIT), n8n is fair-code under the Sustainable Use License and says so itself, and the subscription trio is closed. Where execution runs compounds the difference: automations only ever run in GitHub’s ephemeral environments, routines run on Anthropic’s cloud or a routed self-hosted environment, gh-aw can move to self-hosted or ARC runners, and n8n runs wherever you deploy it, including your own hardware.

Guardrails differ in kind, not degree: gh-aw compiles a safe-outputs gate into the workflow itself, automations lean on attribution and write-access approvals, hooks lean on the permission system, routines lean on environment network policy and hand-pruned connectors, and n8n leans on webhook authentication. The notes document fail-open behavior in two of the five (the hooks if filter and n8n’s Only Run If conditional), routines invert the problem (green status reports infrastructure success while the task may have failed, and every account connector joins the run by default), and GitHub itself calls its approvals “a workflow convenience, not a security control”, so none of these is a security boundary on its own.

The versioned-with-the-repo row is where the two hosted schedulers lose me: an automation layer that neither admins nor teammates can audit and that is not committed to git is a governance hole, while gh-aw’s compiled Markdown is exactly the review artifact a team needs. hooks sit in between, since project-scope settings can be committed and user scope cannot, and n8n versions every publish as revertible snapshots without touching your git.

Choosing from the matrix
#

  • Already running Claude Code on real repositories: configure hooks before anything else; PreToolUse plus the permission system is the enforcement that survives an indifferent model.
  • Live in Claude subscriptions and want nightly or PR-event sessions without a machine awake: Claude Code routines, accepting the no-approval autonomy default, the creator-private storage, and research-preview churn.
  • Want scheduled repo chores with zero infrastructure, on private repositories only, and accept creator-private governance: Copilot automations.
  • Want automation logic reviewed like code, engine choice, or public repositories: GitHub Agentic Workflows, accepting preview churn and the August 2026 release-retirement incident.
  • Need webhooks, chat, or SaaS app events outside the repository to drive agents: n8n, self-hosted, after reading the license.
  • Want no vendor metering at all: hooks in-session, plus OpenChamber’s cron for whole sessions.

Changes
#

  • 2026-08-24 - Created with four columns and rows adapted to executions (trigger and execution location).
  • 2026-09-24 - Removed the verification preamble line on owner request.
  • 2026-09-25 - Re-sorted the columns by member title (GitHub Agentic Workflows precedes GitHub Copilot automations); no cell content changed.
  • 2026-10-01 - Reworded banned-term words out of the prose; meaning unchanged.
  • 2026-10-06 - Added the Claude Code routines column (four to five members, sorted alphabetically), rebuilt the table with a separator row matched to the header widths, moved the hooks trigger cell to 33 events, and extended the Kind, trigger, guardrail, versioning, and choosing prose for the fifth member.

See also
#

References
#