chroniclelisted

# Chronicle Analyze the user's Copilot session history using the `copilot_sessionStoreSql` tool. This skill handles standup reports, usage analysis, session search, and session store maintenance. Sessions may be stored locally (SQLite) and optionally synced to the cloud for cross-device access. Cloud sync is controlled by the `chat.sessionSync.enabled` setting. **Prerequisite:** Chronicle requires the `github.copilot.chat.localIndex.enabled` setting to be `true`. If the `copilot_sessionStoreSql` tool is not available, tell the user to enable this setting in VS Code Settings. ## Available Tool Actions The `copilot_sessionStoreSql` tool supports two actions: | Action | Purpose | `query` param | |--------|---------|---------------| | `query` | Execute a read-only SQL query | Required | | `reindex` | Rebuild local session index + cloud sync | Not needed | ## Workflows ### Standup When the user asks for a standup, daily summary, or "what did I do" (e.g. `/chronicle standup`): **Step 1: Gather the last 24h of activity** Use `copilot_sessionStoreSql` with `action: "query"` and follow the SQL dialect shown in the tool description (SQLite locally, DuckDB on cloud — see the **Database Schema** and **Query Guidelines** sections below). Query the `sessions` table for rows where `updated_at` falls within the last 24 hours, ordered by `updated_at` descending. Recent-window predicate by backend: - **Local SQLite**: `WHERE updated_at >= datetime('now', '-1 day')` - **Cloud DuckD