@fabgaliano@barb1709_@mattpocockuk Yeah for sure, if it’s getting a bit complicated, hard to trust the context alone.
Better to make a plan and make sure *that* gets it right.
Let’s say I didn’t make a plan and just used grill-me.
Then it starts implementing and as it does, it runs out of context. It will automatically summarise the context within that chat right?
So in that cause would it be better if the plan was a proper doc vs just chat history (which could be poorly summarised)?
@mattpocockuk What about when context needs to be summarised?
Wouldn’t a plan likely be a better record of the implementation details than whatever it summarises the context to?
It’s all vibes and there’s no science here so any thoughts?
@leerob Would be REALLY nice to be able to accept or reject changes and diffs in open files instead of just as part of the changes view (which often combines all changes in the branch)
It feels like composer 2 fast has similar speed to what regular composer models used to have
Cause non-fast composer 2 is slow which previous composer models weren't