Refactoring von Legacy-Codebases mit Cursor: Vier-Stufen-Workflow

[00:00] Hi. It's so good to see everyone. Thank you all for joining. Um if you are in refactoring legacy codebases with Cursor, you are in the right place. I am Amrita. Um I'm going to be one of your hosts today, and I'm joined by the lovely Regan. Regan, do you want to do a quick intro? [00:18] Hey everyone. I'm Regan. I'm also one of the field engineers here at Cursor. [00:23] Amazing. And then we're also joined by Ronnie who's going to be off camera, uh but she's our basically our our workshop magician. She organizes all of these workshops for us. And so if you want to see more Cursor workshops, go to cursor.com/workshops, um and you'll see the full list of both previous and upcoming workshops that are happening. Um cool. I'll let folks trickle in, and we'll get started in a couple minutes. I do love uh if people can share where they are calling in from. Um it's nice to see how many corners of the earth that Cursor reaches. But yeah, happy to have you all here. Thank you for joining, whether it's morning, evening, afternoon for you all. Uh we're going to get started in a couple minutes or so. [01:30] Okay. Amazing. I'm seeing Dolomites, I'm seeing Tennessee, Vancouver. Joining from India, amazing. Love seeing this. [01:50] All right. For folks just joining, we're going to get started in just a minute or so. Um I am Amrita. I'm joined by my colleague Regan and Ronnie who will be off camera. And we are hosting Refactoring Legacy Codebases with Cursor. Uh today's session is going to be pretty interactive, so I actually recommend folks have Cursor up on their machines with me while I'm going through some of these and trying out all of the little different, you know, tools and features that I'm going to be using. Um but with that said, I think we should probably kick it off. Um this meeting is being recorded and we will send out the recording, um I want to say within a couple days or so. Look out for a email from Luma. And then for folks who maybe have attended previous workshops, the recordings are coming. We just have a ton in our little backlog, so keep an eye out for those as well if you have attended some and have not gotten the recordings just yet. Okay. Let's kick it off. Um hi everyone, I'm Amrita. Uh I am going to be leading the workshop today. If you have any questions, please feel free to put them in the chat and Regan is actually going to be curating them and I'll be stopping here and there um for uh just answering anything that comes up. Uh as you can see, this is a bit of a more advanced uh AV setup than what I'm used to, so it's why I keep looking between my laptop and the camera. If it's you guys don't know where I'm looking, um if you've attended my previous workshops, they were a lot less professional. So thank you Cursor IT. Um awesome. I'm going to get started and show some slides, and then we're going to dive into the product. [03:25] Okay. So today's session is about Refactoring Legacy Codebases. And I want everyone today to leave today's session with two main takeaways. And actually before I forget, let me make sure I am recording, one second. Oh yes, I think I am. Um so the first question is what are the best ways to refactor, you know, legacy codebases with AI? And then the second question is why use Cursor to do it? And I actually want to switch the order of these two questions today, because the first one I'd like to answer with slides and show you all a little bit of what makes Cursor special. And then the second one is a little bit more of a demo rather than just talking because I'm actually going to migrate a couple of components with you all and show you the best ways to do it with Cursor. So for context, I was a software engineer, uh before I was a field engineer here at Cursor and so, I've used a lot of AI tools and there's a lot of great AI tools out there. Um and today I want to speak a little bit as to what makes Cursor different and why I like to especially do really large migrations, refactoring, any work basically in monorepos or multiple services within Cursor specifically. If you haven't used Cursor maybe in the last six months or so, this might look new to you. This is the agents window. And this is what we kind of see is the future of development with Cursor. Um as you can see, your agents kind of live off to the side in their, you know, uh repositories and then in the middle is the agent or the chat where you actually talk to Cursor. You can pick your models and you can work across different repositories. You also have the option in Cursor to use the IDE, as well. Um so this is where Cursor started and this is where a lot of developers still choose to stay. Uh it's a fork of VS Code. So if you like the VS Code debugger, if you like extensions and having the terminal kind of up on the bottom there, then this is a great place to work. We also have a CLI, which a lot of folks might not know about. Uh the Cursor CLI is great if you want to preserve any tmux workflows, if you want to work in some IDEs like maybe Android Studio or Xcode that don't have a native Cursor solution just yet. Um and so the Cursor CLI is available. It's on our website, you can download it and use it, and it's very similar to any of other, you know, TUI AI products that you've used. And then lastly, this is actually where we're going to be spending most of our time in today. We have the Cursor Cloud or Cursor Cloud Agents. And this is a really great way to use Cursor because basically, these agents operate autonomously and they operate on remote machines, meaning that I can launch an agent and close my laptop and the agent will still continue to run. And that's really great for these long migrations or refactoring projects which you have to do a lot of, you know, back and forth with the agent. With the Cursor Cloud, you can actually just send off a large agent like we're going to do shortly and have that agent work on refactoring until it's finished and prove that it's actually done what it's supposed to with videos, screenshots and testing. So the Cursor browser is where we're going to actually be showing some of this today, but there are other places where you can use uh the Cursor Cloud agent. A very common way that we use it at Cursor is actually with Slack. So you can see here we actually have a cursor agent that lives inside of our channel that is able to check whether our, you know, documentation online goes out of sync with our implementation. And this is really great because it can open up a PR, it can have someone review it, and it automatically gives you just visibility into what Cursor is doing without you ever having to open the Cursor app or the browser. And then the last place that you can use the Cursor Cloud, um is the mobile app. So we have a Cursor mobile app. It's available on the App Store, just for iOS right now, Android coming soon. And you can navigate through all your agents, you can pass off your agents from local to cloud and then work on them from the app, uh wherever you are, and it's a really great way of again, you know, taking a step back from your laptop, closing it and then working with your agents completely remotely from your phone. Now, another thing that makes Cursor special is its model flexibility. So I think a lot of you folks know this, but Cursor offers all the models from all the frontier labs right now, in addition to a lot of the open source models as well. So Kimi, GLM, um and then obviously our own in-house models, Composer being one of them and then Grok 4.6 actually being the latest and greatest of them all. Grok 4.6 was actually released, I want to say yesterday, um and it was or it is an amazing model. You can see how it's benchmarked here, compared to a lot of the other frontier labs on a various set of benchmarks that are kind of published to external third parties. Um so you can see here that it's a really strong model, but I think what also makes Grok really powerful is how cheap it is and how effective it is for such a powerful model. You can see here where Grok stands kind of compared to some of these other frontier models. So, it's a little bit, you know, more expensive than Composer and GPT which are more, you know, execution-focused models, but for how powerful it is and how, you know, capable it is of doing long-running tasks, it's very inexpensive compared to some of these other frontier labs. Uh so, we're going to be spending some time with Grok 4.6 today, and I'll actually show you and talk through when I decide to use it and when I don't, but I highly recommend if you haven't tried it yet to give it a go. With that said, um I like to talk a little bit about what makes model flexibility in Cursor actually effective. Um and this is the fact that you can combine different models to have a really good output for a very small amount of money. Um so this is actually a case study that we did at Cursor where we tried to rebuild SQLite from scratch. We have a great blog post about this, Regan actually, if you can put that in the chat as well. And we actually showed in this blog post that thanks to kind of our agent swarm, we were able to rebuild SQLite with this combination of models for much cheaper than if someone were just use Fable or if someone just use GPT 5.5. So kind of highlights the importance of having a wide range of models, um because models are going to do different things and they should be leveraged for different things. And so with this chart here you can kind of see how using one heavier-duty model for planning and one more execution-focused model for, uh actual writing code is really useful for your general budget. So now I want to talk a little bit about, you know, the Cursor harness is what we call it, but what lives between the platform, which we introduced Cursor with and the model. So the platform is basically all the different surfaces you can use Cursor, and the model is what I talked about, which is the LLMs that Cursor can, you know, leverage or delegate to. But in between all of those, we have what we called the Cursor harness, which is made up of all these different things. So, tool execution, cache management, dynamic context management, um context assembly, these all of these tools make it so that using these models in Cursor actually make it more powerful for refactoring large codebases or migrating from one version of SQL Alchemy to the next. And so that's why I really recommend trying out something like this within Cursor, because there's much more than just the model and the platform. There's also the harness that we provide on top of it. And if you want more technical details about the harness, feel free to check out this blog post from April, written by two of our lovely engineers and it goes a little bit deeper into what we do within Cursor to make it really powerful as a layer on top of the models that we provide. Okay. So that was a bit of a speed run through why Cursor, what makes Cursor special and what makes it different. Um now I'm going to talk about what are the best ways to actually do a refactoring with Cursor. And we're going to go through a couple steps today, uh four steps actually, which I've seen both internally for refactoring as well as what I've seen with customers. The first is we're going to use Cursor /canvas to audit our codebase and use Cursor Plan Mode to strategize what we're going to migrate. Then we're going to leverage plugins to actually take this plan that we've built and write tickets. So we're going to make actually a whole Jira epic of tickets for a migration from PHP to React. Then we're going to hand off those tickets to a Cursor Cloud agent, and this is where you're going to see how you can have a local plan and a local set of tickets that you've made, but then you can delegate them to these autonomous Cursor Cloud agents that can go off and work on them with your laptop shut, with you want to walk with you asleep, and then come back to you with the result. And then lastly I'm going to talk about automations in Cursor and how you can build workflows and tools to maintain a really good level of quality and stability for whatever you've refactored or migrated over. I finished this first part of slides. Regan, are there any questions I can answer before I go into the demo? [12:19] Uh yeah, there's a quick question on whether DeepSeek V4 Flasher Pro will be coming to Cursor hosted on US servers. I believe the answer is no, but correct me if I'm if I'm wrong about that, Amrita. [12:30] I don't think we have any plans for that one yet. Correct. [12:33] Cool. [12:35] Awesome. All right. So let's now get into the Cursor product. As I mentioned, please use uh please have Cursor up on your screen while I'm talking. I do feel like it makes it a lot more interactive and relevant for you if you're able to kind of follow along with what I'm doing. And you can do it with any repository, any folder, anything that you have already. Um but try and see if you can emulate any of the things that I'm doing because it'll make it a lot more valuable if you can see it on your own screen. Awesome. So today I'm going to be working actually in just a open-source repository. This is, um if you all remember WordPress, I actually had a WordPress account maybe back in, uh I don't know, when I was a teenager and, uh I used it to create blog posts. Um and it's a pretty, you know, old website. I'll actually open it up here in the Cursor browser so you can see it. So I cloned the WordPress repo and what I did is I just asked Cursor to run the the web app uh for WordPress in the Cursor browser. You can do that just by tagging @browser in Cursor and Cursor actually has a built-in browser that's able to run anything that from a full stack app to just a front-end app. Um and you can actually just open it up here. So I'm going to open up the browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. Um so I can see all my full stack WordPress app running up in here. And what I'm going to do actually is I'm going to do two things. I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan, where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React, which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. Um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in uh Confluence that it's able to pull on to make sure that all my plans look the same. Um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? Um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. Um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is running, I want to go back and show you the canvas that Cursor created. So again, this is a built-in tool within Cursor, um and Cursor is actually the only tool I know that has this, where I can open this canvas here and what I love about Cursor canvas is it can take any data. It can take files, Excel spreadsheets, you can give it data from an MCP. In this case, it took data from the codebase, and it creates these beautiful interactive visualizations that I can use if I want to present this to my leadership team, or if I want to just look and visualize things that usually is, you know, presented in just tables or raw data. So you can see here it creates this really nice table of, you know, the coverage by the different admin screens. And I love how it does this where it says, hey, these are the things I think you should migrate next, these are the things that you should do after and these are the components that are already in React. So it kind filters everything really nicely. Um it says here the places to add coverage, here the places with client JS that has no QUnit tests, and then this is the way to structure new tests. The cool thing about canvases as well is that you can actually modify them. So I can for example say make this a bar chart instead, instead and it can go ahead and do that. But I like using canvases as a way to audit codebases, I like using it as a way to again, print out test coverage docs or anything around coverage generally before I do a migration, because it's a really great way to again, visualize your codebase in a very fast and easy way. What's also cool about canvases is you can share them. So I can actually publish this, and now anyone who has the link to my canvas, so for example if I sent this to Regan, she can actually open it up in her browser and see my canvas and see any changes that I make to the canvas. So it's a living breathing document that is really easy to spin up, just use /canvas. Okay, so this is good data, I want to make sure that I take some of this into account, especially maybe the the screens that it's thinking of migrating next. I'll look and see if the plan covers any of these. I'm now going to go back to my plan here. Oh looks like it's asking me some more question. Hmm which legacy component should anchor the migration plan? This is a good question. I'm going to say the profile for now. Um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. Um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. Um so sometimes also, let me actually close this out. Um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? Um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. Um and looks like with the plan is almost done. It's refining the phased migration plan. Um in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. Um as you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here to have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. Um so I can see all my full stack WordPress app running up in here and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in uh Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [21:37] Yeah, one quick question, um opening the canvas in the browser. Do you mind just showing where you can find the click to copy link? [21:45] Absolutely. So I'm going to go back to the canvas here. um As you can see I published the link and I actually made this change where I made that from a pie chart to a bar chart. So I'm going to sync it. And then what I'm going to do is I'm going to copy the link right here. And I'll actually open it up in the browser for you guys. So I'm going to open up my browser, you can see it here. To have a little more real estate, I'm just going to close this side panel for now. But here I have the WordPress browser. um So I can see all my full stack WordPress app running up in here, and what I'm going to do actually is I'm going to do two things. So I'm first going to audit this codebase, uh and I'm going to see what tests currently are here and what can be improved for test coverage. And I'm going to use Cursor Canvas for that. And then at the same time, I'm going to work on a migration plan where a lot of these components are pretty old, um and they're all written in PHP. I want to migrate some of these components to React. So just so you all can see what I'm working with, this is kind of the the WordPress website. It's built in a mixture of PHP and React, but there's still a lot of legacy code here. So I'm going to work on migrating that legacy code over to React which is it's current modern framework right now. So what I'm going to do is I'm going to close this, and I'm going to open up a new chat, um and I'm going to do two things. So the first thing as I mentioned is I'm going to create a canvas, so I'm going to say create a /canvas. This is again, built-in skill, so you all should see it with me. Slash canvas is something that everyone should have access to. That analyzes test coverage for this codebase, highlights any gaps and presents the information to me about where I can add more test coverage if I migrate this to React this codebase to React. So I'm going to send that one off. You can see here it automatically starts running inside of my WordPress repo on the side here which I love. While that's working, I'm going to launch another agent, um and this is actually where I'm going to go into plan mode. So this is where I actually want to develop the strategy for doing the migration. In this scenario, I actually am going to change my model. I'm going to use uh GPT 5.6 soul. I love this model. It's a really great model for writing. I think it's actually a better writer, um our head of Dev rel actually said this. It's a better writer than Grok, um but obviously there's gaps in other places. But because I like its writing style, I like to use it for planning. So I'm going to go ahead here and say, um I want to migrate the components in this codebase say the legacy components of this codebase from PHP to React. I want to make sure that tests are added to verify no regressions have been introduced. I want you to draw a diagram of the current status quo technical architecture, and how that will change with the migration. Cursor is really good at drawing diagrams. um Cursor uses Mermaid diagrams as its base, but you can actually connect Cursor to Lucid charts, to Excalidraw, to FigJam, and have and have it actually print out its diagrams in any of those services. So I like to do that sometimes, but usually the the first mermaid diagram is a good place to start. So you can see here, uh for the plan, what it's doing is it's actually using my plan skill. This is a TDD template that actually lives in Confluence that it's able to pull on to make sure that all my plans look the same. um but before it's going to go and actually write the plan, what Cursor is very good at is getting direction from me early. So you can see it's saying, hey, legacy components is a little vague here, what scope should this design target? um and I'm going to say one screen for now, and then we'll do a reusable phased pattern. um and then sometimes Cursor will ask you more than one question, so it's kind of up to you how you want to customize that tool. It's called the ask question tool and you can make it so that it actually, you know, asks you at least five questions before it goes in and writes a plan. But the cool thing about plan mode as I mentioned is the output is a markdown file, it's a document. Cursor is never going to go in and actually make or write code in plan mode, it's only going to write you with strategy. So I'll let this run. While this is working, I want to talk about how you can have multiple agents up in Cursor at once. um so for example, you have one agent running but you want to look at another agent. You can actually tile your agents left and right here. So for your tmux users, you don't have to stay in the terminal, you can actually have something similar just like this, and you can see kind of if you have one agent running here, in the meantime, you can kind of look and see at your your other agent and how it's working. So very cool. I do this a lot when I have two long-running agents run side by side. um so sometimes also, let me actually close this out. um if I have a long-running agent and I want to see like, hmm what is it doing or why did it make this particular decision? um I can see actually more details by highlighting something, hitting add to side chat, and saying what exactly were these patterns? And this doesn't conflict at all with this parent agent, it's more so like a if you've used /btw in cloud code before, a easier more UI-friendly way of seeing that. So I love using that sometimes when I have a long-running agent, um because I can use it to kind of double-click on a particular part of the codebase or see kind of what's going on while my parent agent still continues to run. I'm going to close this for now. um and looks like with the plan is almost done. It's refining the phased migration plan. in the meantime, Regan, are there any other questions I can answer? [2