|
|
@@ -1,5 +1,59 @@
|
|
|
# @kilocode/cli
|
|
|
|
|
|
+## 0.3.0
|
|
|
+
|
|
|
+### Minor Changes
|
|
|
+
|
|
|
+- [#3623](https://github.com/Kilo-Org/kilocode/pull/3623) [`ef6bcac`](https://github.com/Kilo-Org/kilocode/commit/ef6bcac79ed5708996e80c0c943d52f12c0fe3b2) Thanks [@Sureshkumars](https://github.com/Sureshkumars)! - # Checkpoint Restore
|
|
|
+
|
|
|
+ Allows users to restore their conversation to a previous point in time.
|
|
|
+
|
|
|
+ ## What do we have here?
|
|
|
+
|
|
|
+ ### View your checkpoints
|
|
|
+
|
|
|
+ `/checkpoint list`
|
|
|
+
|
|
|
+ This shows all available restore points with:
|
|
|
+ Hash for the checkpoint
|
|
|
+ When it was created
|
|
|
+
|
|
|
+ ### Restore to a checkpoint
|
|
|
+
|
|
|
+ `/checkpoint restore abc123...`
|
|
|
+
|
|
|
+ You'll see a confirmation showing:
|
|
|
+ Which checkpoint you're going back to
|
|
|
+ How many messages will be removed
|
|
|
+ What will happen to your current work
|
|
|
+
|
|
|
+ Choose `Restore` to go back, or `Cancel` to keep working.
|
|
|
+
|
|
|
+ ### Example
|
|
|
+
|
|
|
+ Let's say you asked Kilo CLI to refactor some code, but you don't like the result:
|
|
|
+
|
|
|
+ Run `/checkpoint list` to see earlier save points
|
|
|
+
|
|
|
+ Find the checkpoint from before the refactoring
|
|
|
+
|
|
|
+ Run `/checkpoint restore <hash>` with that checkpoint's hash
|
|
|
+
|
|
|
+ Confirm the restore
|
|
|
+ Your conversation is now back to before the refactoring happened
|
|
|
+
|
|
|
+ ### Why use checkpoints?
|
|
|
+
|
|
|
+ 1. Undo mistakes - Go back if something went wrong
|
|
|
+ 2. Try different approaches - Restore and try a different solution
|
|
|
+ 3. Keep working states - Return to a point where everything was working
|
|
|
+
|
|
|
+### Patch Changes
|
|
|
+
|
|
|
+- [#3500](https://github.com/Kilo-Org/kilocode/pull/3500) [`2e1a536`](https://github.com/Kilo-Org/kilocode/commit/2e1a53678fc1c331d98a63f0ab15b02b53fc1625) Thanks [@iscekic](https://github.com/iscekic)! - improves windows support
|
|
|
+
|
|
|
+- [#3641](https://github.com/Kilo-Org/kilocode/pull/3641) [`94bc43a`](https://github.com/Kilo-Org/kilocode/commit/94bc43af224fed36023d0f3571d39c04d21aa660) Thanks [@KrtinShet](https://github.com/KrtinShet)! - Fix workspace path resolution when using relative paths with --workspace flag. Bash commands now execute in the correct directory.
|
|
|
+
|
|
|
## 0.2.0
|
|
|
|
|
|
### Minor Changes
|