VS Code Chronicle: Local Chat History Indexing

Local Session Indexing and Querying

Chronicle addresses the difficulty of tracking developer activity across multiple Copilot chat sessions by automatically logging metadata—including edited files, branches, and PRs—into a local SQLite database. To activate the feature, users must enable the local index setting in VS Code. Once enabled, the system provides a suite of built-in commands accessible via the command palette:

• Chronicle: Standup: Generates a summary of activity from the last 24 hours, including repo context and file changes.
• Chronicle: Tips: Analyzes the last seven days of sessions to provide personalized feedback, such as suggesting when to consolidate short sessions or break up excessively long ones.
• Chronicle: Reindex: Crawls historical chat sessions to ingest data into the local SQLite store.
• Free-form queries: Users can type Chronicle followed by a natural language prompt to search across all indexed sessions.

Debugging and Limitations

Users can inspect the underlying data retrieval process by opening the Chat debug logs, which display the raw SQL queries executed against the database. Currently, the feature is restricted to the local host machine, meaning it does not support remote scenarios like dev containers. While the current implementation is read-only, the team identifies the ability to resume past sessions as a future development goal.