Build Great Products · YouTube · 12:03

Vibe Coding is Dead. This is the Future

Five structural shifts redefining how developers build with AI agents in 2026.

Posted

May 12th 2026

3 days ago

Duration

12:03

Format

Listicle

educational

Channel

BGP

Build Great Products

§ 01 · The Hook

The bait, then the rug-pull.

Twelve minutes. One camera. No B-roll. And a host who opens by declaring the genre he is talking about dead. Chris from Build Great Products is not being contrarian for sport. He is tracking five structural shifts he thinks most AI builders are sleeping on, and his case lands because he names actual tools, actual people, and one embarrassingly relatable image: sitting there hitting yes yes yes yes approve while the agent just works.

§ · Stated Promise

What the video promised.

stated at 00:15“I wanna break down the five big shifts that are happening in vibe coding today so that you know exactly how to build with AI the right way going into the rest of 2026.”delivered at 11:09

§ · Chapters

Where the time goes.

00:00 – 01:00

01 · Cold open and promise

FUD hook: vibe coding changed more in recent weeks than most realize. Promise: 5 shifts, the future of AI building, how to apply them today to be ahead of 99%.

01:00 – 03:17

02 · Shift 1 - Agents code anywhere

Moving from AI inside an IDE to agents accessible from phone, terminal, any environment. Tools: Claude Code remote control, Cursor Cloud Agents, Replit and Lovable mobile apps. Sessions transfer across devices.

03:17 – 05:09

03 · Shift 2 - Auto-compaction

Manual context management is becoming obsolete. Frontier models ship auto-compaction that preserves critical context without context rot. Amp leads the way.

05:09 – 07:54

04 · Shift 3 - Stack the queue

As agent quality rises, stop send-wait-review loops. Queue multiple prompts; automate daily code review at EOD. Codex desktop shows this: stack messages, drag to reorder, interrupt mid-chain.

07:54 – 09:15

05 · Shift 4 - Let the agent cook

Power users already run dangerously-skip-permissions 100% of the time. Sub-agents generate so many tool calls that manual approvals are pure friction. Anthropic and OpenAI ship auto-review modes for this reason.

09:15 – 11:09

06 · Shift 5 - Multi-agent multi-project

Run multiple agents across multiple projects simultaneously. Orchestrate so they do not conflict. Non-code tasks (research, launch videos, social, presentations) belong in the agent queue too.

11:09 – 12:03

07 · CTA and outro

Community pitch: school.com/aiapps, 250+ members.

§ · Storyboard

Visual structure at a glance.

open - FUD hook

hookopen - FUD hook00:00

agenda slide

promiseagenda slide00:22

shift 1 - agents anywhere

valueshift 1 - agents anywhere01:10

shift 2 - auto-compaction

valueshift 2 - auto-compaction03:17

shift 3 - queue stacking

valueshift 3 - queue stacking05:09

shift 4 - let it cook

valueshift 4 - let it cook07:54

shift 5 - multi-agent

valueshift 5 - multi-agent09:15

CTA school.com/aiapps

ctaCTA school.com/aiapps11:37

§ · Frameworks

Named ideas worth stealing.

00:15list

The Five Shifts of Vibe Coding

Agents code anywhere (not just inside an IDE)
Auto-compaction replaces manual context management
Queue-stacking replaces send-wait-review
Permission delegation - let the agent cook
Multi-agent multi-project orchestration

A sequential framework mapping the behavioral evolution of AI-assisted coding from 2024 babysitting to 2026 fleet orchestration.

Steal forAny state-of-AI content, tutorial on upgrading your Claude Code or Cursor workflow, or positioning piece on why solo builders are now faster than dev teams

§ · Quotables

Lines you could clip.

00:18

“You can be ahead of 99% of other people.”

Self-selection promise with near-universal framing - works as a hook with zero setup→ TikTok hook

08:44

“You can just sit there hitting yes yes yes yes approve constantly until the AI agent actually completes its work and 99% of those approvals actually did not need your input at all.”

Visceral relatable pain point. The repetition lands as comedy and frustration simultaneously.→ IG reel cold open

09:13

“Part of being able to do this is actually just a skill issue in terms of how you use these AI coding tools.”

Honest slightly confrontational - calls out the human as the bottleneck rather than the tool→ TikTok hook

07:54

“There are people who are already doing this months ago using dangerously skipped permissions pretty much 100% of the time.”

Social proof for a controversial stance. Naming real people elevates credibility.→ newsletter pull-quote

§ · Pacing

How they spent the runtime.

Hook length60s

