Merge pull request #13389 from Kilo-Org/docs-session-file-context

docs: document session-scoped file context
This commit is contained in:
Marius
2026-08-24 18:36:37 +02:00
committed by GitHub
2 changed files with 6 additions and 0 deletions
@@ -193,6 +193,8 @@ Imported work stays associated with its branch or worktree and can be continued
- When a worktree is selected, open session history to use the **Worktree** source, which is selected by default and lists only sessions assigned to that worktree. Opening a worktree session returns to its owning worktree.
- 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.
When a session delegates work to a subagent, open the child transcript from its task card or background-agent row. Agent Manager displays it in the read-only **Subagents** inspector. The inspector supports multiple child-session tabs and keeps them scoped to the selected project and parent session. For the difference between Agent Manager inspector tabs and the separate subagent editor tabs used by the sidebar, see [Inspecting delegated sessions in VS Code](/docs/customize/custom-subagents#inspecting-delegated-sessions-in-vs-code).
### Renaming Worktrees
@@ -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: