option to have plans in git repo! yes!

💯% agree.

At a bare minimum

an immediate workaround:

add a Windsurf vscode command to view the current chat's

Why:

I work on a plan with Cascade, and approve it.

So, keep its internal musings in silent mode unless I click something to show them; named plans go in my project folder (in docs/plans would be best); switch plans when I say to.

Nowadays, almost for every new chat, a new plan.md document is created and that's not that valuable, I would think that those plans should evolve into an architectural document local to the project.

For example, if I have a project already advanced, I tell Windsurf to analyze everything, and build an MD document with the definitions of the project's architecture and complement it with the best practices of software development focused on the framework I am using in that project, plus SOLID, more clean code and that the document is well structured so that it is the absolute truth for decision-making in the new code.

This should make it automatic and you should always consult this document first so that you can make the most accurate decisions and not get lost in the architectural design of the project we are developing.

What do they think?

I agree with this but for now what I do is let it create the plan in the user directory and then when I like it I as chat to save the plan in my current workspace. It seems like if you let it copy the file there it doesn't lose track of it if you do a save as. I've only done this a couple of times though so experiences may vary.

Agree that this should be in the project/repo, not in some magic windsurf folder.

When working in an enterprise the plan for the repo IS the plan. All developers should be able to see it and act on it.

I could see options here where there is a repo level plan and as an individual you can have your own (whether in windsurf dir, or more likely also living in the project folder just gitignored) Something like ./plan.md and ./.user/plan.md or whatever needed to namespace it.

yeah, i also like it can be in project, i have seperate plan.md for diffferent project and i don't want them to interface, now ws force me mixed them, it's not good.

in windsurf it's just a tiny option, global(default)/project

mmmhh someone has learned from the data sent... the planning method is extraordinarily similar to our modus operandi that has always been with AI and these are the operations that we are going to do pre task and post windsurfing and all the other editors with AI, yes, as the comment says, it makes absolutely more sense to put the plan.md in the repository in the directory you want. So the trigger should be on the name/role of the file not on the keyword and position.

then users on workspaces with more than one repo, will have an issue with that. Plus, the plan is to keep track between you and your ai, not sure if I want my team to pull the plan.md and see how I get things done (albeit we can gitignore it), we have project management apps for that. Just my two cents,

Happy coding!

You can easily do a save as. The working plan.md has a lot of churn as cascade works thru the list. Maybe the step by step is what you want in your repo, maybe just the original plan.

That said, I have had cascade create a plan from a prompt, saved it, went to a new project and started the new conversation with “execute the plan in plan.md”. Mostly worked (it did try to skip one step). As you can tune a plan to a known state, vs hoping the LLM randomizer is nice to your prompt, I see the potential of having a library of cultivated plans.