← Back to all sparks
Asana logo

Asana

PMCOLLAB
Velocity8.8

Work management platform for teams

Asana is bolting an agent layer and a docs surface onto work management.

ai-teammatesautomationcollaborative-docsrich-textwork-management
Current state
Asana is shipping on two tracks at once. The visible one is editor surface work — Pages, rich text in custom fields, threaded comments, text highlighting — landing in a tight cluster over the last month. The structurally significant one is quieter: AI Teammates and AI Studio have moved from executing work to inspecting and authoring the automation rules that govern it. Most of these releases cite named Forum requests, so the roadmap is visibly demand-led.
Where it's heading
The editor work converges on a single canvas where documents and tasks share formatting and context, with Pages as the anchor and rich text spreading outward into fields and inline highlighting. The AI work converges on an agent that can read and write the workspace's own configuration, with a human review gate before anything publishes. Read together, Asana is trying to keep both the planning document and the automation layer inside its own product rather than at the integration boundary.
Prediction
Expect the rich-text surface to close its mobile gap and pick up the remaining formatting options Asana says it is still exploring, and expect AI Teammates to widen from drafting a single rule to proposing changes across a project's whole automation set.

Recent moves

  1. 5d ago

    Make key details pop with text ✨ highlighting ✨

    Text highlighting arrives in the rich-text editor one day after rich text reached custom fields, continuing the steady buildout of Asana's writing surface. It ships deliberately thin: one color, web only, and editing a highlighted passage on mobile strips the highlight. The web-versus-mobile formatting gap is now the visible seam running through this whole workstream.

    View source ↗
  2. 7d ago

    📝 Rich text in custom fields is now live!

    Text custom fields gain headings, lists, hyperlinks, and inline images, pushing structured content out of the description box and into the field layer. It answers a long-running Forum request for a genuinely long-text field type. The caveats mark it as a first pass — list and board views render a simplified version, and CSV exports drop formatting entirely.

    View source ↗
  3. 8d ago

    Threaded Comments are LIVE! 🧵

    Replies now nest under the comment they answer across tasks, goals, messages, and status updates, on both web and mobile. This is overdue table stakes rather than new capability, but it lands inside the same collaboration-surface push as Pages and rich text. The case it actually fixes is a busy task carrying several parallel conversations at once.

    View source ↗
  4. 19d ago

    ✨📄 Introducing Pages! (formerly known as Notes)

    ⚡ SPARK

    Notes becomes Pages and picks up real-time co-editing with presence, inline comments, version history, task creation from the page, and AI-assisted drafting — the anchor release that makes the rest of this window's editor work read as one program rather than scattered polish. Asana states plainly that Pages is not a wiki or knowledge base, which bounds the ambition to documents attached to work.

    View source ↗
  5. 28d ago

    ✍️ AI Studio can now suggest clearer rule instructions

    AI Studio now reviews the instructions written for a rule and offers an inline rewrite, or explains what is too vague to rewrite. It is a quality gate on the prompt layer of Asana's automation product, and it is strictly opt-in — nothing applies unless accepted. It pairs with the AI Teammates rule work from two days earlier, both aimed at the same problem: rules that people cannot get right by hand.

    View source ↗
  6. 1mo ago

    🤖 AI Teammates can now help you understand and build rules

    ⚡ SPARK

    AI Teammates can now audit a project's or portfolio's rules — what exists, what is paused, what errored, what happened on the last run — and draft new or amended rules from a plain-English request, with a review step before publish. This moves the agent from doing work inside Asana to configuring how Asana itself works. It is the release that makes the surrounding AI Studio investment legible as a single program.

    View source ↗