Pre-caching context overhead (system prompt, tools, skills, ...) ?

<!-- SC_OFF --><div class="md"><p>I actually make some tests with lm studio and Opencode with the new Gemma 4 26b model.</p> <p>The results are really impressive especially on

<!-- SC_OFF --><div class="md"><p>How do you guys deal with long context, for example while coding, when you’re going back and forth for adjustments or fixing some errors and

<!-- SC_OFF --><div class="md"><p>As the title says. I don't think it's normal to invalidate 100k of context cache for no reason. For example Cline and Qwen code addon for VS code

<!-- SC_OFF --><div class="md"><p>Curious to hear how long you guys are waiting for a long context session(100k tokens+) to resume in coding agents running locally. </p>

<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1s2bne8/context_shifting_sliding_window_rag/"> <img alt="Context Shifting + sliding window + RAG"

<!-- SC_OFF --><div class="md"><p>Model size gets a lot of attention. I believe the real difference between a frustrating and a great local LLM experience comes from everything

<!-- SC_OFF --><div class="md"><p>Been using ClaudeCode CLI with Opus 4.6 and many MCP's and honestly its addicting. </p> <p>Just tell it what to build and it does everything —

&#32; submitted by &#32; <a href="https://www.reddit.com/user/phantom69_ftw"> /u/phantom69_ftw </a> <br /> <span><a