GitHub vs Shortcut for AI agents

GitHubL4Runs on its own

Through every checkpoint. Next: pay without a person

Runs on its own once it holds an existing identity: L4 · Runs on its own. Sign-up itself never got past a block on the signup page, so every later call ran on an existing account approved once through device-flow login. From there the work ran headless: REST, GraphQL, the gh CLI and the official MCP server created repos, commits, pull requests, reviews, issues and Actions runs, repeated across the core work. Codespaces refused our datacenter network, and the cloud coding agent needs a paid plan, so neither ran. Nothing to cancel on the free plan; account deletion is documented as web-only, so our agent revoked its grant and left the identity in place.

ShortcutL4Runs on its own

Got in; first wall at delete (blocked). Next: pay without a person

Gets in on its own: L4 · Runs on its own. Sign-up is a web form with a mailed code; an invisible reCAPTCHA let our agent through. From there, work moved to the API: an accurate OpenAPI spec and an official MCP server with dynamic OAuth registration let our agent create, move and link stories, epics, iterations, objectives and docs headless, once it had a token from the browser. Our agent started no paid plan, so there was nothing to cancel. Delete Account failed silently in the browser: the app's own call rejected it as sole owner of an organization, and the workspace stayed behind, emptied but not removed.