Memory, Local Models, and Execution Receipts Are Different Controls

GitHub Copilot is bringing three previously separate layers into JetBrains: cross-session memory, a local model provider, and agent execution records.

The August 11 update lets Copilot Memory retain and recall information across agent chats. Ollama is now available as a BYOK provider with provider configuration and model selection inside JetBrains. Codex sessions also appear in agent debug logs and support updated permission modes, instructions, and skills.

Those are different controls. Memory decides what survives into later sessions. Ollama decides where a model runs. Debug logs and permissions show what this run could do and what it actually did.

Enterprise settings now cover plugin availability, MCP server access, permission bypass behavior, and OpenTelemetry. The useful review is therefore four separate checks: memory scope, model source, permission policy, and execution receipt.

This is a read of GitHub's official changelog, not a local JetBrains reproduction.

Source: https://github.blog/changelog/2026-08-11-copilot-memory-and-ollama-in-github-copilot-for-jetbrains/