[6Az4Mj4D]

Can you please share your Claude usage workflow?

I use Github copilot and often tend to be frustrated. It messes up old things while making new. I use Claude 4 model in GH CP.

[fzzzy]

I use github copilot chat right now. First I use ask mode to ask it a question about the state of the codebase outlining my current understanding of the condition of the code. "I'm trying to x, I think the code currently does y." I include a few source files that I am talking about. I correct any misconceptions about the plan the llm may have and suggest stylistic changes to the code. Then once the plan seems correct, I switch to agent mode and ask it to implement the change on the codebase.

Then I'll look through the changes and decide if it is correct. Sometimes can just run the code to decide if it is correct. Any compilation errors are pasted right back in to the chat in agent mode.

Once the feature is done, commit the changes. Repeat for features.

[ghm2180]

I also do the same. I am on the 200$ maxpro plan. I often let the plan go to pretty fine level of detail, e.g. describe exactly what test conditions to check, what exact code conditions to follow. Do you write this to a separate plan file? I find myself doing this a lot since after compaction Claude starts to have code drift.

Do you also get it to add to it's to-do list?

I also find that having the o3 model review the plan helps catch gaps. Do you do the same?

[6Az4Mj4D]

Does it remember context from chat mode and when you switch to agent mode?

[csomar]

GitHub Copilot models are intentionally restricted, which unfortunately makes them less capable.

I'm not the original poster, but regarding workflow, I've found it works better to let the LLM create one instead of imposing my own. My current approach is to have 10 instances generate 10 different plans, then I average them out.

[mkozlows]

Github Copilot is weirdly bad, and all the alternatives are better. Sometimes people think "they have the same model, must be the same," but it's not.