{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"vscode-codeontherocks-claude-config","slug":"claude-config","name":"Claude Config","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=CodeontheRocks.claude-config","page_url":"https://unfragile.ai/claude-config","categories":["code-editors"],"tags":[],"pricing":{"model":"freemium","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"vscode-codeontherocks-claude-config__cap_0","uri":"capability://automation.workflow.claude.desktop.configuration.file.management.with.multi.profile.persistence","name":"claude desktop configuration file management with multi-profile persistence","description":"Creates, reads, updates, and deletes named configuration profiles for Claude Desktop by directly manipulating the underlying configuration file system. The extension maintains multiple named configurations as discrete profiles, allowing developers to save and restore entire Claude Desktop states (including Filesystem MCP server settings, directory paths, and other parameters) without manual file editing. Profiles are persisted to disk and can be selected via Command Palette, enabling rapid context-switching between project-specific Claude configurations.","intents":["I want to save my current Claude Desktop configuration and restore it later without manually editing config files","I need to maintain separate Claude configurations for different projects with different MCP server settings","I want to quickly switch between pre-configured Claude setups without restarting or manually modifying files"],"best_for":["developers managing multiple projects with different Claude Desktop configurations","teams using Claude Desktop with project-specific Filesystem MCP server configurations","solo developers who frequently switch between different Claude working directories"],"limitations":["Configuration file format and schema are undocumented — no validation occurs before saving, risking incompatibility with Claude Desktop versions","No conflict detection if multiple VS Code instances attempt simultaneous configuration changes","Configuration file location is undocumented, making manual backup or migration difficult","No version control or diff preview — changes are applied immediately without review","Cannot validate that a saved configuration is actually compatible with the installed Claude Desktop version"],"requires":["VS Code 1.75.0 or higher","Claude Desktop application installed and accessible on the local system","Write permissions to Claude Desktop configuration file directory (location undocumented)"],"input_types":["configuration profile name (string)","directory path (string)","Claude Desktop config file (JSON or YAML format — undocumented)"],"output_types":["named configuration profile (persisted to disk)","configuration file (written to Claude Desktop config directory)"],"categories":["automation-workflow","configuration-management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-codeontherocks-claude-config__cap_1","uri":"capability://automation.workflow.active.directory.switching.for.claude.desktop.filesystem.mcp.context","name":"active directory switching for claude desktop filesystem mcp context","description":"Dynamically updates the active directory path in Claude Desktop's Filesystem MCP server configuration to point to the current VS Code workspace folder. When invoked, the extension reads the active workspace path from VS Code, writes it to Claude Desktop's configuration file, and optionally restarts Claude Desktop to apply the change. This enables Claude to access and operate on files in the current project directory without manual path configuration.","intents":["I want Claude Desktop to automatically work with files in my current VS Code project without manually changing its directory","I need to switch Claude's working directory to match my active VS Code workspace when I switch projects","I want Claude to have filesystem access to my current project's files via the Filesystem MCP server"],"best_for":["developers using Claude Desktop with Filesystem MCP for file-based operations","teams switching between multiple projects in VS Code and needing Claude to follow context","developers who want seamless Claude-to-project alignment without manual configuration"],"limitations":["Requires Claude Desktop to be restarted for the directory change to take effect (unless auto-restart is disabled)","No validation that the target directory exists or is accessible before writing to config","Cannot handle symbolic links or relative paths — behavior with non-standard paths is undocumented","If Claude Desktop is not installed or not accessible, the extension provides no error feedback (error handling is undocumented)","Directory switching is one-way: does not update VS Code workspace if Claude Desktop's config is changed externally"],"requires":["VS Code 1.75.0 or higher","Claude Desktop application installed and accessible","Active VS Code workspace folder (single-folder or multi-root workspace)","Write permissions to Claude Desktop configuration file"],"input_types":["current VS Code workspace folder path (automatically detected)"],"output_types":["updated Claude Desktop configuration file with new active directory path"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-codeontherocks-claude-config__cap_2","uri":"capability://automation.workflow.claude.desktop.application.lifecycle.management.with.configurable.restart.delay","name":"claude desktop application lifecycle management with configurable restart delay","description":"Provides commands to gracefully shutdown and restart the Claude Desktop application process from within VS Code. The extension can trigger a restart manually via the Command Palette or automatically when a configuration change is detected (if auto-restart is enabled). A configurable delay (default 2 seconds) is applied between shutdown and restart to ensure the process fully terminates before restarting, preventing race conditions or orphaned processes.","intents":["I want to restart Claude Desktop after changing its configuration without leaving VS Code","I need Claude Desktop to automatically restart when I switch configurations or directories","I want to control the timing of Claude Desktop restarts to avoid interrupting active work"],"best_for":["developers who frequently change Claude Desktop configurations and need quick restarts","teams using Claude Desktop with automated configuration switching workflows","developers who want to avoid manual application restarts between project switches"],"limitations":["No feedback on whether the restart succeeded or failed — restart status is not reported to the user","If Claude Desktop is not running, restart command may fail silently or produce undocumented errors","Restart delay is global and fixed per configuration — cannot be adjusted per-restart","No graceful shutdown of Claude Desktop's active sessions — restart is a hard process kill","Cannot detect if Claude Desktop is hung or unresponsive; restart will fail if process cannot be terminated"],"requires":["VS Code 1.75.0 or higher","Claude Desktop application installed and accessible on the system PATH or known installation directory","OS-level process management permissions (may require elevated privileges on some systems)"],"input_types":["restart delay in seconds (integer, configurable via extension settings, default 2)"],"output_types":["Claude Desktop process restart (no explicit output; success/failure is undocumented)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-codeontherocks-claude-config__cap_3","uri":"capability://automation.workflow.automatic.configuration.change.detection.and.triggered.application.restart","name":"automatic configuration change detection and triggered application restart","description":"Monitors for configuration changes (either manual edits via the extension or external file modifications) and automatically restarts Claude Desktop when changes are detected, if the `autoRestartAfterConfigChange` setting is enabled. This ensures that Claude Desktop picks up new configuration values without requiring manual user intervention. The restart is delayed by the configurable `restartDelay` setting to allow the configuration file write to complete before the process restarts.","intents":["I want Claude Desktop to automatically restart whenever I change its configuration so I don't have to manually restart it","I need configuration changes to take effect immediately without manual intervention","I want to avoid the overhead of manually restarting Claude Desktop after each configuration switch"],"best_for":["developers using automated configuration switching workflows who want zero-touch restarts","teams with CI/CD pipelines that modify Claude Desktop configurations programmatically","solo developers who want to minimize manual steps when switching between project configurations"],"limitations":["Auto-restart can be disruptive if Claude Desktop has active sessions or unsaved state — no session preservation","Detection mechanism is undocumented — unclear if it uses file watchers, polling, or manual triggers","No user confirmation before restart — auto-restart happens silently, potentially interrupting work","Restart delay is fixed and global — cannot be adjusted per configuration change","If restart fails, no error notification is provided to the user","Cannot distinguish between intentional configuration changes and accidental file modifications"],"requires":["VS Code 1.75.0 or higher","Claude Desktop application installed and accessible","`claude-config.autoRestartAfterConfigChange` setting enabled (default: true)","`claude-config.restartDelay` setting configured (default: 2 seconds)"],"input_types":["configuration file changes (detected automatically)","boolean setting for auto-restart enable/disable","integer setting for restart delay in seconds"],"output_types":["Claude Desktop process restart (automatic, no explicit output)"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-codeontherocks-claude-config__cap_4","uri":"capability://tool.use.integration.vs.code.command.palette.integration.for.configuration.operations","name":"vs code command palette integration for configuration operations","description":"Exposes all configuration management operations through VS Code's Command Palette interface, making them accessible via keyboard shortcuts (`Ctrl+Shift+P` / `Cmd+Shift+P`) and searchable command names. Commands include switching active directories, creating new configurations, selecting active configurations, viewing/editing configurations, deleting configurations, and restarting Claude Desktop. This provides a unified, discoverable interface for all extension operations without requiring custom keybindings or menu navigation.","intents":["I want quick access to Claude configuration commands without leaving the editor or using the mouse","I need to discover available configuration operations through VS Code's standard command interface","I want to bind configuration commands to custom keybindings for faster workflow integration"],"best_for":["developers familiar with VS Code's Command Palette workflow","power users who want keyboard-driven configuration management","teams standardizing on VS Code as the primary development environment"],"limitations":["No custom keybindings are documented — all access requires opening the Command Palette first","Command names are fixed and cannot be customized or aliased","No fuzzy search or command history — relies on VS Code's built-in command search","Commands are not available in VS Code's menu bar or context menus — Command Palette only","No command grouping or categorization beyond the command name prefix"],"requires":["VS Code 1.75.0 or higher","Claude Config extension installed and enabled"],"input_types":["command name (string, selected from Command Palette)","user input for configuration profile names or directory selection (context-dependent)"],"output_types":["command execution result (configuration change, restart, profile selection, etc.)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-codeontherocks-claude-config__cap_5","uri":"capability://automation.workflow.extension.settings.configuration.for.auto.restart.behavior.and.timing","name":"extension settings configuration for auto-restart behavior and timing","description":"Provides two configurable settings in VS Code's extension settings UI to control the automatic restart behavior and timing of Claude Desktop. The `autoRestartAfterConfigChange` boolean setting enables or disables automatic restarts when configurations change (default: true), and the `restartDelay` integer setting controls the delay in seconds between shutdown and restart (default: 2 seconds). These settings are persisted in VS Code's configuration system and can be modified via the Settings UI or by editing `settings.json` directly.","intents":["I want to disable automatic restarts so Claude Desktop doesn't interrupt my work when I switch configurations","I need to adjust the restart delay to account for slower systems or network-dependent startup","I want to control the extension's restart behavior globally across all my projects"],"best_for":["developers who want fine-grained control over Claude Desktop restart behavior","teams with system-specific requirements (e.g., slower machines needing longer restart delays)","developers who prefer manual restarts over automatic ones"],"limitations":["Settings are global and apply to all projects — no per-project configuration overrides","No validation of the `restartDelay` value — invalid values (negative, non-integer) may cause errors","Settings changes take effect immediately — no confirmation or preview before applying","No documentation on optimal `restartDelay` values for different system speeds","Cannot configure restart behavior per configuration profile — only global settings available"],"requires":["VS Code 1.75.0 or higher","Claude Config extension installed"],"input_types":["boolean value for `autoRestartAfterConfigChange` (true or false)","integer value for `restartDelay` (seconds, default 2)"],"output_types":["VS Code configuration file update (settings.json or UI-managed settings)"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":40,"verified":false,"data_access_risk":"high","permissions":["VS Code 1.75.0 or higher","Claude Desktop application installed and accessible on the local system","Write permissions to Claude Desktop configuration file directory (location undocumented)","Claude Desktop application installed and accessible","Active VS Code workspace folder (single-folder or multi-root workspace)","Write permissions to Claude Desktop configuration file","Claude Desktop application installed and accessible on the system PATH or known installation directory","OS-level process management permissions (may require elevated privileges on some systems)","`claude-config.autoRestartAfterConfigChange` setting enabled (default: true)","`claude-config.restartDelay` setting configured (default: 2 seconds)"],"failure_modes":["Configuration file format and schema are undocumented — no validation occurs before saving, risking incompatibility with Claude Desktop versions","No conflict detection if multiple VS Code instances attempt simultaneous configuration changes","Configuration file location is undocumented, making manual backup or migration difficult","No version control or diff preview — changes are applied immediately without review","Cannot validate that a saved configuration is actually compatible with the installed Claude Desktop version","Requires Claude Desktop to be restarted for the directory change to take effect (unless auto-restart is disabled)","No validation that the target directory exists or is accessible before writing to config","Cannot handle symbolic links or relative paths — behavior with non-standard paths is undocumented","If Claude Desktop is not installed or not accessible, the extension provides no error feedback (error handling is undocumented)","Directory switching is one-way: does not update VS Code workspace if Claude Desktop's config is changed externally","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.46,"quality":0.37,"ecosystem":0.15000000000000002,"match_graph":0.25,"freshness":0.9,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:34.118Z","last_scraped_at":"2026-05-03T15:20:40.998Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=claude-config","compare_url":"https://unfragile.ai/compare?artifact=claude-config"}},"signature":"VTQ4qdjQFGmYqOy4Mznw/+dAzf+hiHdkDwUZ1ewiXjScxkLj0/t8ET0nBEuI9A18PeWXQi6MnlApc0tkDl5gDA==","signedAt":"2026-06-16T22:49:56.166Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/claude-config","artifact":"https://unfragile.ai/claude-config","verify":"https://unfragile.ai/api/v1/verify?slug=claude-config","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}