Using a local 7B for chatting, I saw it tries very hard to check for inconsistencies of itself, and that may spill to also checking for the user's "inconsistencies".
Maybe it's better to carefully control and explain the talk progression. Selectively removing old prompts (adapting where necessary) - which also reduces the context - results in it not having to "bother" to check for inconsistencies internal to irrelevant parts of the conversation.
Eg. asking it to extract Q&A from a line of text and format it to json, which could be straightforward, sometimes it would wonder about the contents from within the Q&A itself, checking for inconsistencies eg:
- I need to be careful to not output content that's factually incorrect. Wait but I'm not sure about this answer I'm dealing with here..
- Before the questions were about mountains and now it's about rivers, what's up with that?
- etc..
I had to strongly demand it to treat it all as jumbled text/verbatim, and never think about their meaning. So it should be more effective if I always branched from the starting prompt when entering a new Q&A for it to work on. So this is what I meant by "selectively remove old prompts".
what work flow where you using to feed it code? was it cline? Cline has major prompting issues with DeepSeek, Deepseek really doesn't like you changing out its prompt with what normal LLMs are using.
