GitHub Copilot CLI: Rewind Without Git

GitHub CopilotAug 7, 2026View original changelog

GitHub Copilot CLI's /rewind command no longer requires an active Git repository, letting developers undo an agent's changes to conversation history and files even outside version control. The update preserves any edits made after the rewound point, giving Copilot CLI a consistent safety net regardless of a project's underlying repository setup.

Key Takeaways

/rewind no longer requires an active Git repository, letting developers undo Copilot's changes even when working outside version control.
The command restores both conversation history and the specific files Copilot modified, rather than reverting the entire working directory.
Edits made after the rewound point are preserved, so developers don't lose unrelated work when undoing an agent's changes.
The update closes a known pain point raised by developers using Copilot CLI in non-Git or alternative-VCS projects.
It ships alongside the new /worktree command and Sessions sidebar, part of a broader push to make the CLI safer and easier to manage during long agentic sessions.
No configuration is required — the Git-independent rewind behavior is available automatically in the latest CLI release.

GitHub Copilot CLI's /rewind Command Now Works Without Git

GitHub Copilot CLI's /rewind command no longer depends on Git, closing a long-standing gap for developers who use the CLI outside a Git repository or with an unsupported version control system.

What Changed

Previously, /rewind — the command that lets developers roll back changes an agent made during a session — required an active Git repository to function, since it relied on Git's history to restore file state. With this update, /rewind can restore both the conversation history and the specific files Copilot modified, independent of Git, while preserving any edits made after the rewound point.

Why It Matters

Not every project Copilot CLI touches lives inside Git — some developers work against other version control systems, generated scaffolding, or plain directories. For those users, an agent making unwanted changes previously meant no safety net for undoing them. Extending rewind to work without Git gives every Copilot CLI session the same undo capability, regardless of the underlying repository setup, and reduces the risk of running agentic edits on directories that aren't backed by version control.

Availability

The Git-independent /rewind is live now in GitHub Copilot CLI, shipping alongside the new /worktree command and the multi-session Sessions sidebar as part of the CLI's August 3, 2026 weekly update.