Robert Ta describes Anthropic's Artifacts in Cloud Code beta, launched June 18, which generates live shareable web pages from code sessions without copy-pasting to Slack. Unlike full app builders like Codex Sites, Artifacts are single-page frontends with no backend, form handling, or API calls, designed to quickly visualize LLM outputs for teams.
Cloud Code sessions now build shareable web pages in real time. Here's what happened and what matters for teams using Cloud Code daily. You could stop copy pasting terminal outputs and screenshotting your pages into Slack and start sharing live dashboards that update as your agent works. That's what the Anthropic team just released on the heels of Fable-5 being pulled from production. On June 18th, Anthropic launched Artifacts in Cloud Code beta. Cloud Code Sessions can now generate interactive shareable webpages that update in real time. And so if you're familiar with the Cloud Artifacts kind of experience, if you're a Cloud user, you'll know that Artifacts is really cool, pops up on the right. You could see your plans, you could see your, you know, written markdown or whatever you're building, HTML files, et cetera. And Codex has adopted that paradigm into their app. This continues with the news that we reported last week with Codex Sites. Are Lovable and Base44 and other Vibe Code editors going to die soon? Like, is the application layer that's carved out there, is there really a moat? If Cloud Code is going after this now with Artifacts and Codex from OpenAI, they're clearly going after that space as well with sites. What are we seeing? Jonathan, maybe that's the first thing I'd love your take on is, is Lovable dead with this move of Cloud Code Artifacts?
I think it's kind of moving that direction where it's more capable of, uh, building the kind of things you would in Base44. But for me, this is solving a slightly different problem, which is just kind kind of like, you know, when I'm interacting with the model and I sort of like, aha, I get it. Now, how can I show this to my teammate? There might be insights spread across 3 or 4 different responses. And I'm like copying and pasting text from the output of the LLM to share with a colleague. I think this is like, okay, let's synthesize this. Let's create a visual artifact that I can share and do it really quickly. And I think that feels like the magic that they're presenting right here is solving that, that kind of problem versus the Base44 problem.
Makes sense. Yeah. And we see here what an artifact is not, which is just as important. As what it is. It's a capture of work, not an application. It is a one self-contained page with no backend. So it cannot store form input, call an API at view time, or serve multiple routes. As opposed to Codex with Sites, Sites actually allows, from what I understand, some input data and data to be captured. So if you have some sort of forms you want to capture across your teams at an enterprise, you could do that. Looks like artifacts currently are not that in Cloud Code, though I wonder if they're going to go that direction in the future. We will have to see.
And we've been discussing the need for an internal tool like Shopify Qwik system, which is like a server that can contain HTML pages that you could share very easily with teammates. So it solves that problem of like, hey, here's what I built on localhost, let me show it to you. And I think both the Codex and Cloud Code are getting closer to this, like helping teammates experience what you're experiencing with your localhost creations.
