Michael

“WORK HARDER!” everyone keeps yelling. Go faster. Stay later. No pain, no gain. So people created more tools. More tabs. More ping-ping-pinging threads. More check-ins to check in on… the last check-in. But the problem isn’t effort. It’s context – or a lack of it. And clarity – also lacking. And confidence – because who even trusts their AI’s answers? That’s why we’ve spent the last 5 years building Computer: the only AI with native “shared memory”. Because when your AI has full context – across every tool, every system, every conversation, every decision – there’s less guesswork. Less busywork. You get more clarity. More order. More time to focus on work that, you know, matters. All thanks to AI answers you can trust – and act on. Working harder? That’s over. It’s time to work softer.

How do so many polymarket traders find codex and Claude engineers in coffee shops to review their “builds” 😂.

This isn’t X it’s Y is the new Em-Dash.

@aikarjal Reach out if you want to try Computer for just this.

Someone needs to build a company around Customer Context Graph. Collect all the threads – emails, meeting transcripts, slack messages, contracts, deliverables, detail, info, and config – from your customers into context that can be explored and queried by agents. This info is scattered between CRMs, ticketing systems, note takers, product, landing pages – it's inherently cross platform information. You need a new solution. Kind of how Segment did it trad SaaS apps. With this context, you can fire up Claude Cowork or similar for ad-hoc work or build extremely powerful agent automation flows. Expose the context as skills, MCP, and file system. Even better if you build it as open-source with a hosted option so people can take it on-prem as needed. Create a connector ecosystem around it. This will power every single next-gen AI-native full-stack business. Sort of like the context graph (@ashugarg @JayaGup10 ) that has been discussed recently but I'm thinking something very concrete: "Get me all the context about this particular customer." A customer-level, cross-system context substrate that agents can explore and act on

@SenSanders This type of broad restrictive legislation has a history of working out really well, especially love policy being defined by people with zero understanding of the technology

I will be pushing for a moratorium on the construction of data centers that are powering the unregulated sprint to develop & deploy AI. The moratorium will give democracy a chance to catch up, and ensure that the benefits of technology work for all of us, not just the 1%.

@tommoor Queue post: Major upgrade to our product less than 12 hrs of 5.2 release!!

At what point will every AI tool stop announcing every point release they add to their model picker? Soon, please? It's a string… in an array… lets stop pretending otherwise.

@fletchrichman lol did you watch our keynote last week ;)

Also, we are hiring! Please reach out if you're excited about building this

Working on this with a small group of design partners

@petergyang You think skills will dethrone it for you?

Maybe I’m old fashioned but I still find Projects far more useful than AI agents, AI browsers, or whatever is hot in AI right now.

Machado’s rule!

Today we launch Computer. 🎤👇

@dheeraj abandoning the devs, @stewart say it ain’t so!

The brand is battered… the agent crawlers did it to them. 🥹

Trust and fostering a community use to mean something at SFDC; now it’s about lock-in by degrading developer experiences.

@evanowen @grinich @SlackHQ @Benioff @GlueAI Let’s figure this out; between Glue and DevRev; we can take the slack handcuffs off.

@grinich @SlackHQ @Benioff @GlueAI stay tuned.

The new @SlackHQ API rate limits are absolutely insane: For accessing messages, you can now only make 1 request per minute, with a maximum of 15 messages 🤯 And yes this applies to ALL apps, not just public ones. We can't build internal tools on our OWN data. @Benioff this is wrong and hostile to your customers. Please reverse this immediately. If you are worried about abuse, just limit APIs for public apps. Companies must always have unlimited access to their own data in your products.

@grinich @SlackHQ @Benioff It’s obvious… Salesforce is saying it’s NOT your data

Had anyone actually heard of Astronomer before? Part of me thinks this may just be the best awareness campaign ever.

@tommoor I think they just saved you the effort of blocking this only to get a like message from a different number.

How is "Block and report as spam" not an option here… do Apple employees somehow not get this stuff?

@tommoor @codegen These guys launched yesterday, been at it for a year now. thesys.dev

Who's building the @codegen of design?

@hvpandya Forget Figma; this is my guidance to any non-designer. Swallow your intuition to give suggestions and simply comment on what you like.

🧠 Underutilized Figma trick Positive affirmations while leaving feedback on a file are just as important as comments that deliver critique. Designers benefit a lot from understanding the nature of thinking they should *amplify*. Goes a long way towards value alignment.

With so much AI revenue up for grabs through current tech and good engineering, Foundation teams are stuck competing to maintain their 3, 6, 9-month edge, often at the cost of the inventiveness AGI may require.

@brian_armstrong @DavidSacks I have a feeling it won’t run on MCP; or atleast won’t rely on it.@DavidSacks

@DavidSacks Needs to be at the operating system level probably? So that means Google, Apple, or Microsoft. Unless this leap is big enough for a new OS company to come out (probably not).

First agent to connect to all of your work apps — so it can access information and complete tasks across all of them — will probably win.