opensource/kilocode
3
0
Fork 0
mirror of https://github.com/Kilo-Org/kilocode.git synced 2026-10-29 18:52:45 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs(kilo-docs): address session search review

Browse Source
This commit is contained in:
Josh Lambert
2026-08-09 11:34:23 -04:00
parent 5fb5d4d5c0
commit c237a69d01
2 changed files with 32 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/kilo-docs/pages/code-with-ai/agents/context-mentions.md
+4 -4
View File
@@ -25,15 +25,15 @@ Type `@` in the chat input to get autocomplete suggestions. You can mention:
| **File** | Attach a file's contents to your message | `@src/utils.ts` |
| **Terminal** | Include your active VS Code terminal output | `@terminal` |
| **Git Changes** | Attach uncommitted working-tree diffs and new files | `@git-changes` |
| **Past chats** | Attach a previous session's transcript as context | `@` → **Past chats** → pick a session |
| **Past chats** | Add a previous session's chat history as context | `@` → **Past chats** → pick a session |
Selecting a suggestion inserts the mention and highlights it in the input. File contents, terminal output, and git changes are attached as context when you send the message.
### Referencing Past Chats
Choosing **Past chats** from the `@` menu opens a searchable picker of sessions in the current workspace, ordered by recency. Search matches session titles and workspace names. Selecting a session inserts a highlighted mention token; when you send the message, that session's current transcript is attached as context so the agent can build on the earlier conversation. Clicking the mention token opens the referenced session.
Choosing **Past chats** from the `@` menu opens a searchable picker of sessions in the current workspace, ordered by recency. Search matches session titles and workspace names. Selecting a session inserts a highlighted mention token; when you send the message, that session's current chat history is added as context so the agent can build on the earlier conversation. Clicking the mention token opens the referenced session.
Very long transcripts are truncated, keeping the beginning and end, so a single mention cannot fill the context window.
Very long chat histories are truncated, keeping the beginning and end, so a single mention cannot fill the context window.
### Drag and Drop
@@ -77,7 +77,7 @@ This means the agent can explore your entire project as needed, rather than bein
| **Mention files when helpful** | If you know the exact file, mention its path to save the agent a search step |
| **Keep editor tabs relevant** | Open tabs are passed as context, so keep relevant files open |
| **Trust the agent's tools** | The agent can search, read, and explore your codebase — let it do the discovery work |
| **Reference a past chat** | Type `@` and choose **Past chats** to search sessions in the current workspace. Selecting a session attaches its current transcript as context when you send the message. |
| **Reference a past chat** | Type `@` and choose **Past chats** to search sessions in the current workspace. Selecting a session adds its current chat history as context when you send the message. |
{% /tab %}
{% tab label="CLI" %}
packages/kilo-docs/pages/code-with-ai/agents/session-history.md
+28 -22
View File
@@ -5,7 +5,7 @@ description: "Find, search, inspect, and resume local Kilo Code sessions"
# Session history and search
Kilo Code keeps local session metadata and transcripts so you can resume earlier work. You can search session titles in the history UI or CLI, ask the agent to search transcript content, or inspect the local SQLite database directly.
Kilo Code keeps local session metadata and chat history so you can resume earlier work. You can search session titles in the history UI or CLI, ask the agent to search chat content, or inspect the local SQLite database directly.
{% callout type="info" %}
Local sessions use SQLite, not PostgreSQL. Use `kilo db` or `sqlite3`, not `psql`, to inspect the local database.
@@ -17,12 +17,14 @@ Different search surfaces cover different content and scopes:
| Method | Searches | Scope |
|---|---|---|
| VS Code or JetBrains History | Session titles | Sessions loaded in the selected Local or Cloud history view |
| CLI `/sessions` picker | Session titles | Current workspace |
| `kilo session list --search` | Session titles | Current workspace, or every local workspace with `--all` |
| Ask Kilo to recall past chats | Titles and high-signal transcript content | Current workspace |
| VS Code transcript search | Rendered content in the open session | Current session |
| SQLite query | Any stored field you select | Entire selected local database |
| [VS Code History](#search-session-history-in-vs-code) | Session titles | Sessions loaded in the selected Local or Cloud history view |
| [JetBrains History](#search-session-history-in-jetbrains) | Session titles | Sessions loaded in the selected Local or Cloud history view |
| [CLI `/sessions` picker](#search-session-history-in-the-cli-tui) | Session titles | Current workspace |
| [`kilo session list --search`](#filter-session-titles) | Session titles | Current workspace, or every local workspace with `--all` |
| [Ask Kilo to recall past chats](#ask-kilo-to-search-past-chats) | Titles and high-signal chat content | Current workspace |
| [VS Code chat search](#search-the-open-chat-session) | Rendered content in the open session | Current chat session |
| [VS Code Past chats](#add-a-past-chat-to-the-current-session) | Session titles and workspace names | Current workspace |
| [SQLite query](#query-sqlite-directly) | Any stored field you select | Entire selected local database |
History and CLI list searches do **not** search message content. To find a string inside prompts or replies, ask Kilo to search past chats or use a direct SQLite query.
@@ -31,7 +33,7 @@ History and CLI list searches do **not** search message content. To find a strin
{% tabs %}
{% tab label="VS Code" %}
### Search session history
### Search session history in VS Code
1. Open the Kilo Code sidebar.
2. Select the **History** button in the sidebar title bar. You can also select **Show History** below the recent sessions on a new chat.
@@ -43,24 +45,26 @@ Local history actions also let you rename, export, or delete a session. Cloud hi
The History search is a fuzzy title search over the sessions currently loaded into the view. It does not search prompts or agent replies.
### Search the open transcript
### Search the open chat session
Open a session and select the magnifying-glass button in its header. Transcript search supports:
Open a session and select the magnifying-glass button in its header. Chat search supports:
- Previous and next match navigation
- Match case
- Whole word
- Regular expressions
Kilo loads older messages while the search is active so the search covers the full local transcript, not only the messages initially visible.
Kilo loads older messages while the search is active so the search covers the full local chat session, not only the messages initially visible.
### Reference another session
### Add a past chat to the current session
Type `@` in the chat input, select **Past chats**, and search by session title or workspace name. Selecting a result attaches that transcript as context when you send the message. Past chats includes sessions in the current workspace.
Type `@` in the chat input, select **Past chats**, and search by session title or workspace name. Selecting a result adds that past chat's content as context when you send the message from your current session. It does not switch or reopen sessions. Past chats includes sessions in the current workspace.
{% /tab %}
{% tab label="JetBrains" %}
### Search session history in JetBrains
1. Open the Kilo Code tool window.
2. Select **History** in the tool window toolbar.
3. Select **Local** or **Cloud**.
@@ -69,11 +73,13 @@ Type `@` in the chat input, select **Past chats**, and search by session title o
You can rename or delete local sessions. In Cloud history, enable **Only this repository** to narrow the list.
The JetBrains History search matches session titles, not transcript content.
The JetBrains History search matches session titles, not chat content.
{% /tab %}
{% tab label="CLI TUI" %}
### Search session history in the CLI TUI
Run `kilo`, then enter any of these commands:
```text
@@ -87,7 +93,7 @@ Start typing in the session picker to filter sessions by title. The picker also
{% /tab %}
{% /tabs %}
## Ask Kilo to search transcripts
## Ask Kilo to search past chats
The simplest way to search message content across past local sessions is to ask Kilo directly:
@@ -97,7 +103,7 @@ Search my local sessions for "database disk image is malformed" and summarize th
Kilo's local recall search covers session titles, user and assistant text, file references, and failed tool errors in the current workspace. Every query term must occur somewhere in a matching session; exact phrases and user-authored matches rank higher.
The search includes archived and child sessions. It excludes reasoning, synthetic or ignored text, successful tool output, file contents, and other metadata. Kilo can then read the full transcript for a selected result.
The search includes archived and child sessions. It excludes reasoning, synthetic or ignored text, successful tool output, file contents, and other metadata. Kilo can then read the full chat history for a selected result.
## Search with CLI commands
@@ -238,7 +244,7 @@ curl -u "kilo:$KILO_SERVER_PASSWORD" \
--data-urlencode "limit=50"
```
Read the complete transcript for one result:
Read the complete chat history for one result:
```bash
curl -u "kilo:$KILO_SERVER_PASSWORD" \
@@ -246,7 +252,7 @@ curl -u "kilo:$KILO_SERVER_PASSWORD" \
--data-urlencode "directory=$PWD"
```
The list endpoint's `search` parameter searches titles only. To search transcript text programmatically, list candidate sessions, read their messages, and inspect text parts in your application.
The list endpoint's `search` parameter searches titles only. To search chat content programmatically, list candidate sessions, read their messages, and inspect text parts in your application.
The JavaScript SDK exposes the same endpoints:
@@ -266,17 +272,17 @@ const result = await client.session.list(
)
for (const session of result.data) {
const transcript = await client.session.messages(
const history = await client.session.messages(
{ sessionID: session.id, limit: 0 },
{ throwOnError: true },
)
// Inspect transcript.data[*].parts for the content your application needs.
console.log(session.title, transcript.data.length)
// Inspect history.data[*].parts for the content your application needs.
console.log(session.title, history.data.length)
}
```
`limit: 0` requests the complete transcript from the compatibility API. For large sessions, use a positive `limit` and follow the pagination cursor instead.
`limit: 0` requests the complete chat history from the compatibility API. For large sessions, use a positive `limit` and follow the pagination cursor instead.
## Local and cloud sessions