Macro is the all-in-one workspace that combines email, messages, docs, tasks, code, agents, calls, and CRM. With team-level memory, you can query your entire workspace and never lose context.
This is the 2nd launch from Macro. View more
Macro
Launched this week
Macro is the all-in-one workspace that combines email, messages, docs, tasks, code, agents, calls, and CRM. With team-level memory, you can query your entire workspace and never lose context.
Free Options
Launch Team
How does the team-level memory actually work across different tools like email and code—does it pull context live or do you need to keep everything inside Macro for it to be useful?
Macro
@ozkur99489 Email, it connects to your Google Workspace / Gmail accounts. We've had requests for IMAP and Outlook which is on our roadmap. For your other tools, you canconnect them here. Just hit MCP's in the bottom left to add integrations. From there, the agent will be able to access or import your content. Just say "import my docs from ..." etc.
the super-app graveyard is real. slack tried to be your inbox, docs, calls, CRM. teams too. both ended up as chat with a lot of tabs nobody clicks. the thing that would actually make one of these work is the connective tissue between the parts. team memory is that, if it knows who said what where.
genuine question: is the memory a permission-scoped graph or a flat corpus? that's where team products either become invaluable or become HR nightmares.
Macro
@thenameisarian Thanks for your comments Mustafa - see my reply to Dipankar!
Inheriting the launching user's permissions is a sane default. Where it got us was memory writes: once the agent summarizes something into shared memory, a teammate with lower access can pull that derived summary later even if they were never allowed to see the source it came from. Does a memory entry carry the ACL of its most-restricted source, or does it just inherit the channel it was created in?
The "query your entire workspace" piece is what stands out to me. I do research-heavy work and the hardest part is that context ends up scattered across notes, docs, and threads. Curious how the shared memory handles retrieval when the sources are so different in shape — a call transcript vs. a code file vs. an email thread. Is it one unified index under the hood, and can memory be scoped per person/team so private DMs don't surface in a shared query? The open-source angle is a nice touch too.
CheckYa
I've been waiting for a workspace where AI actually understands everything happening across emails, docs, and tasks. This looks like a promising step in that direction. Best of luck with the launch!
Macro
@monir_ You can also accomplish this by MCP'ing Claude/Chat into all your tools. But:
MCP is often a limited subset of the app itself, or rate limited. Your agent received a partial representation of what you get as a human user. It often makes mistakes that aren't forgivable. Incentives are misaligned because each develop wants to keep you in their ecosystem, just just become something that lives under the LLM.
You're still paying for all of those tools. The cost adds up to much more than Macro's free version or $40/month plan. if you sum Superhuman, Notion, Linear, Slack, HubSpot, etc., etc., you get to a significant sum. And to save money, often you'll not give e.g. HubSpot seats to everyone who needs them which leads to further fragmentation of who-can-see-what in your company. Macro unifies all of this into one business system.
You still have to login, 2FA and have sign ins to a bunch of different tools. This is mostly a problem on mobile where you have links going across apps. It's easier, but still annoying, to context switch between different tabs on desktop. It's even harder on mobile.
Fundamentally, each tool was designed as a silo, only with limited integrations. For example there is no button in Superhuman to take a customer email and report it as a Linear ticket: that's a manual process you have to do of pasting an image in Slack and having an engineer (or you) create a ticket, which doesn't always happen. In Macro, because each product surface was co-designed you don't have to do this, just hit "task" from email to bidirectionally link a new task to that customer email.
There is no unified memory layer, in part because nobody is "in charge" of constructing this. Nobody has all the pieces. You buy a little slice of your stack from each vendor. Macro provides unified and team-level memory across all your tools, because it is all your tools, co-located in one ta and co-designed to work together.
Open source is a smart trust move for a workspace that wants to hold email, docs, tasks, calls, and CRM in one place! The adoption challenge is that most teams will not move their whole stack at once. Are early users starting with Macro as an email client first, or are they bringing docs and tasks in from day one?
Team-level memory that lets you query your whole workspace is the compelling part - most unified-workspace tools stop at search. Does the memory span everything (docs, calls, CRM) from day one, or is there a lookback window before it kicks in?