Copilot memory makes coding assistants more stateful
GitHub Copilot for JetBrains now has persistent memory, local model access through Ollama, more enterprise controls, everyday chat workflow improvements, and reliability fixes across MCP servers. This is not a broad frontier-model moment, but it is a useful shift: IDE agents are moving from one-off chat helpers toward remembered, governed work partners that can also touch local models. The immediate value is not JetBrains itself. It is the operating pattern. Test whether persistent memory improves repeat coding tasks without letting old assumptions leak into new work. Use a contained repo, define what Copilot is allowed to remember, and compare its next session against a clean-session baseline.