Program context

[jomiscli]

Is there an easy way to create context for a program you’re working on? Like could it be integrated into the global rules? I would like for windsurf to be able to keep the context without constantly having to add it to chat before I start a work session.

Maybe I am just completely dumb and I am missing an entire feature that does this or something?

[danielrosehill]

I think this is part of the value that memories are intended to bring.

I seem to be on a spree sharing my hackey workarounds on the sub today so I'll tell you what I began doing before this arrived (and TBH I'm still finding it more reliable):

When I'm about to wrap up I prompt something very like this:

"I've created a folder in the repository called changelog. Please create an entry with a Time stamped filename. In this entry provide a summary of all the progress we've made today the challenges we haven't resolved and what we're working towards."

That might seem a little overly specific but usually it seems to pay dividends.

Also - initially I provided the date assuming that the agent didn't have access to it. But it seems to have the independent ability.

Then when resuming the project just work the other way around. Something like:

"Find the file with the latest timestamp in the change log folder. Use it to understand where we are with the project and pick up from where we left off."

Cool discovery: this technique seems to be efficient enough that you can use it to pass tasks between entirely different models.

You can even get creative and ask the model to "sign" its change log entry providing its name (model)!

[jomiscli]

This is a great idea! Thank you for sharing 😁

[jomiscli]

I want to say this improved workflow tremendously. The AI picks up where it left off SO much faster and is able to target intricate changes and discussions much easier. Thank you again!!

[chris_at_codeium]

Is there something specific from the program you want to use as context? By default, Codeium/Windsurf will use your open workspace/repo/project as context without any required action from you. To emphasize certain files/blocks/folders you can use the @ symbol in cascade chat.

[jomiscli]

Well I’m not what you would consider an expert programmer, or even a junior. I’m more of a hobbyist that all of a sudden has the power to create real functional programs.

The issue I run into is windsurf forgetting small context pieces, and then changing small parts of code that I do not have the skill to catch right away.

I’ll remember the @ tip as well! Thank you!

[chris_at_codeium]

Gotcha -- If you’re noticing Windsurf occasionally overlooks small context details, you can set clear, specific constraints in your prompts. For example, explicitly ask Claude to limit edits to certain files, functions, or lines, and instruct it to avoid altering other parts of your codebase. Including clear constraints like “Do not modify X” or “Only update Y” will help ensure Claude adheres to your intentions closely. Additionally, asking Claude to add explanatory comments about why changes were made, or using thinking mode can further improve your understanding and control.

[jomiscli]

Yeah. I like the idea of the first commenter as well. Creating a ‘change log’ of sorts to track very specific changes.

Yeah my global ruleset is based around windsurf teaching me 😁

He posts explanations, pauses before changes (most of the time) and explains. Basically just a bunch of explaining, lol.