AI Weekly Malaysia

Anthropic's Claude blog published the third post in its 'human-agent teams' series, a case study of how Asana runs AI agents as teammates on its own Work Graph model, with Arnab Bose, Asana's Chief Product Officer, describing the setup. At Asana, Claude is the default AI tool connected to Google Drive, Slack, Asana, Zoom meeting recordings and Databricks reports; agents get defined roles, are assigned tasks, read and write messages, and appear in activity feeds next to humans, with extra safeguards on what they can access and share. The piece names three required capabilities: persistent memory, agents having their own credentials, and shared context.

Why: The reusable idea here is architectural, not product news: Asana did not build a separate context store for agents, it put them inside the existing task/project/owner graph, and it gives agents their own credentials rather than a shared service account. If you are wiring agents into a product or internal workflow, those two decisions are what determine whether permissions, audit trails, and 'who changed this' stay answerable. The post gives no numbers, no failure cases and no pricing, so treat it as a design pattern to compare against your own setup, not as evidence that this works at scale.