Macro

Unifies your work into one app with shared memory

Productivity

Task Management

Artificial Intelligence

Visit WebsiteSee on Product HuntInstagram ⧉App Store ⧉Twitter ⧉Github ⧉

Love the concept. Curious if it is able to manage two+ workspaces or profiles. For example: one for work, one for personal? Another use case: a fractional CMO/CFO/etc has hands in multiple companies, multiple clients. How do you keep them from cross-pollinating signals?

How do you make sure team memory does not show private or restricted information to the wrong person?

For example, if a junior engineer at company ask a question and the answer is hidden inside an email, call note, or document of company's CXO that they do not have access to, will Macro completely ignore that information or still retrieve then data ?

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.

finally an app that actually unifies my inbox and tasks without feeling clunky, the memory search pulled up a thread from last month instantly

This is very interesting, and I like the unified experience. But does that mean I have to move out of Notion and rebuild everything?

how does team-level memory actually work when people leave or join a workspace, does it retain or wipe their context

Finally tried Macro this morning and the team memory feature actually works like advertised. Asked it to pull up last week's client thread and got the email, doc, and follow up tasks in one view.

How does team-level memory actually work across different tools like email and code, and is it really seamless or do you have to manually tag what gets stored?

How does team-level memory actually work across different apps — does it just index everything or is there a way to exclude certain conversations or docs from being searchable by the rest of the team?

the team-level memory idea is genuinely clever - being able to query your whole workspace instead of digging through tabs sounds like a real quality of life upgrade

Finally tried Macro after hearing about it for weeks and the team memory feature is the real deal. Pulled up everything I needed across docs and messages without jumping tabs.

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?

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?

The constant hopping between apps is one of those small daily drains you stop noticing, so seeing it all pulled into one calm place is a relief.

finally something that pulls my chaotic slack, gmail, and notion stuff into one place without me copy-pasting between tabs. the team memory search is genuinely useful for digging up old context

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?

replacing 17 tools with one app is the pitch every all-in-one workspace makes, and it usually means each individual piece ends up 80% as good as the dedicated tool it replaced. what's actually best in class here vs just "good enough to not need Slack anymore" - email triage, docs, or something else

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 shared memory part is the bit I’m most curious about. Feels like a lot of tools are getting better at storing more context, but more context is not always the same as useful context. How does Macro decide what is actually worth remembering? Is it mostly things I tell it to save, or does it start picking up patterns from how I work over time?