You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .roomodes
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
customModes:
2
2
- slug: release-notes-writer
3
-
name: Release Notes Writer
3
+
name: 📝 Release Notes Writer
4
4
roleDefinition: "You are a technical writer for Roo Code release notes. Your job is to: - Automate release note creation. - Fetch and analyze GitHub pull requests. - Convert technical changes into user benefits. - Ensure updates align with documentation standards. - Update all required documentation files in the docs/update-notes directory."
5
5
whenToUse: |-
6
6
Use this mode to create or update release notes from GitHub PRs and existing docs.
@@ -47,7 +47,7 @@ customModes:
47
47
- mcp
48
48
source: project
49
49
- slug: documentation-writer
50
-
name: 📝 Documentation Writer
50
+
name: 📖 Documentation Writer
51
51
roleDefinition: You are a technical documentation writer for the Roo Code project. Your writing is direct, concise, and technical. You write for a developer audience and follow the instructions in the .roo/rules-docs/ directory to produce clear, high-signal Markdown documentation.
52
52
whenToUse: Use this mode for creating or updating documentation in Markdown (.md, .mdx) files.
53
53
description: Creates and maintains Roo technical docs.
Copy file name to clipboardExpand all lines: docs/basic-usage/the-chat-interface.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,11 +29,11 @@ The chat interface consists of the following main elements:
29
29
30
30
4.**Send Button:** This looks like a small plane and it's located to the far right of the input field. This sends messages to Roo after you've typed them.
31
31
32
-
5.**Plus Button:** The plus button is located at the top in the header, and it resets the current session.
32
+
5.**Plus Button:** The plus button is located at the top in the header. It switches to the Chat tab and focuses the input. To reset the session, start a new task or clear the current task.
33
33
34
34
6.**Settings Button:** The settings button is a gear, and it's used for opening the settings to customize features or behavior.
35
35
36
-
7.**Mode Selector:** The mode selector is a dropdown located to the left of the chat input field. It is used for selecting which mode Roo should use for your tasks.
36
+
7.**Mode Selector:** The mode selector is a dropdown located to the left of the chat input field. It is used for selecting which mode Roo should use for your tasks. Its settings gear opens the Modes tab, not general settings.
37
37
38
38
<imgsrc="/img/the-chat-interface/the-chat-interface-1.png"alt="Chat interface components labeled with numbered callouts"width="900" />
Copy file name to clipboardExpand all lines: docs/features/checkpoints.mdx
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ Access checkpoint settings in Roo Code settings under the "Checkpoints" section:
61
61
62
62
## How Checkpoints Work
63
63
64
-
Roo Code captures snapshots of your project's state using a shadow Git repository, separate from your main version control system. These snapshots, called checkpoints, are automatically created **before** file modifications occur, ensuring you can always undo unwanted changes. Checkpoints are recorded throughout your AI-assisted workflow—when tasks begin, before files change, and before commands run.
64
+
Roo Code captures snapshots of your project's state using a shadow Git repository, separate from your main version control system. These snapshots, called checkpoints, are automatically created **before** file modifications occur, ensuring you can always undo unwanted changes. Checkpoints are recorded when tasks begin and before file modifications. They are not automatically created before command execution.
65
65
66
66
Checkpoints are stored as Git commits in the shadow repository, capturing:
67
67
@@ -82,7 +82,7 @@ Checkpoints appear directly in your chat history:
82
82
-**Task checkpoint** marks your starting project state
83
83
<imgsrc="/img/checkpoints/checkpoints-1.png"alt="Task checkpoint indicator in chat"width="500" />
84
84
85
-
-**Regular checkpoints** are created before file modifications or command execution, allowing easy undo of any changes
85
+
-**Regular checkpoints** are created before file modifications, allowing easy undo of any changes
86
86
<imgsrc="/img/checkpoints/checkpoints-2.png"alt="Regular checkpoint indicator in chat"width="500" />
87
87
88
88
Each checkpoint provides two primary functions:
@@ -100,7 +100,7 @@ To compare your current workspace with a previous checkpoint:
100
100
- Added lines are highlighted in green
101
101
- Removed lines are highlighted in red
102
102
- Modified files are listed with detailed changes
103
-
-Renamed and moved files are tracked with their path changes
103
+
-Renames may not always be detected; diffs reflect per-file changes between commits
104
104
- New or deleted files are clearly marked
105
105
106
106
<imgsrc="/img/checkpoints/checkpoints-3.png"alt="View differences option for checkpoints"width="800" />
@@ -164,7 +164,7 @@ Checkpoints are task-scoped, meaning they are specific to a single task.
164
164
Checkpoint comparison uses Git's underlying diff capabilities to produce structured file differences:
165
165
- Modified files show line-by-line changes
166
166
- Binary files are properly detected and handled
167
-
-Renamed and moved files are tracked correctly
167
+
-Rename detection may be limited; diffs focus on file content changes between checkpoints
168
168
- File creation and deletion are clearly identified
169
169
170
170
### File Exclusion and Ignore Patterns
@@ -190,6 +190,10 @@ The checkpoint system respects `.gitignore` patterns in your workspace:
190
190
- Excluded files won't appear in checkpoint diffs
191
191
- Standard Git ignore rules apply when staging file changes
192
192
193
+
#### Git LFS Patterns
194
+
195
+
Patterns defined in your workspace's `.gitattributes` for Git LFS are read and added to checkpoint exclusions. This helps avoid tracking large LFS-managed assets in the shadow repository.
196
+
193
197
#### .rooignore Behavior
194
198
195
199
The `.rooignore` file (which controls AI access to files) is separate from checkpoint tracking:
@@ -200,15 +204,11 @@ This separation is intentional, as `.rooignore` limits which files the AI can ac
200
204
201
205
#### Nested Git Repositories
202
206
203
-
The checkpoint system includes special handling for nested Git repositories:
204
-
- Temporarily renames nested `.git` directories to `.git_disabled` during operations
205
-
- Restores them after operations complete
206
-
- Allows proper tracking of files in nested repositories
207
-
- Ensures nested repositories remain functional and unaffected
207
+
If nested Git repositories are detected in your workspace, checkpoints are disabled. Remove or relocate nested repositories to enable checkpoints.
208
208
209
209
### Concurrency Control
210
210
211
-
Operations are queued to prevent concurrent Git operations that might corrupt repository state. This ensures that rapid checkpoint operations complete safely even when requested in quick succession.
211
+
The extension prevents duplicate checkpointing within a single streaming operation. There is no dedicated Git operation queue.
description: Edit or delete messages with instant rollback checkpoints, Kimi K2-0905 provider update, and stability fixes across indexing, grounding, and multi-root workspaces.
3
+
keywords:
4
+
- roo code 3.27.0
5
+
- release notes
6
+
- edit messages
7
+
- delete messages
8
+
- checkpoints
9
+
- auto checkpoints
10
+
- rollback
11
+
- chutes provider
12
+
- kimi k2-0905
13
+
- 256k context
14
+
- provider update
15
+
- codebase indexing
16
+
- multi-root workspace
17
+
- mcp config
18
+
- slash commands
19
+
- gemini grounding
20
+
- citations
21
+
- openai responses api
22
+
- previous_response_id
23
+
- vscode terminal profiles
24
+
- ci e2e
25
+
image: /img/social-share.jpg
26
+
---
27
+
28
+
# Roo Code 3.27.0 Release Notes (2025-09-05)
29
+
30
+
This release adds message editing and deletion with instant rollback checkpoints, updates the Chutes provider with Kimi K2-0905, and improves reliability across indexing, grounding, and multi-root workspaces.
31
+
32
+
## Edit and delete messages with instant rollback checkpoints
33
+
34
+
Edit or delete any chat message and quickly recover from mistakes using automatic checkpoints (thanks NaccOll!) ([#7447](https://github.com/RooCodeInc/Roo-Code/pull/7447), [#7713](https://github.com/RooCodeInc/Roo-Code/pull/7713)):
35
+
36
+
- Edit or delete past messages to correct prompts without restarting the session.
37
+
- Automatic checkpoint on every user message enables instant rollback, even when no file diffs exist.
38
+
- Review changes with a Checkpoint Restore dialog before applying them.
39
+
- Runs in the background and suppresses extra chat noise.
40
+
41
+
> 📚 Documentation: See [Checkpoints](/features/checkpoints) and [The Chat Interface](/basic-usage/the-chat-interface).
42
+
43
+
## QOL Improvements
44
+
45
+
* Welcome screen readability and spacing improvements for faster scanning (#[7682](https://github.com/RooCodeInc/Roo-Code/pull/7682))
46
+
47
+
## Bug Fixes
48
+
49
+
* Fixes an issue where indexing very large projects could hit a stack overflow (thanks StarTrai1!) (#[7712](https://github.com/RooCodeInc/Roo-Code/pull/7712))
50
+
* Fixes an issue where terminal launch sometimes failed when VS Code provided the shell path as an array (thanks Amosvcc!) (#[7697](https://github.com/RooCodeInc/Roo-Code/pull/7697))
51
+
* Fixes cases where MCP and slash-command paths in multi-root workspaces resolved to the wrong folder (now uses the active folder CWD) (thanks NaccOll, kfuglsang!) (#[6904](https://github.com/RooCodeInc/Roo-Code/pull/6904))
52
+
* Fixes an issue where Gemini grounding citations sometimes leaked or duplicated (thanks HahaBill!) (#[7434](https://github.com/RooCodeInc/Roo-Code/pull/7434))
53
+
* Fixes an issue where conversation context could be lost when previous_response_id became invalid (now retries with full history) (#[7714](https://github.com/RooCodeInc/Roo-Code/pull/7714))
54
+
* Fixes a CI issue where e2e runs sometimes timed out while downloading VS Code (#[7583](https://github.com/RooCodeInc/Roo-Code/pull/7583))
55
+
56
+
## Provider Updates
57
+
58
+
* Chutes: Adds Kimi K2-0905 model with a 256k context window and pricing metadata (thanks pwilkin!) (#[7701](https://github.com/RooCodeInc/Roo-Code/pull/7701))
59
+
> 📚 Documentation: See [Chutes](/providers/chutes)
0 commit comments