NocoBase
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
A side-by-side editorial comparison of Asana and Tracecat — release velocity, themes, recent moves, and the top alternatives to consider.
Asana's agent left the app — it now answers work questions inside Slack threads.
Two arcs run in parallel. A text and editor surface has been built out steadily — Pages, rich text in custom fields, highlighting, threaded comments, and now syntax highlighting — and an agent layer has grown alongside it through AI Teammates, Teammate Skills, and AI Studio. Nearly every release cites a named Community forum request as its origin. The editor work carries a recurring caveat: features land on web first and mobile trails, sometimes losing formatting outright.
Tracecat is turning case comments into an agent console while it hardens the sandbox around them
Tracecat is deep in a beta.52 release-candidate train, eight RCs in, following the beta.51 release that made the Action Gateway mandatory. Two threads dominate: agents are becoming addressable from inside case comments, and the sandbox that runs them is being bounded — socket budgets, registry artifact caches, egress filtering. The product is a security automation platform steadily converting its agent story from a feature into the primary interaction surface.
Two arcs run in parallel. A text and editor surface has been built out steadily — Pages, rich text in custom fields, highlighting, threaded comments, and now syntax highlighting — and an agent layer has grown alongside it through AI Teammates, Teammate Skills, and AI Studio. Nearly every release cites a named Community forum request as its origin. The editor work carries a recurring caveat: features land on web first and mobile trails, sometimes losing formatting outright.
The editor arc is now mostly closing out a backlog of formatting asks, and each release is narrower than the last. The agent arc is the one changing shape: it has moved from configuring automations inside Asana to answering questions about the work graph from inside another vendor's application, on every tier including Personal. Building it permission-inheriting and private-by-default suggests Asana is treating the agent as a distribution surface rather than a feature to upsell.
Expect the same agent to appear on more surfaces — Teams and email are the obvious next ones — and expect mobile parity work on the editor features that shipped web-only. The language-tier expansion Asana flagged for syntax highlighting is the low-risk near-term item.
Tracecat is deep in a beta.52 release-candidate train, eight RCs in, following the beta.51 release that made the Action Gateway mandatory. Two threads dominate: agents are becoming addressable from inside case comments, and the sandbox that runs them is being bounded — socket budgets, registry artifact caches, egress filtering. The product is a security automation platform steadily converting its agent story from a feature into the primary interaction surface.
The agent work is moving from 'you can invoke an agent' to 'the agent lives in the case thread' — mentions, session chat, activity shown inline, and now MCP integration references correlated on workspace pull. Running alongside it is a sustained isolation effort: every second RC raises or filters the NSTUN socket budget, which reads as capacity being tuned under real agent load rather than a one-off fix. The UI is catching up too, with a properties rail and editor redesign borrowed from Linear's density.
Expect beta.52 to land as a final release with agent-in-comments as its headline, and the NSTUN capacity raises to stop once the ceiling holds. Whether the MCP reference correlation grows into full workspace-level integration mapping is not yet visible in these entries.
Other PM products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Asana or Tracecat.
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
Hive ships in batches, and this one is all planning accuracy and admin control.
Plane ships a fortnightly digest, and the AI layer is where the real work is going.
Ever Teams shipped ten tags in twelve hours and one of them touched the product
Apploye's feed is an SEO blog, and its running theme is defending monitoring on privacy grounds.
Notesnook ships steady 3.4.x patches across desktop and Android with the notes kept off-feed.
See all Asana alternatives → · See all Tracecat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Asana and Tracecat are shipping at a similar cadence (velocity 7.5 vs 7.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Asana and Tracecat are shipping at a similar cadence (velocity 7.5 vs 7.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Asana alternatives in PM are ranked by recent ship velocity. Browse the "Asana alternatives" section above for the current picks, or visit /alternatives/asana for the full list with editorial commentary on each.
Top Tracecat alternatives in PM are ranked by recent ship velocity. Browse the "Tracecat alternatives" section above for the current picks, or visit /alternatives/tracecat for the full list with editorial commentary on each.