Shortcut vs Asana
Side-by-side trajectory, velocity, and editorial themes.
Shortcut redesigns its API for AI agents and pushes Korey beyond its own walls.
Shortcut is making concrete bets on agent-based work. API v4 entered alpha on May 12 with explicit framing around expanded capabilities and 'agent compatibility' — a positioning shift, not just a version bump. Their in-house AI assistant Korey is expanding outward: right-click access in February, then a dedicated Chrome extension in April that runs on any webpage. Around the strategic work, smaller improvements (Teams on Roadmap, March's SLA Alerts) keep shipping, alongside feed-noise from brand-guide pages being scraped as if they were releases.
Shortcut is positioning itself as the project-management surface that AI agents naturally operate against, not just a PM tool with AI features bolted on. Korey is being pushed from in-app helper toward general-purpose web assistant; the API is being redesigned with external agent consumers in mind. That's a coherent strategic stance the bigger PM players — Jira, Linear, Asana — have not yet made as explicitly. Underlying release cadence stays steady, suggesting these are strategic plays, not panicked pivots.
Expect API v4 to surface MCP-style tooling endpoints and structured action surfaces aimed squarely at agent frameworks. Korey's Chrome extension is likely a stepping stone toward a 'Korey anywhere' positioning — deeper integrations with browser, email, and calendar are the natural next dominoes.
Asana goes serious on enterprise governance while loosening its core workspace model.
Asana is running two parallel arcs. The first is a real enterprise governance push: RBAC for View Permissions, then Create Permissions, both landing in Release Preview within a week — the most credible enterprise hardening Asana has shipped in a while. The second is a quiet structural relaxation: Teamless Projects break the long-standing rule that every project lives inside a team, and subtasks now inherit parent context up to five levels deep.
Expect more granular admin controls (Edit Permissions, audit scopes) to follow the RBAC View/Create pair, with GA dates already cited for early June. Automation continues to creep toward scheduled and bundle-managed rules, suggesting Asana wants rules to feel like programmable infrastructure rather than per-project knobs. The structural side — teamless, hierarchy-aware task panes — points to Asana letting work organize itself across teams rather than forcing the team container.
Within the next release cycle Asana will round out RBAC with Edit/Delete permission scopes and tie them to the audit log, completing the story it can take into enterprise procurement reviews. Expect Scheduled Triggers and Bundles to converge into a single rules-management surface.
See more alternatives to Shortcut →
See more alternatives to Asana →