Info densitymedium

Filler15%

§ · Resources Mentioned

Things they pointed at.

02:14toolClaude Code remote control

02:24toolCursor Cloud Agents

02:27toolReplit mobile app ↗

02:28toolLovable mobile app ↗

04:20toolAmp coding agent

07:00toolOpenAI Codex desktop app

07:54channelPeter Steinberger

07:56channelRiley Brown

11:37productschool.com/aiapps ↗

§ · CTA Breakdown

How they asked for the click.

11:37product

“If you are building with AI and you wanna build apps and software that actually work and launch to real customers, I have got a community helping people do just that over at school.com/aiapps.”

Soft sell - mentioned twice (60s and 11:49). No hard pitch, no price, just community size (250+) and outcome promise. Low friction.

§ · The Script

Word for word.

HOOKopening / re-engagementCTAthe pitchmetaphor

00:00HOOKWipe coding has changed a lot in the last year. But in the last few weeks, it's changed more than some of you might realize. And most people don't know that this is happening. So in this video, I wanna break down the five big shifts that are happening in vibe coding today so that you know exactly how to build with AI the right way going into the rest of 2026.

00:18HOOKCTASo in this video, we're gonna break down the five shifts that are happening in vibe coding right now, what the future of building with AI looks like, and how to actually apply these lessons to your vibe coding or AI coding workflows today so that you can be ahead of 99% of other people. If you don't know me, my name is Chris. And for the last fifteen years, I've been designing apps and advising startups and products and design. If you are interested in building real applications and software with AI and you wanna learn how to do that and launch to real customers, I've got a community helping people do that and you can find out more by clicking the link in the description down below. Otherwise, let's jump in and break down the five big shifts happening in coding. And number five is gonna completely change the way that you build. So the first big shift that is happening in vibe coding today is moving from AI coding inside of an editor or an IDE to AI agents that are coding anywhere.

01:10CTAAnd what I mean by this is being able to access your coding sessions through multiple different agents from anywhere that you are, whether you're out and about and you're accessing your agents on your phone or whether you're sitting at your desk and using your laptop. And not only that, but being able to use agents inside of different environments as well. So not just inside of an IDE or a coding environment, but being able to access your agents from inside of terminals,

01:35inside of other apps, and to communicate between different apps as well. Now most of these big shifts are taken from the recent release of AMP's new coding agent and what they see as their vision of the future of AI coding agents and how people are gonna use them over the next year and beyond. And AMP took their previous coding agent. They almost completely scrapped their entire product and rebuilt the entire coding agent from the ground based on first principles and what they saw as the future of AI coding. And if you wanna explore some ways of leveraging this first big shift in vibe coding and being able to go from AI coding inside of an editor to AI agents that are able to code anywhere,

02:14there are few things that you can start using that you can start looking at in order to improve the workflow that you already have. Tools like remote control from ClaudeCode, Cloud Agents from Cursor, and even the Replit and Lovable mobile apps. And not only that, we're also seeing connections happening between different environments like the terminal and your phone. So you're able to kick off a coding agent inside of the terminal and then carry on working with that coding agent on your phone until you get back to your desk and you can continue in the terminal. So these sessions for AI coding agents are actually transferable

02:48across different environments and different devices as well. This means that you're not just tied to coding at your desk on your laptop, but if you wanna take your coding sessions elsewhere, whenever you go out, whenever you go to lunch, whenever you're working away from your desk, you can do that with these tools. So wherever you're vibe coding or coding with AI agents,

03:07look at the features and the options that they have there to use cloud based agents in order to continue your vibe coding work when you're not sat at your desk inside of an editor. The second big shift that is happening in vibe coding is going from monitoring your own context to context auto compaction. And if you've spent any time in AI coding tools, you know that that context bar fills up pretty quickly and you have to keep on top of the context that is going into your chat so that the results you're getting from your AI coding agent don't suffer and the output quality isn't super low. But that is soon gonna be a thing of the past. All of the frontier models and all of the leading AI coding agents in the world right now are developing systems

03:49where they can auto compact memory and context in a conversation in a way which maintains the critical parts of your conversation, doesn't use up a load of tokens, and also doesn't suffer from context rot which happens over an extended session where you have context compacted on top of each other multiple times and you lose all of that critical information that you need in the work that you're doing in that session. Now this is one of the things that AMP's new AI coding agent is claiming to be able to fix with this auto compaction.

