docs: document session-scoped file context

2026-08-29 03:44:06 +08:00 · 2026-08-24 17:59:33 +02:00
parent 21ae999e3e
commit 2a98f0d3b7
2 changed files with 6 additions and 0 deletions
@@ -151,6 +151,8 @@ Imported work stays associated with its branch or worktree and can be continued
 - Use session history to reopen local sessions or preview cloud sessions
 - Continue a cloud session locally from Agent Manager using the same extension sign-in and provider settings

+File mentions, clickable file links, review-comment file links, file-link validation, and native VS Code opening resolve against the referenced session's directory or worktree. If a session ID is present in multiple projects, Kilo rejects the unqualified reference rather than choosing an arbitrary project.
+
 ### Renaming Worktrees

 Double-click a worktree name to edit its label inline. You can also right-click the worktree and choose **Rename**. Press `Enter` or click outside the field to save, or press `Escape` to cancel.
@@ -56,6 +56,10 @@ The extension automatically includes context from your editor with each message

 Selected code and editor diagnostics (errors/warnings) are not included automatically. However, you can send these to Kilo Code through VS Code's Code Actions: select code or hover over an error, then use the lightbulb menu to find context-dependent actions like "Explain with Kilo Code" or "Fix with Kilo Code."

+### Session-scoped file references
+
+In Agent Manager, file mentions, clickable file links, and review-comment file links use the referenced session's directory or worktree. File-link validation and native VS Code opening use the same scope, even after you switch sessions. Kilo rejects an unqualified session ID when it is ambiguous across projects instead of opening or validating a file in the wrong project.
+
 ### Tool-Based File Access

 Rather than attaching file contents up front, the agent reads files on demand during its work: