I joined with @macrodotcom last week as an official Macro partner. I've worked with a lot of companies as a partner, but I've never seen anything like this ๐. A few of my suggestions have already been built.
As a partner it is important for us to be able to communicate what our clients need, this is spectacular and I am excited about the future!
I'm currently in 14,562 support channels with mostly free users. It is a constant firehose and well beyond the point of not scaling, but we're still doing it.
And recently, instead of just leadersip and gtm, we added the entire engineering to these channels!!
It is super overwhelming but we learn a lot and it gives us so much energy. The support channels are the best thing we've ever done.
If not for them we would have...
Never known how badly people wanted Outlook, Slack, WhatsApp integrations, more task features...
Never caught a million tiny paper cuts and bugs...
Never developed meaningful relationships and heard the kind words of strangers who love what we've built and want to see the Macro project succeed.
Thank you to everyone who has provided their feedback to us, positive and negative.
We'll try scaling this to 100k users! To do so, we'll probably need to build some new tech which we may productize and make helpful to other companies as part of the product.
We've significantly expanded Routines. We think they're the best Routine product in the market.
Here's why:
Basically every AI product at this point has Routines, i.e. AI things you can kick off on a schedule, and they're not so useful.
After a few scheduled runs you probably get bored of your "weekly digest" and disable it.
The reason they're bad is in the word "scheduled" or "heartbeat".
For time-sensitive things, running on a timer isn't great.
You want them to run instantly when things happen *across your company*.
But how do you know "when things happen"?
There's where Macro's Unified Events System comes in, that has a single event bus for everything.
E.g. When a super important email comes in from a client โyou want to detect that using Jev โ and then update a channel or create an !!! Urgent task.
E.g. When a call ends, but only if it's an external call, place it in the right place on the CRM, or move it if it already exists.
Here's a quick voiceover:
Introducing Macro Tasks 2.0 ๐
The first version of Macro Tasks mirrored the informal way that our eng team likes to work: no cycles, no sprints, autonomy and minimal overhead.
But we quickly heard from users in support channels that this is insufficient and you want more traditional project management functions.
You asked us for:
1. Projects like Linear to organize your work
2. Kanban and Gantt view and saved views
3. The ability to assign Tasks to agents using the same dropdown that you use to assign to humans
4. Better Status icons that let you see the progress of a Task at a glance
5. Subtasks nested under parents tasks
6. Routines with a Unified Events system that allows you to create tasks programatically, or update them when things happen across the workspace, like a customer email, a #bugreport message, a message from a customer channel, a log event, etc.
Tasks in Macro are now self-driving if you want them to be. They create themselves from events, assign themselves to teammates based on team-level memory, and complete themselves with connected agents.
Of course, you can do all this via UI or MCP.
Paired with Macro's Github block, you can go from message -> task created -> task assigned to agent -> pull request -> merged without leaving your channel. It all links together bidirectionally.
And Macro Tasks isn't just for eng. It's great for marketing teams, sales teams, and generic Trello-esque project tracking.
Clipping is here ๐ฌ
Grab your favorite moment from any video, add your take, and post it without leaving X.
Creators: every clip credits your original video and links back to it, so new viewers can find your work and keep watching.
Clippers: you now have an easy, native way to share moments from your favorite creators directly on X.
The best part? Both the original creator and the clipper can earn from views on the clip through Original Content Rewards.
Everyone wins when great moments travel. Clipping is one more step toward making X the best place to create, grow and earn.
In Macro Chat, with the new agents system, your agents are like people. They're first-class citizens you can add to a specific channel โ or all Team channels โ and mention them to give them work.
Like humans, they can also ambiently listen to channels and reply to things without being mentioned.
Try running @claude, Hermes and other agents from one message and watch them coordinate with each other.
Thirty-four days before she reported to prison, Theranos founder Elizabeth Holmes gave Nathan Fielder and Lance Oppenheim access to document her every move.
That turned into a three-year project, and A24 will release the resulting documentary this October.
Clipping is here ๐ฌ
Grab your favorite moment from any video, add your take, and post it without leaving X.
Creators: every clip credits your original video and links back to it, so new viewers can find your work and keep watching.
Clippers: you now have an easy, native way to share moments from your favorite creators directly on X.
The best part? Both the original creator and the clipper can earn from views on the clip through Original Content Rewards.
Everyone wins when great moments travel. Clipping is one more step toward making X the best place to create, grow and earn.
What are you using for your unified AI workspace? What I mean is a place where all of your employees and your AIs can work together. Obsidian is great for 1 person but not so great for multiple people to work on. What do you use?
@zachlloydtweets Yes, I was putting this in Obsidian, but it was only single user, then I found @macrodotcom and now we've got it in there. Full multi-user.
That same-day note discipline is doing more work than most tools do. It's also the tell: you're the integration layer.
The manual step is exactly where context leaks. Miss the note on a busy day and that decision never made it into the vault, and your agents don't know what they don't know. And "email stays in email unless it changes something" means you're making that judgment call every single time.
In Macro, that capture step disappears. Calls are recorded and transcribed into the shared memory, and email already lives in the workspace, so a decision is in context the day it's made. No re-filing, no inbox folder to remember.
Your setup is honestly a perfect test case for this. I offer a free AI assessment: you tell me how your team and your agents run now, and I send back a short personalized video on where the manual steps will bite as you scale, and what I'd change first. It's in my profile link if you want it.
@kottley@markgurman Yeah, once youโre used to delegating the outcome, going back to directing every action feels like more work, not progress. I'll stick with my newer agents like Grok and Muse thanks.
@Hilltech No rule needed. Lookups go to the agent, and it pulls the answer from the email, the doc, the call where it was decided. Humans get what's left: the judgment. That IS the separation. You can even tell the agent to mention the human who might know the answer.