04:18And we're gonna see more and more of these frontier models and AI coding harnesses adopt auto compaction as a default technique to maintaining context throughout a long conversation without the user having to keep constantly starting new conversations or new threads, which also presents its own problem because that means the agent has to go and reread the the code base in order to get an understanding of what you're actually building and working on every time you start that new conversation. And so auto compaction is just gonna make it easier and easier to continue a long running thread or series of chats where you don't have to worry about managing the context yourself.

04:53The AI agent is gonna be able to do that. So a great way to think about how you can use this today is are you spending a lot of time on context management? How can you reduce the amount of time you're spending on context management? And how can you start to trust these AI agents with auto compaction a lot more than you used to, and to be aware that when these things come out and when these features are released in these AI coding agents, they're gonna enable you to work even faster without worrying about how you manage the context for those agents. Big shift number three in vibe coding is going from send, wait, and review to being able to stack the queue. And what I mean by this is that as AI coding agents get more and more competent and successful

05:36at completing these tasks, especially smaller, more straightforward tasks, the easier it is to begin to queue up a lot of prompts, a lot of changes in a row as a sort of backlog or to do list for the AI agent to actually go and complete without worrying too much about context switching or whether the AI agent is actually gonna complete that task at a high enough quality. Now previously, a lot of best practice for coding and vybe coding with AI coding agents is about making a change, building a feature, and then doing regular code review in order to maintain the quality of the code that is written by the AI agent. And so all that this means in the long run is that you're gonna start to see that window increase,

06:17whereas you build with AI coding agents, you're not gonna need to do code review as much. You're not gonna need to review the code that it's writing as much. And you're not gonna need to keep waiting to actually fix any of the issues that come out of that code. Now, this can combine really, really well with actually a very rigorous bug fixing and code review process. And you can even automate this where if you're working on a lot of codes during the day, if you're building an app or building anything where you're vibe coding with these coding agents, to set up automations where at the end of each day, it automatically goes and reviews the code that it's written that day, identifies any bugs, plans how to fix them, and then fixes them for you before you start work the next day on the next set of features that you wanna build. And you can see this playing out inside of the new Codex desktop app from OpenAI,

07:04where when you submit a message to the coding agent and then you send follow-up messages on top of that, it actually stacks them in a line on top of each other where you can drag those messages around inside of the queue and you can send those messages straight to the agent directly to interrupt its chain of thought and actually steer the AI agent in the process that it's already working on. And if you wanna start using this today, then start using something like the Codex desktop app and start getting comfortable with submitting those series of tasks and prompts on top of each other in a queue that the AI agent can work through one after the other without you having to directly supervise every single thing that it's doing. Big shift number four in vibe coding is going from approving every request and every permission to letting the agent cook. And there are people who are already doing this months ago like Peter Steinberger,

07:54Riley Brown, and many others in the vibe coding and AI coding space where they were already using dangerously skipped permissions pretty much a 100% of the time. And the reason that this is happening is because of two things. First is the increase in the quality of the reasoning of the AI coding agent and that it can actually make better decisions as it's going through step by step trying to identify what it needs to do in a plan and actually build out the feature or the application that you're working on for you. And the second reason this is happening is because now with sub agents and all of these different processes and reasoning steps that coding agents are running,

08:28there are just a vastly increased number of tool calls and permission requests to the point where if you are manually approving those permissions, you can just sit there hitting yes yes yes yes approve constantly until the AI agent actually completes its work and 99% of those approvals actually didn't need your input at all. And this is part of the reason why Anthropic and OpenAI have introduced the auto review modes as part of their coding agents. And the way that you can start using this today is to start working with these auto review modes for these coding agents to actually lower the permission levels that you have set as default in the coding tools that you're using and to trust the agent and the model more in terms of what it's actually doing. And the final shift here in Vibe coding is is going from one project and one stream to multiple projects and multiple agents running at the same time. And part of being able to do this is actually just a skill issue in terms of how you use these AI coding tools. It's about building up the confidence to give these AI coding agents a bit more free rein in the tasks they're doing, to feel comfortable working across multiple projects, multiple folders at the same time, and to understand how you can orchestrate multiple agents across different sets of tasks where they aren't gonna interfere with each other in terms of writing code to the same files and features inside of your code base or creating conflicts and bugs that contradict each other. An easy way to start doing this is to think about what tasks can I do inside of my project that aren't necessarily to do with writing code? Maybe I wanna create a launch video for my app idea, and I actually do that inside of my code base because the agent will have context of the app that I'm actually building, and then you can use a skill like hyperframes to be able to build that launch video for you. You could also do things like conducting research,

