Knock vs GitHub
Side-by-side trajectory, velocity, and editorial themes.
Knock is rewiring notifications infrastructure to be configured by agents, not just developers.
Knock is methodically rebuilding its primitives — audiences, layouts, reusable steps, in-app guides — so they're versioned, environment-promotable, and addressable from an agent in addition to the dashboard and CLI. The recent run shows a clear pattern: each new feature ships with at least one agent-accessible path. Underneath, the engineering surface is also tightening, with reusable request input schemas making composability less guesswork.
Knock is positioning its platform as agent-buildable messaging infrastructure rather than just a developer SDK. Skills, dynamic audiences, and schema'd reusable steps are the building blocks of a future where a product team agent (or Knock's own) can spin up an entire notification flow without a developer touching code. The Layouts 2.0 refresh and Guides toolbar work in parallel to harden the human surfaces that remain.
Expect Knock to publish a more opinionated agent surface — likely an MCP-style server or an in-product agent that orchestrates skills against dynamic audiences. The reusable-input-schemas release is the kind of plumbing that precedes a 'build a workflow from a prompt' demo, so a higher-level natural-language workflow composer is the most probable next move.
GitHub is collapsing Copilot from chat into autonomous task execution across the platform.
Copilot has graduated from a code-completion sidebar into a multi-model agent woven through GitHub's surface area — code review, Actions, issues, security. Recent releases shift model selection from user choice toward automated routing, add semantic understanding of the issues corpus, and extend the cloud agent's reach to fix failing CI jobs and apply review feedback in one click. The model lineup keeps widening (Gemini 3.5 Flash GA), but the bigger move is hiding that complexity behind verbs like 'Fix with Copilot'.
GitHub is moving the user one rung up the abstraction ladder: instead of picking models, prompts, or scopes, you delegate jobs and Copilot orchestrates underneath. Multi-vendor model support signals comfort with using the best provider per task rather than betting on one model house, while a deliberate verb consolidation ('Fix with Copilot') unifies what used to be feature-specific buttons. Auxiliary work — telemetry URL stabilization, OIDC expansion, GHAS trial flows — keeps the platform plumbing in step with that agentic push.
Expect Copilot to claim more of the actual git workflow next: autonomous PR drafting from issue context, agent-led triage built on the new semantic issues index, and broader cloud-agent coverage of the Actions and security surfaces where one-click fixes already exist. Model-choice UI is likely to keep shrinking as the auto-router takes over.
See more alternatives to Knock →
See more alternatives to GitHub →