Are Task Implementor buttons making the wrong thing the easy thing?

[jdhines]

The docs clearly say it's important to use /clear between tasks, but then the UI provides easy one-click buttons to go to the next task:

When using these buttons the chat is not cleared, so my question is: should they even be there if do what the docs specifically say not to do? Or do the buttons actually clear the context (but just keep the previous discussion above)?

[WilliamBerryiii]

@jdhines - fair feedback. The docs take precautionary measures as the GHCP extension conversation summarization and the compaction routines have been changing with significant frequency since November. We've tried to encourage people who are new to the repo (e.g. reading the docs), to be overly cautious with context and token management by suggesting a clear (and the instructions do as well), but for the power users, having the buttons gives more of a flow space experience. I'd like to get this all synchronized, but I just don't think we're there yet with stability in the VSCode GHCP extension. Thoughts?

[jdhines]

Good to know; I'm running in enterprise, so tokens not really an issue. I appreciate the flow and also it not having it clear the chat history, which actually I don't like, because sometimes there's things there I want to read (I know there's all the output files, but sometimes those are hard to scan). I just wanted to make sure I wasn't shooting myself in the foot if I use the buttons to flow to the next phase.