10:15building context files, and turning code into a number of other assets including websites, social posts, business strategies, presentations, spreadsheets, and a whole load of other things. And you can do all of this inside of these AI coding tools, especially now with tools like the new Codex desktop app from OpenAI, which is as good of a tool for just general purpose knowledge work as it is for writing any code or building software and application. And so how you can get started with this today is to start using something like the OpenAI Codex PAP and start running multiple agents in multiple projects with different types of tasks. And not only that, but you can think about how do I turn the projects that I'm working on into a folder on my computer which have a set of markdown files that give the agent context of what it needs to build, and how do I install the right skills

11:03CTAinto those projects to allow the agent to be able to do a whole set of other tasks like creating video, editing video, creating images, social posts, building websites, and all of the stuff that I mentioned previously. And so those are the five big shifts that are happening in VIVE coding and AI coding right now. And so if you're building with AI, you need to be aware of these things. What is happening in the AI coding space and how to adjust and change your workflows so that you're building skills are not only gonna be relevant now, but are gonna be relevant for the future of AI coding. Now I'd love to know which shift you think is gonna be the biggest of these and if you're leaning into any of these shifts already. And if you are building with AI and you wanna build apps and software that actually work and launch to real customers, I've got a community helping people do just that over at school.com/aiapps.

11:49CTAYou can find out more by clicking the link in the description down below. There's over 250 people inside that community who are building real applications and have launched to real customers. If you enjoyed the video, don't forget to like and subscribe. Thank you for watching, and I will see you next time.

§ · For Joe

Steal the five-shift frame.

Build Great Products playbook

One bold provocation plus five numbered shifts plus one concrete tool per shift plus one action per shift equals a 12-minute talking-head that holds attention with zero B-roll.

Lead with a funeral: declare something dead. The provocation is the hook.
Each shift needs a villain (the old behavior) and a hero (the new behavior). Name them explicitly.
Ground every shift in one tool people can install today. Abstract gets skipped. Specific gets subscribers.
End each shift with a start-today action - even one sentence. It transforms advice into instructions.
For Joe: the multi-agent shift maps directly to JoeFlow and Claude Code Sessions. That angle is yours to own.
The skill issue framing is a steal: stops the listener from blaming the tool and puts them back in the driver seat.

§ · For You

Two habits worth changing today.

If you already build with AI

Most of the friction in AI-assisted development is self-inflicted - you are still treating a 2026 agent like a 2023 autocomplete.

Queue your tasks. Instead of sending one prompt and waiting, write three to five tasks in a row and let the agent work through them.
Lower your permission guard. If your tool supports an auto-approve or reduced-permission mode, try it for a focused session. Most approvals are noise.
Let sessions continue across devices. If your tool has a mobile or cloud component, try picking up a session on your phone. The continuity is real.
Treat the agent as a general-purpose knowledge worker, not just a coder. Research, outlines, strategy docs, video scripts - all valid tasks in the same queue.

§ · Frame Gallery

Visual moments.

open - FUD hook

Frame at 00:13 from Vibe Coding is Dead. This is the Future

agenda slide

Frame at 00:31 from Vibe Coding is Dead. This is the Future

Frame at 00:40 from Vibe Coding is Dead. This is the Future

Frame at 00:49 from Vibe Coding is Dead. This is the Future

§ · Watch next

More from this channel + related dossiers.

Build Great Products · Tutorial

How to Build ACTUALLY Beautiful UI With This Claude Code Skill

A 12-minute demo proving that two install commands and one prompt can take your AI-built UI from generic purple gradients to near-professional design.

November 18th 2025

Build Great Products · Tutorial

Claude Cowork Just Changed the Game

Chris Ashby 5-tip walkthrough of Claude Cowork — Claude Code with a GUI — ending in a live 15-minute app business plan built end-to-end.

January 13th 2026

Simon Scrapes · Tutorial

Claude Code has a new UI (pair it with Claude OS)

A 5-minute walkthrough of Anthropic's native Agent View TUI and how it slots into a folder-based Agentic Operating System.

GosuCoder · Review

Claude Code is so freaking good

318 commits in May. One outline canvas. One creator's honest pricing breakdown.

Alex Finn · Tutorial

5 Secret Claude Code Features You Need to Know About

A 12-minute tutorial covering slash commands, sub-agents, hooks, think modes, and CLAUDE.md rules — each delivered as a single copy-paste prompt.

Theo - t3․gg · Talking Head

I'm Addicted to Claude Code (i get it now)

Theo goes all-in on Claude Code over the holiday break — six parallel instances, no IDE opened, two projects from scratch — and comes back with a changed worldview on writing code.

January 6th 2026