[FEATURE]:在恢复消息之前,预览受影响的文件并请求确认
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 35/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- git, typescript
- Bereich
- devtools
Rechercherichtung
Start with the revert flow that emits the session.revert.stage log event and see where it restores files from snapshots, since that is where a preview step would go. The config key snapshots in opencode.jsonc controls capture, so check it first when reproducing the empty repos directory. Done means a preview listing affected files appears before the rollback and can be cancelled, with the snapshots default behaviour settled or split into its own issue.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Feature request: preview affected files and ask for confirmation before reverting a message
Problem
When I use Revert from a message menu (or /undo), the files touched by later assistant steps are restored immediately. There is no way to see which files will change before the rollback is applied.
If the working tree contains edits made after that assistant step (by me or by another tool), those edits are silently overwritten. The docs acknowledge this risk:
Current edits to an affected path can be overwritten, so review the restored summary and
git diffbefore continuing.
But no "restored summary" is shown before the rollback happens, and git diff can only be checked afterwards, when the edits are already gone.
The revert is described as staged, but in practice only the conversation is staged (messages can be brought back with /redo) — files are restored right away, with no preview and no confirmation.
Steps to reproduce
- Open a session in a git repository with snapshots enabled.
- Let the assistant edit a file.
- Make an unrelated manual edit to the same file.
- Choose Revert on an earlier message (or run
/undo). - The assistant's change is rolled back and the manual edit is lost, with no warning.
Expected behavior
Before applying the rollback, show which files will be affected and ask for confirmation, for example:
This revert will change 3 files:
222/test.txt restored to version before step 4
src/new.ts removed (created by the reverted step)
src/api.ts restored to version before step 4
[Cancel] [Revert these files]
A concise git diff --stat style preview would already be enough.
Alternatives considered
/redoafter/undo— only undoes the rollback itself; it does not preview anything.- Checking
git statusafterwards — too late, overwritten edits are already gone.
Additional observation (possibly a separate issue)
In my setup, file capture did not work until I set "snapshots": true explicitly in opencode.jsonc.
Before that:
~/.local/share/opencode/reposstayed empty;- the log showed
session.revert.stage ... files=undefined; - no
snapshotentries appeared in the log.
The Snapshots docs say snapshots are enabled by default, so this may be a bug or a version difference. Happy to file it separately if useful.
Environment
- opencode
2.3.2 - OpenCode Desktop
- Git repository with at least one commit
snapshots: trueset explicitly
- Vorherrschende Sprache
- TypeScript
- Sterne
- 227k
- Forks
- 30.7k
- Ø Merge
- 3 Std. 57 Min.
- Gemergte PRs (30 T.)
- 484
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus anomalyco/opencode
-
[Site] Active section detection should respect scroll-margin-topEvtl. vergeben Ein verknüpfter Pull Request ist offen oder bereits gemergt. Offenarea/web reproduced type/bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
anomalyco/opencode#65384 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
area/cli type/feature version/v2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
anomalyco/opencode#65379 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Shell tool: no upper bound on the timeout a model can ask for, so one call can hold a turn for hoursOffenarea/core platform/linux type/feature version/v2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
anomalyco/opencode#65254 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
inference/go type/feature
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 72/100
anomalyco/opencode#65148 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
area/providers type/feature version/v2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
anomalyco/opencode#64845 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in anomalyco/opencode
Ähnliche Issues
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
vercel-labs/ui#999 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
melgarafael/DeskcommCRM#5109 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Doist/todoist-sdk-typescript#783 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 64/100
nicobailon/pi-subagents#3319 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag