AGI Was Achieved in February 2026 | Bernardo Aceituno artwork

AGI Was Achieved in February 2026 | Bernardo Aceituno

MTS

November 6, 2026

StackAI co-founder Bernardo Aceituno explains why open-weight models have caught up to frontier closed models for enterprise automation, arguing that AGI for enterprise tasks arrived in February 2026.

0:00

Bernardo Aceituno

I always say, and I start by this, that AGI was achieved in February 2026 Around the time ClothForce Opus 4.6 came to the market, and today there's hundreds of open-weight models that perform better than this ClothForce model, just like running in a local computer.

And that's mind-blowing.

0:19

Safiya

Today we are joined by Bernardo Aceituno. He's a returning guest today, and he is the co-founder of StackAI, which is now part of Asana, and open-weight models, and how enterprises are actually adopting AI agents, is what we're going to talk about today. So Bernardo, welcome to MTS.

0:36

Bernardo Aceituno

Thank you so much, Safiya. Pleasure to be back.

0:38

Safiya

Pleasure to be back. I think one of the reasons I like talking to you is because you know everything that's going on when it comes to open source and enterprise. Let's just give a quick recap. What happened in the last few weeks that really changed the game?

0:50

Bernardo Aceituno

Well, many, many things. I think that more than the last few weeks, I would say the last year has been really like the advent of open source. Past few weeks, we've seen just a, you know, perhaps a cambric explosion of open source models. We've seen meta-reflection, you know, we've seen pretty much Chinese labs with new chemists coming out there that now are like surprising benchmarks and beating frontier models.

But what I think actually you see the most impact is when you look at the ability to provide cheap inference, that is also frontier in performance when you look at enterprise tasks. I always say and I start by this that AGI was achieved in February 2026 Around the time, Cloth for Opus 4.6 came to the market. And today, there's hundreds of open-way models that perform better than this Cloth for Model just like running in a local computer.

And that's mind-blowing. I would say that, of course, the frontier will always like, you know, set the pace and you know, always the open-way model will lag behind. But the open-way community will catch up. And yeah, the frontier will always be ahead. But at one point, you think, start realizing, okay, what's my trade-off on investment, governance, residency, the likes.

2:00

Safiya

Yeah. A lot of enterprises recognize that they should start using open-way models for different parts of the stack. But how do you actually do that? How do you think about what to integrate, when you should still be using the closed frontier lab models versus the open-source models?

2:14

Bernardo Aceituno

Yeah, 100%. Well, if you look at the way an enterprise will adopt AI, they will have, I would say, two ways in which they bring AI to the operation. There's, of course, a more assistive AI usage, where they have like an AI assistant that is available to employees, let it be cloud, copilot, IGPT enterprise, etc.

And at this level, it's very normal to rely on the frontier labs. Not necessarily for the frontier model per se, but because of the application layer that exists there. Now we're seeing an advent of new tools that allow you to operate under your selection of model. And the fact that you can translate that usage from a closed-way model that lives into an unknown cloud, that lives in an unknown region, and where you don't have a complete visibility on what AI operates with, depending on your arrangement with that provider, makes it such that it's very attractive for enterprises to switch their usage to open-weight. We've seen plenty of enterprises start switching their usage, especially after they start looking at the token bill, when it starts crossing seven, eight figures a year, it starts raising alarms. And that's the first category of enterprise usage. The second category of enterprise usage is what we call back office automation, workflow automation, where they take processes that are consistent across the organization and they place agents in different places of those processes or translate just a full process into AI agents in order to transform parts of the operation. This is what we do at StackAI.

And in there, the switch to open-weight was very rapid, because most of these systems are built either with custom tooling or with AI development platforms, where often you have the ability to figure out a model, and you have a very big control on how you use tokens. When I look at some of my top customers in StackAI, I think that there used to be a major trade-off between open-weight and having a closed-source model, especially when I look at my military clients. They had to decide, okay, do I want good performance? I have to make a trade-off and use OpenAI hosting an Azure GovCloud. But if I want full residency and control in my data center, I can use a menstrual model or a Kimi model or whatnot. Today, we got to a point where for the purpose of these workflow automation tasks, they can go to their latest open-way model, let it be Inklink, let it be Muse, let it be Beam. And they can have just as good a performance as they will have expected in February this year, when for the purpose of enterprise automation, these models achieve this general intelligence capability.

Read the other 8 minutes of this episode here.

$15 gets you this episode and 99 more. Credits never expire. After checkout, one link brings you back here to read it.

Not what you expected? Full refund within 14 days.

Thousands of transcripts fetched by people building searchable podcast archives

Fetch transcripts with code

The same credits work from a script or an AI agent. The demo key returns a sample episode in full, no card needed:

request
curl -H "x-api-key: pt_demo" \
  https://spoken.md/transcripts/1000651996090

Markdown with the speakers named, for your notes, your knowledge base, or anything that makes HTTP calls.

From $0.10 per transcript. No subscription. Credits never expire. Prices exclude VAT, added at checkout for EU customers. Not what you expected? Email us within 14 days with 20 or fewer credits used and we refund the pack in full.

Using your own key:

request
curl -H "x-api-key: YOUR_KEY" \
  https://spoken.md/transcripts/1000800324741