[Feature Request] Integrate with VS Code "timeline" functionality
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other:
- Claude CLI version: 1.0.11
- Operating System: mac OS
- Terminal: VS Code integrated terminal
Description
Now that Claude Code has a VS Code extension, it would be awesome if it could hook into the "timeline" feature in VS Code. Normally, whenever a file is saved in VS Code, an entry is captured in the timeline which allows for quickly restoring the file to a previous version if necessary. However, editing a file via Claude Code does not store an entry in the timeline.
When rapidly iterating via Claude Code, it would be super useful to be able to revert a file to a previous state if Claude decides to go in the wrong direction.
Update: it appears that the VSCode Timeline API is still not finalized, which means that custom timeline integration won't be possible if the Claude Code extension is to be published in the VSCode Marketplace.
However, I believe there are workarounds available such as having the Claude Code extension itself call .save() on the edited document or making some kind of small change to the file then reverting it and saving the file (add a space, then remove it and save the file) whenever Claude makes an edit.
@jpitchell I think a better link to the matter of Timeline API still being stuck in "proposed" state is https://github.com/microsoft/vscode/issues/84297
I'd be grateful for whatever lobbying the Anthropic folk can do to persuade the VS Code team (in particular @lramos15) to finalize this valuable API and thus unlock it for all extension developers.
This is a huge issue and frankly stopping me from being able to feel comfortable using Claude Code. I'm surprised a workaround hasn't been found yet.
I agree, been using Claude for a few weeks and have really missed this feature. Timeline was very useful before LLMs, and would be eve more so now. Claude just corrupted a file it tried to modify, and it advised me to revert to git. Unfortunately I had a week's worth of refactoring after git that may be compromised.
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.