Settings Storage and Sync

Settings, Storage, and Sync

简体中文 · Home

The Settings header includes keyword search for filtering and jumping to individual settings.

Settings index

Section	Purpose
Channels	Models, APIs, tool mode, retries, and custom request fields
Tools	Tool availability, options, and per-turn call limits
Auto Execute	Which tools run directly or require confirmation
MCP	Add and manage MCP servers
Checkpoints	Automatic checkpoints, exclusions, preview, and cleanup
Summarization	Automatic thresholds, model, and prompt
Image Generation / Dependencies	Image services and optional tool dependencies
Context	File tree, tabs, diagnostics, and pinned files
Prompts	Modes, templates, prompt entries, variables, and tool policy
Token Counting	Counting method per channel
Sub-Agents	Specialized agents, tools, runtime, and model policy
Sound / Appearance	Sounds, language, animation, TPS, and streaming effects
Usage	Tokens, estimated cost, and IDE activity time
Memory	OptMem prompt, raw entries, and runtime limits
General	Proxy, updates, storage path, and settings transfer

VS Code Settings Sync

Most options live under the graycode.* namespace and can follow VS Code Settings Sync, including tool toggles, auto-execution policies, prompts, UI preferences, token counting, and image tools.

The following machine-specific settings are not synchronized:

• graycode.proxy
• graycode.storagePath
• graycode.activeChannelId

This prevents proxy ports, local data locations, and the active channel from overwriting one another across devices.

Local data and storage path

Conversation history, checkpoints, persistent memory, and selected runtime data remain local. Change and migrate the data path under Settings → General; a window reload is normally required afterward.

Create a filesystem-level backup before moving or cleaning data. Avoid moving the same directory while a synchronization service is actively writing it.

Settings import and export

Use Settings → General or GrayCode: Export Settings / GrayCode: Import Settings from the Command Palette. Exports include channels, MCP servers, Skills, and VS Code settings, with options to skip existing entries or overwrite them.

Settings exports do not include:

• Conversation history
• Checkpoints
• Raw persistent-memory data
• Workspace files

Migrate the storage path or back these up separately.

Checkpoints

Checkpoints restore workspace state around tool batches or important messages. Configure automatic phases, included tools, and exclusions, or create one manually from the input toolbar. Save or resolve unsaved editor content before restoration.

Checkpoints are not a replacement for version control. Important code should still be committed and backed up remotely with Git.

Migration from older versions

When upgrading, GrayCode attempts to migrate the old globalStorage/settings/settings.json into VS Code Settings and backs up the original as settings.json.bak. If settings look incorrect afterward, check whether workspace-level values override global values before importing a backup.