Merge pull request #9845 from microsoft/ntrogh/session-sync

Remove session sync article

Author: ntrogh

docs/copilot/chat/session-insights.md

@@ -6,7 +6,7 @@ MetaSocialImage: ../images/shared/github-copilot-social.png
 ---
 # Query session history with chronicle
 
-Your GitHub Copilot sessions build a searchable history of everything you work on. Ask natural language questions about past sessions, generate standup reports, get personalized tips, and search your coding history. With [session sync](/docs/copilot/chat/session-sync.md) active by default, queries draw from sessions across Copilot CLI, coding agent, code review, and VS Code.
+Your GitHub Copilot sessions build a searchable history of everything you work on. Ask natural language questions about past sessions, generate standup reports, get personalized tips, and search your coding history.
 
 ## Chronicle commands
 
@@ -18,11 +18,11 @@ Use these commands in the chat input to query your session history:
 | `/chronicle:tips` | Analyze your recent session history (typically 7 days) and suggest ways to use Copilot more effectively. Tips are grounded in your actual usage patterns: tools you rarely use, prompting patterns that lead to better results, or workflow improvements. |
 | `/chronicle:cost-tips` | Analyze recent sessions to identify opportunities to reduce token usage and Copilot cost. |
 | `/chronicle:search <query>` | Search sessions by keyword, file path, or PR or issue reference. Uses full-text indexing across session summaries, conversation turns, file paths, and checkpoint notes. Results include session IDs and timestamps so you can resume relevant sessions. |
-| `/chronicle:reindex` | Rebuild the local session index and sync session data to your account. |
+| `/chronicle:reindex` | Rebuild the local session index. |
 
 ## Free-form questions
 
-You can also ask free-form questions about your session history directly in chat. For example, type "What files did I edit yesterday?" or "Have I worked on anything related to the payments API?" and Copilot searches your synced session history to answer. Unlike `/chronicle:search` which performs a direct content search, free-form questions use semantic understanding to find relevant sessions.
+You can also ask free-form questions about your session history directly in chat. For example, type "What files did I edit yesterday?" or "Have I worked on anything related to the payments API?" and Copilot searches your local session history to answer. Unlike `/chronicle:search` which performs a direct content search, free-form questions use semantic understanding to find relevant sessions.
 
 ## What gets tracked
 
@@ -33,11 +33,11 @@ For each chat session, the local session store records:
 * **Files touched**: file paths from tool calls such as `replace_string_in_file`, `create_file`, `read_file`, and `apply_patch`.
 * **External references**: PR numbers, issue numbers, and commit SHAs extracted from GitHub MCP tool calls and terminal commands.
 
-Data is stored in a local SQLite database. Secrets such as tokens, API keys, passwords, and connection strings are automatically filtered before data is synced to the cloud.
+Data is stored in a local SQLite database.
 
 ## Reindex the session store
 
-If sessions appear missing or the database becomes corrupted, rebuild the index. Reindexing also syncs your session data to your account.
+If sessions appear missing or the database becomes corrupted, rebuild the index.
 
 ```prompt
 /chronicle:reindex
@@ -50,10 +50,8 @@ Situations where reindexing helps:
 * After restoring session files from a backup
 * After an unexpected crash that prevented data from flushing to the store
 * After manually deleting session directories
-* After opting back into session sync
 
 ## Related content
 
-* [Session sync](/docs/copilot/chat/session-sync.md) - Sync sessions to your GitHub account for cross-device access
 * [Manage chat sessions](/docs/copilot/chat/chat-sessions.md) - Create and organize chat sessions
 * [Settings reference](/docs/copilot/reference/copilot-settings.md) - All Copilot settings

docs/copilot/reference/copilot-settings.md

@@ -94,8 +94,6 @@ The team is continuously working on improving Copilot in VS Code and adding new
 | `setting(chat.utilitySmallModel)`<br/>Override the language model used for fast, lightweight [utility flows](/docs/copilot/customization/language-models.md#change-the-model-for-utility-tasks), such as commit messages, rename suggestions, and intent detection. A fast, inexpensive model is recommended. | `"Default"` |
 | `setting(github.copilot.chat.edits.suggestRelatedFilesFromGitHistory)` _(Experimental)_<br/>Suggest related files from git history in chat context. | `true` |
 | `setting(github.copilot.chat.localIndex.enabled)`<br/>Enable local session tracking for [session insights](/docs/copilot/chat/session-insights.md) and `/chronicle` commands. | `true` |
-| `setting(chat.sessionSync.enabled)`<br/>Enable [session sync](/docs/copilot/chat/session-sync.md) to GitHub.com. When enabled, Copilot session data syncs to your GitHub account for cross-device access. Requires `setting(github.copilot.chat.localIndex.enabled)` to also be enabled. | `true` |
-| `setting(chat.sessionSync.excludeRepositories)`<br/>Repository patterns to exclude from [session sync](/docs/copilot/chat/session-sync.md). Use exact `owner/repo` names or glob patterns like `my-org/*`. Sessions from matching repositories are stored locally only. | `[]` |
 
 ## Agent settings
 

docs/toc.json

@@ -76,7 +76,6 @@
           ["Overview", "/docs/copilot/chat/copilot-chat"],
           ["Chat Sessions", "/docs/copilot/chat/chat-sessions"],
           ["Session Insights", "/docs/copilot/chat/session-insights"],
-          ["Sync Sessions", "/docs/copilot/chat/session-sync"],
           ["Add Context", "/docs/copilot/chat/copilot-chat-context"],
           ["Inline Chat", "/docs/copilot/chat/inline-chat"],
           ["Review Edits", "/docs/copilot/chat/review-code-edits"],