-
Notifications
You must be signed in to change notification settings - Fork 2.4k
docs: chat recall tutorial #5975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,91 @@ | ||
| --- | ||
| title: Chat Recall Extension | ||
| description: Search conversation history and load session summaries across all your goose sessions | ||
| --- | ||
|
|
||
| import Tabs from '@theme/Tabs'; | ||
| import TabItem from '@theme/TabItem'; | ||
| import { PlatformExtensionNote } from '@site/src/components/PlatformExtensionNote'; | ||
| import GooseBuiltinInstaller from '@site/src/components/GooseBuiltinInstaller'; | ||
|
|
||
| The Chat Recall extension helps goose remember past conversations by searching across your session history. When you need context from previous work, goose can search for relevant conversations or load summaries of specific sessions. | ||
|
|
||
| goose automatically uses Chat Recall when you reference past work or ask questions that require historical context. | ||
|
|
||
| ## Configuration | ||
|
|
||
| <PlatformExtensionNote/> | ||
|
|
||
| <Tabs groupId="interface"> | ||
| <TabItem value="ui" label="goose Desktop" default> | ||
| <GooseBuiltinInstaller | ||
| extensionName="Chatrecall" | ||
| description="Search conversation history across all your sessions" | ||
| /> | ||
| </TabItem> | ||
| <TabItem value="cli" label="goose CLI"> | ||
|
|
||
| 1. Run the `configure` command: | ||
| ```sh | ||
| goose configure | ||
| ``` | ||
|
|
||
| 2. Choose to `Toggle Extensions` | ||
| ```sh | ||
| ┌ goose-configure | ||
| │ | ||
| ◇ What would you like to configure? | ||
| │ Toggle Extensions | ||
| │ | ||
| ◆ Enable extensions: (use "space" to toggle and "enter" to submit) | ||
| // highlight-start | ||
| │ ● chatrecall | ||
| // highlight-end | ||
| └ Extension settings updated successfully | ||
| ``` | ||
| </TabItem> | ||
| </Tabs> | ||
|
|
||
| ## Example Usage | ||
|
|
||
| Chat Recall can search across all sessions using keywords. Results are grouped by session and ordered by recency, and can be filtered by date. Alternatively, you can provide [session IDs](/docs/guides/goose-cli-commands#session-list-options) to load summaries of specific sessions. | ||
|
|
||
| Let's ask goose to find recent conversations about a topic: | ||
|
|
||
| ### goose Prompt | ||
|
|
||
| ``` | ||
| What did we discuss about database migrations last week? | ||
| ``` | ||
|
|
||
| ### goose Output | ||
|
|
||
| :::note Desktop | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes! It's in the template for Desktop output examples |
||
| I found discussions about database migrations in your recent sessions. Here's what we covered: | ||
|
|
||
| **Database Migration Discussions - Last Week** | ||
|
|
||
| #### Session: Fix migration scripts (Nov 26, 2024) | ||
| **Working Dir:** /projects/myapp | ||
|
|
||
| We debugged a production database migration that was failing with a "column already exists" error. The key points were: | ||
|
|
||
| - The migration was trying to add a column that already existed in some environments | ||
| - We added conditional logic to check if the column exists before adding it | ||
| - Tested the fix locally and committed the changes | ||
|
|
||
| #### Session: Database schema updates (Nov 27, 2024) | ||
| **Working Dir:** /projects/myapp | ||
|
|
||
| We discussed adding email verification functionality: | ||
|
|
||
| - Planned to add a new `email_verified` column to the users table | ||
| - Discussed whether to make it nullable or default to false | ||
| - Created the migration script for the new column | ||
|
|
||
| Both sessions were focused on safely updating the database schema in production. Would you like me to load the full details from either of these sessions? | ||
| ::: | ||
|
|
||
| :::info | ||
| Compacted sessions from goose versions prior to v1.14.0 may not be searchable due to a change in how conversation history is stored. | ||
| ::: | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| import React from "react"; | ||
| import Admonition from '@theme/Admonition'; | ||
|
|
||
| export const PlatformExtensionNote = () => { | ||
|
|
||
| return ( | ||
| <Admonition type="info" title="Platform Extension"> | ||
| <p>This is a <a href="/goose/docs/getting-started/using-extensions#built-in-platform-extensions">built-in platform extension</a> that's enabled by default. Platform extensions provide core functionality and are used within goose just like MCP server extensions.</p> | ||
| </Admonition> | ||
| ); | ||
| }; |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The extensionName should be "Chat Recall" (with space and proper casing) to match the naming convention used by other platform extensions like "Extension Manager" and "Todo".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Chatrecall" is the display name in the desktop