A history management extension for codecompanion.nvim that enables saving, browsing and restoring chat sessions.
history-demo.mp4
- πΎ Flexible chat saving:
- Automatic session saving (can be disabled)
- Manual save with dedicated keymap
- π― Smart title generation for chats
- π Continue from where you left
- π Browse saved chats with preview
- π Multiple picker interfaces
- β Optional automatic chat expiration
- β‘ Restore chat sessions with full context and tools state
- π’ Project-aware filtering: Filter chats by workspace/project context
- π Chat duplication: Easily duplicate chats to create variations or backups
The following CodeCompanion features are preserved when saving and restoring chats:
Feature | Status | Notes |
---|---|---|
System Prompts | β | System prompt used in the chat |
Messages History | β | All messages |
Images | β | Restores images as base64 strings |
LLM Adapter | β | The specific adapter used for the chat |
LLM Settings | β | Model, temperature and other adapter settings |
Tools | β | Tool schemas and their system prompts |
Tool Outputs | β | Tool execution results |
Variables | β | Variables used in the chat |
References | β | Code snippets and command outputs added via slash commands |
Pinned References | β | Pinned references |
Watchers | β | Saved but requires original buffer context to resume watching |
When restoring a chat:
- The complete message history is recreated
- All tools and references are reinitialized
- Original LLM settings and adapter are restored
- Previous system prompts are preserved
Note: While watched buffer states are saved, they require the original buffer context to resume watching functionality.
Note
As this is an extension that deeply integrates with CodeCompanion's internal APIs, occasional compatibility issues may arise when CodeCompanion updates. If you encounter any bugs or unexpected behavior, please raise an issue to help us maintain compatibility.
- Neovim >= 0.8.0
- codecompanion.nvim
- snacks.nvim (optional, for enhanced picker)
- telescope.nvim (optional, for enhanced picker)
- fzf-lua (optional, for enhanced picker)
Using lazy.nvim:
{
"olimorris/codecompanion.nvim",
dependencies = {
--other plugins
"ravitemer/codecompanion-history.nvim"
}
}
require("codecompanion").setup({
extensions = {
history = {
enabled = true,
opts = {
-- Keymap to open history from chat buffer (default: gh)
keymap = "gh",
-- Keymap to save the current chat manually (when auto_save is disabled)
save_chat_keymap = "sc",
-- Save all chats by default (disable to save only manually using 'sc')
auto_save = true,
-- Number of days after which chats are automatically deleted (0 to disable)
expiration_days = 0,
-- Picker interface (auto resolved to a valid picker)
picker = "telescope", --- ("telescope", "snacks", "fzf-lua", or "default")
-- Customize picker keymaps (optional)
picker_keymaps = {
rename = { n = "r", i = "<M-r>" },
delete = { n = "d", i = "<M-d>" },
duplicate = { n = "<C-y>", i = "<C-y>" },
},
---Automatically generate titles for new chats
auto_generate_title = true,
title_generation_opts = {
---Adapter for generating titles (defaults to current chat adapter)
adapter = nil, -- "copilot"
---Model for generating titles (defaults to current chat model)
model = nil, -- "gpt-4o"
---Number of user prompts after which to refresh the title (0 to disable)
refresh_every_n_prompts = 0, -- e.g., 3 to refresh after every 3rd user prompt
---Maximum number of times to refresh the title (default: 3)
max_refreshes = 3,
},
---On exiting and entering neovim, loads the last chat on opening chat
continue_last_chat = false,
---When chat is cleared with `gx` delete the chat from history
delete_on_clearing_chat = false,
---Directory path to save the chats
dir_to_save = vim.fn.stdpath("data") .. "/codecompanion-history",
---Enable detailed logging for history extension
enable_logging = false,
---Optional filter function to control which chats are shown when browsing
chat_filter = nil, -- function(chat_data) return boolean end
}
}
}
})
:CodeCompanionHistory
- Open the history browser
gh
- Open history browser (customizable viaopts.keymap
)sc
- Save current chat manually (customizable viaopts.save_chat_keymap
)
The history browser shows all your saved chats with:
- Title (auto-generated or custom)
- Last updated time
- Preview of chat contents
Actions in history browser:
<CR>
- Open selected chat- Normal mode:
d
- Delete selected chat(s)r
- Rename selected chat<C-y>
- Duplicate selected chat
- Insert mode:
<M-d>
(Alt+d) - Delete selected chat(s)<M-r>
(Alt+r) - Rename selected chat<C-y>
- Duplicate selected chat
Note: Delete, rename, and duplicate actions are only available in telescope, snacks, and fzf-lua pickers. Multiple chats can be selected for deletion using picker's multi-select feature (press
<Tab>
). Duplication is limited to one chat at a time.
The extension can automatically refresh chat titles as conversations evolve:
refresh_every_n_prompts
: Set to refresh the title after every N user prompts (e.g., 3 means refresh after the 3rd, 6th, 9th user message)max_refreshes
: Limits how many times a title can be refreshed to avoid excessive API calls- When refreshing, the system considers recent conversation context (both user and assistant messages) and the original title
- Individual messages are truncated at 1000 characters with a
[truncated]
indicator - Total conversation context is limited to 10,000 characters with a
[conversation truncated]
indicator
Example configuration for title refresh:
title_generation_opts = {
refresh_every_n_prompts = 3, -- Refresh after every 3rd user prompt
max_refreshes = 10, -- Allow up to 10 refreshes per chat
}
The extension supports flexible chat filtering to help you focus on relevant conversations:
Configurable Filtering:
chat_filter = function(chat_data)
return chat_data.cwd == vim.fn.getcwd()
end
-- Recent chats only (last 7 days)
chat_filter = function(chat_data)
local seven_days_ago = os.time() - (7 * 24 * 60 * 60)
return chat_data.updated_at >= seven_days_ago
end
Chat Index Data Structure: Each chat index entry (used in filtering) includes the following information:
-- ChatIndexData - lightweight metadata used for browsing and filtering
{
save_id = "1672531200", -- Unique chat identifier
title = "Debug API endpoint", -- Chat title (auto-generated or custom)
cwd = "/home/user/my-project", -- Working directory when saved
project_root = "/home/user/my-project", -- Detected project root
adapter = "openai", -- LLM adapter used
model = "gpt-4", -- Model name
updated_at = 1672531200, -- Unix timestamp of last update
message_count = 15, -- Number of messages in chat
token_estimate = 3420, -- Estimated token count
}
The history extension exports the following functions that can be accessed via require("codecompanion").extensions.history
:
-- Get the storage location for saved chats
get_location(): string?
-- Save a chat to storage (uses last chat if none provided)
save_chat(chat?: CodeCompanion.Chat)
-- Browse chats with custom filter function
browse_chats(filter_fn?: function(ChatIndexData): boolean)
-- Get metadata for all saved chats with optional filtering
get_chats(filter_fn?: function(ChatIndexData): boolean): table<string, ChatIndexData>
-- Load a specific chat by its save_id
load_chat(save_id: string): ChatData?
-- Delete a chat by its save_id
delete_chat(save_id: string): boolean
-- Duplicate a chat by its save_id
duplicate_chat(save_id: string, new_title?: string): string?
Example usage:
local history = require("codecompanion").extensions.history
-- Browse chats with project filter
history.browse_chats(function(chat_data)
return chat_data.project_root == utils.find_project_root()
end)
-- Get all saved chats metadata
local chats = history.get_chats()
-- Load a specific chat
local chat_data = history.load_chat("some_save_id")
-- Delete a chat
history.delete_chat("some_save_id")
-- Duplicate a chat with custom title
local new_save_id = history.duplicate_chat("some_save_id", "My Custom Copy")
-- Duplicate a chat with auto-generated title (appends "(1)")
local new_save_id = history.duplicate_chat("some_save_id")
graph TD
subgraph CodeCompanion Core Lifecycle
A[CodeCompanionChatCreated Event] --> B{Chat Submitted};
B --> C[LLM Response Received];
subgraph Chat End
direction RL
D[CodeCompanionChatCleared Event];
end
C --> D;
B --> D;
end
subgraph Extension Integration
A -- Extension Hooks --> E[Init & Subscribe];
E --> F[Setup Auto-Save];
F --> G[Prepare Auto-Title];
C -- Extension Hooks --> H[Subscriber Triggered];
H --> H1{Auto-Save Enabled?};
H1 -- Yes --> I[Save Chat State - Messages, Tools, Refs];
H1 -- No --> H2[Manual Save via `sc`];
H2 --> I;
I --> J{No Title & Auto-Title Enabled?};
J -- Yes --> K[Generate Title];
K --> L[Update Buffer Title];
L --> M[Save Chat with New Title];
J -- No --> B;
M --> B;
D -- Extension Hooks --> N[Respond to Clear Event];
N --> O[Delete Chat from Storage];
O --> P[Reset Extension State - Title/ID];
end
subgraph User History Interaction
Q[User Action - gh / :CodeCompanionHistory] --> R{History Browser};
R -- Restore --> S[Load Chat State from Storage];
S --> A;
R -- Delete --> O;
end
Here's what's happening in simple terms:
-
When you create a new chat, our extension jumps in and sets up two things:
- An autosave system that will save your chat
- A title generator that will name your chat based on the conversation
-
As you chat:
- When auto-save is enabled (default):
- Each submitted message triggers automatic saving
- Every LLM response automatically saves the chat state
- Manual saving is available via the
sc
keymap - If your chat doesn't have a title yet, it tries to create one that makes sense
- All your messages, tools, and references are safely stored
- When auto-save is enabled (default):
-
When you clear a chat:
- Our extension knows to remove it from storage (if configured)
- This keeps your history clean and organized
-
Any time you want to look at old chats:
- Use
gh
or the command to open the history browser - Pick any chat to restore it completely
- Or remove ones you don't need anymore
- Use
Technical details
The extension integrates with CodeCompanion through a robust event-driven architecture:
-
Initialization and Storage Management:
- Uses a dedicated Storage class to manage chat persistence in
{data_path}/codecompanion-history/
- Maintains an index.json for metadata and individual JSON files for each chat
- Implements file I/O operations with error handling and atomic writes
- Uses a dedicated Storage class to manage chat persistence in
-
Chat Lifecycle Integration:
-
Hooks into
CodeCompanionChatCreated
event to:- Generate unique save_id (Unix timestamp)
- Initialize chat subscribers for auto-saving
- Set initial buffer title with sparkle icon (β¨)
-
Monitors
CodeCompanionChatSubmitted
events to:- Persist complete chat state including messages, tools, schemas, and references
- Trigger title generation if enabled and title is empty
- Update buffer title with relative timestamps
-
-
Title Generation System:
- Uses the chat's configured LLM adapter for title generation
- Implements smart content truncation (1000 chars) and prompt engineering
- Handles title collisions with automatic numbering
- Updates titles asynchronously using vim.schedule
-
State Management:
- Preserves complete chat context including:
- Message history with role-based organization
- Tool states and schemas
- Reference management
- Adapter configurations
- Custom settings
- Preserves complete chat context including:
-
UI Components:
- Implements multiple picker interfaces (telescope/snacks/default)
- Provides real-time preview generation with markdown formatting
- Supports justified text layout for buffer titles
- Handles window/buffer lifecycle management
-
Data Flow:
- Chat data follows a structured schema (ChatData)
- Implements proper serialization/deserialization
- Maintains backward compatibility with existing chats
- Provides error handling for corrupt or missing data
- Add support for additional pickers like snacks, fzf etc
- MCP Hub extension
- VectorCode extension
Special thanks to Oli Morris for creating the amazing CodeCompanion.nvim plugin - a highly configurable and powerful coding assistant for Neovim.
MIT