GitHub Copilot for JetBrains Lets Developers Re-Edit Earlier Messages

GitHub CopilotSep 22, 2026View original changelog

GitHub Copilot for JetBrains now lets developers edit an earlier message in an agent session, rewinding both the conversation and any file changes made after that point before continuing from the corrected prompt. The feature addresses a common failure mode where an early vague instruction sends an agent down the wrong path for several turns before anyone notices. It shipped September 22, 2026 in the same release as JetBrains' new AI-assisted tool approvals.

Key Takeaways

Developers can now edit an earlier message in a GitHub Copilot for JetBrains agent session instead of only revising the latest prompt.
Editing a past message triggers Copilot to rewind both the conversation and any file changes made after that point before resuming from the new prompt.
The feature addresses a common failure mode in long agent sessions: an early vague instruction sending the agent down the wrong path for several turns before anyone notices.
It shipped in the same September 22, 2026 release (version 1.18.0) as GitHub Copilot for JetBrains' new AI-assisted tool approvals feature.
The rewind behavior means developers can correct course without losing useful earlier progress or starting an entirely new session.
The update brings JetBrains agent sessions closer to rollback and editing parity with controls already familiar from other Copilot surfaces (e.g., Copilot CLI's rewind feature).

Sources & Mentions

1 external resource covering this update

New features and improvements in Copilot for JetBrains

daily.dev

Re-Edit Earlier Messages Without Losing ContextGitHub Copilot for JetBrains now lets developers revise an earlier message in an ongoing agent session instead of only being able to edit the most recent prompt or start over from scratch. When a developer edits a past message, Copilot rewinds both the conversation and the file changes made after that point, then continues from the edited prompt as if the intervening steps never happened.

Why It MattersLong agent sessions can drift: a vague early instruction sends the agent down the wrong path several turns before anyone notices, and by then unwinding just the code changes without also resetting the conversation state used to make sense of it leaves a session in an inconsistent state. Rewinding both together means a developer can correct course mid-task without losing everything useful the agent already produced earlier in the session, and without spinning up an entirely new conversation and re-establishing context from scratch.

Shipped Alongside Broader Agent ControlsThe change arrived in the same September 22, 2026 release of GitHub Copilot for JetBrains (version 1.18.0) that introduced AI-assisted tool approvals, giving developers more ways to steer and correct agent sessions without abandoning them.

Mentioned ondaily.dev