Andrew Harvard

[Andrew Harvard @aharvard]

https://t.co/BJVQMXmeVg

[Andrew Harvard @aharvard]

this is where it all started: https://t.co/kQk92r9Ito

[Conrado Brenna @cbr4444]

MCP UI unblocks agentic commerce. Quick mockup on how we plan on bringing this to our Square sellers: https://t.co/Nv9JwSqhvH @blockopensource

[Andrew Harvard @aharvard]

Agentic commerce at @blocks is powered by MCP Apps

https://t.co/LuPKPSUYBX

[Andrew Harvard @aharvard]

We used @goose_oss to dogfood this experience. That help create the MCP Apps spec. That enabled the birth of agentic marketplaces like ChatGPT Apps and Claude Connectors... a full circle moment here of the goose chasing it's tail

[Andrew Harvard @aharvard]

@cbr4444 @blockopensource hey look @cbr4444, we did it! (with a lot of help from folks at Block and friends across the industry) https://t.co/LuPKPSUYBX

[Andrew Harvard @aharvard]

@cbr4444 @blockopensource ...and here's a look at how it might all come together with an MCP UI powered server for Square in a MCP host app like Goose:

[cam worboys @camworboys]

Something new. Coming Thursday.

[Andrew Harvard @aharvard]

@rsms @michaelneale https://t.co/zDebuKgAQG is a bit more detailed

[Andrew Harvard @aharvard]

@rsms @michaelneale my understanding is that it does both: for dense models, one inference can span multiple machines; for multi-model use, it’s not one shared context across models, but one main session that consults other models and injects their outputs.

[Andrew Harvard @aharvard]

@rsms you might find mesh-llm interesting https://t.co/wTVEbde1Xx (made by
@michaelneale)

[goose @goose_oss]

we're working on goose 2.0... in the open 👀

rebuilding the architecture so every client speaks the same language

landed a new TypeScript TUI

desktop moving to Tauri

powered by ACP for one unified agent core

come break it with us.

https://t.co/qlFWz6qRkt

[Andrew Harvard @aharvard]

@hey_amandam you rock! hopefully we can still collab in open source!

[Andrew Harvard @aharvard]

Update: Block leadership informed me that my layoff was due to a clerical error. They offered me the opportunity to return, and I’ve accepted.

[Andrew Harvard @aharvard]

I enjoyed my time at Block. I got to work with great people, honed my skills, and built some cool stuff.

[Andrew Harvard @aharvard]

@kentcdodds thanks, Kent! me too 😅

[Andrew Harvard @aharvard]

To my former colleagues continuing to face the reality of layoffs, please feel welcome to contact me directly for support. I will make time to help you with whatever you need.

[Andrew Harvard @aharvard]

I enjoyed my time at Block. I got to work with great people, honed my skills, and built some cool stuff.

[jack @jack]

we're making @blocks smaller today. here's my note to the company.

####

today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone.

first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay.

we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly.

i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures.

a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers.

we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold.

to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward.

to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow.

jack

[Andrew Harvard @aharvard]

building agentic commerce in @goose_oss has had a meaningful impact on the MCP Apps spec — I'm excited to see this out in the world and rolling out to other MCP hosts soon (great demo @debs_obrien!)

[goose @goose_oss]

Just ordered lunch without leaving my AI agent 🤯 With the Neighborhood extension in goose, I found nearby restaurants, browsed menus with images right in the chat, and added my orders to the cart, all from a simple prompt. The future of AI-powered food ordering is here 🍜🥗

[Andrew Harvard @aharvard]

@kentcdodds I wouldn't say it totally replaces the remote-dom use case, more of a stopgap solution that enables UIs to look like their hosts.

I'm hopeful we can land a new mimeType that gets us all the way there.

[Andrew Harvard @aharvard]

coming soon in @goose_oss: MCP Apps can inherit styles

[Andrew Harvard @aharvard]

delightful

[cam worboys @camworboys]

From the workshop of @DamjanStankovic

Didn’t even make the cut for something new we’re building. But too fun not to share.

Such a fun time to be a designer 💚

[Andrew Harvard @aharvard]

MCP Apps FTW!

[Conrado Brenna @cbr4444]

We shipped the Neighborhood extension to all @goose_oss developers. You can now agentically order breakfast, lunch and dinner. Try it out, and build on top of it! https://t.co/Wly1AoBc2A