How building with Prismic is changing, for you and your agents

Building with Prismic is changing. Slice Machine is no longer our recommended way to build, and the new way is the CLI with an AI agent, plus the new Type Builder.

We know Slice Machine is something you loved, and something we championed, so if you're one of its fans, we owe you a reason why. The good news first: you keep the local, code-first workflow you liked, and you gain an AI agent that can build a page, or a whole site, with you. This post covers what's changing and why, and answers every question we could think of.

What's changing

The Prismic CLI, used with an AI agent, is our new recommended way to model content in Prismic. We built it from the ground up to be used by agents first. We shaped it alongside the Prismic skill, so building with an agent is fast and reliable, and follows Prismic's best practices. Your agent can model content and build directly in Prismic, while you stay in charge of design, styling, and review.

Follow that path and you keep your local, code-first workflow: the CLI runs locally, just like Slice Machine. It runs through npx, and the new Type Builder runs in the cloud, so there's nothing to install and nothing to update by hand. New features reach you automatically, so you're always on the latest version.

The new Type Builder is there when you want it: a visual surface in the cloud for inspecting models, making quick edits, or modeling without AI.

Want to see it in action? Here's a short demo of building with the CLI and an AI agent:

Why we're making the change

Two things drive this change.

The first is how developers build now. Building with AI agents is the default, with 84 to 90% adoption across the 2025 Stack Overflow, JetBrains, and DORA developer surveys. That means our job now covers not just the best developer experience, but the best agent experience too. It's the shift we're building Prismic around, and the core of our mission as an agentic web platform.

The second is our obsession with removing friction. A local app was the right fit before AI, but you had to install it and update it by hand. Those steps never bothered anyone before. Now that agents automate so much of the build, small manual steps stand out. So we set out to remove that last bit of friction.

What you gain by switching

This is the part we're most excited about. The CLI turns your AI agent into a building partner. With Claude Code, Cursor, or Codex and the Prismic skill, you can build a page or bring a whole site over much faster than before, while you stay in charge of design, styling, and review.

The CLI was built from the ground up for agents, and we shaped it alongside the Prismic skill, so building with an agent is fast, reliable, and follows Prismic's best practices. Your agent models content and builds directly in Prismic, and you review the result in code, the way you always have.

You also stay current without thinking about it. Every new capability comes to the CLI and the new Type Builder first, so your workflow only gets better from here.

"But I loved Slice Machine..."

We loved it too. That's why we worked hard to keep most of what you value intact, even if we've still got some work to do. Here's what you keep and what genuinely changes.

What you keep. The control you cared about. Your models stay in your project as files, your codebase stays the source of truth, and you review changes in code. TypeScript type generation and the slice simulator keep working too, so the setup you rely on carries over. The CLI is the direct successor to that local, code-first workflow.

What genuinely changes.

• Two former Slice Machine features now run through your agent: turning an image or a Figma design into a slice, and generating code snippets. Without AI, you can do both by hand.
• Editing model JSON, like rich text labels, still works. On the recommended CLI path, your models are already local, so you just edit and push. If you started a model in the new Type Builder, there's one extra step: pull with npx prismic pull, edit locally, then push back.
• Environments still work, with an --env option on the CLI and a dropdown in the new Type Builder. What changes is the automation. Slice Machine used to tie this together, so switching your active environment also switched what your development site rendered. Now you pass --env yourself, like npx prismic pull --env main-staging.

We know that working with environments means being confident you're on the right one. If the manual way doesn't work for you, we have a few ideas to make this experience excellent, and we're actively working on them. We'll share an update as soon as it's ready. And even with this step, we think the switch is worth it for everything you gain by building with an agent.

Prefer not to use AI?

AI is optional. Both the CLI and the new Type Builder work fully without it. The new Type Builder is a full modeling editor with no AI required, and you can run the CLI by hand whenever you need it.

Ready to switch?

We hope so! Moving over takes minutes; most of it is automated, and your project architecture doesn't change. Three steps:

1. Push any pending model changes from Slice Machine.
2. If you're using AI, install the Prismic skill: npx skills add --global prismicio/skills
3. Run npx prismic init. It swaps the config, pulls your models into the project, and clears out the old Slice Machine packages.

The full walkthrough is in the migration guide in our docs. Slice Machine keeps working, so there's no hard deadline. But everything we build from here goes into the CLI and the new Type Builder, not in Slice Machine. Move sooner, and you stay on the latest, on the same agent-native foundation we're building everything on from here.

Questions you might have