👉 Note: The full sized composer has been removed and is now full integrated into the sidebar (v0.43)

Hey, welcome back! We’re going to focus on actions and bulk actions within Cursor’s Composer. These features help you manage changes while working on your code, giving you control over what gets saved, rejected, or finalized. Once again, let’s use the same pancake recipe script from the previous lesson. This script gives us the ingredients based on the number of servings. Let’s say you added a pinch of cinnamon to the pancake recipe but weren’t sure if you wanted to keep it. You save the changes using Save All and run the code. If you decide it’s not working, you can reject the changes using Reject All. But then, after some thought, you realize the cinnamon was a good addition after all. Instead of typing everything out again, you can hit Reapply, and your cinnamon ingredient will be restored to the recipe. You can then accept it once you're certain. Once you’ve made changes in Composer but you’re not yet ready to finalize them, you can hit Save All. This will temporarily save the changes to the file system without permanently committing them to the codebase. But what if things didn’t go as planned? Maybe the changes you made broke the code or just didn’t fit your needs. That’s where Reject All comes in. This button discards all temporary changes, rolling your code back to its previous state. Now, here’s where Reapply comes in. Sometimes, after rejecting or temporarily saving changes, you might want to bring them back later for testing or further modification. The Reapply feature allows you to reintroduce those changes without having to regenerate or manually re-implement them. Now, if the changes you’ve made are working perfectly, and you’re happy with how the code is functioning, you can hit Accept All. This will take the changes from temporary storage and permanently write them into your codebase. To wrap up, the Save All, Reject All, and Accept All features are super useful for managing your coding process. You can make quick changes, test them, and decide whether to keep or discard them—all without disrupting your workflow. Using Save All temporarily stores your changes in the file system, but they won’t be committed to the codebase just yet. When to Use Save All: when you’re testing new features and want to keep the current state without finalizing it or when you want to pause your work and return later to continue from where you left off. When to Use Accept All: once you’ve tested the changes, and they’re good to go, or when you’re confident that the modifications fit your project and need to be part of the main code. When to Use Reject All: if your modifications didn’t work as expected or when you want to discard experimental changes and return to the last stable version. When to Use Reapply: when you’ve previously rejected changes but want to try them again after making other updates or if you saved changes earlier but now want to apply them and continue refining the project. These features give you full control over your project, making it easier to experiment and refine your work. In the next lesson, we’ll look at how to manage more complex project setups using Composer. Let’s keep going!