Config Manager Connect

Config Manager Connect

Use this skill when the user asks to connect Codex, Claude, or another supported host through AI Config Sync Manager.

Behavior

• If the user passes -h / --help (or asks for usage/help), run ... connect --help and print the CLI output as-is — do not execute the connect flow.
• Resolve the bundled CLI from the Codex plugin root: AI_CONFIG_SYNC_HOST=codex "$HOME/.agents/plugins/ai-config-sync-manager/bin/ai-config-sync" connect. The launcher resolves the runtime via AI_CONFIG_SYNC_ROOT (dev override) → PATH ai-config-sync → npm exec fallback.
• Always export AI_CONFIG_SYNC_HOST=codex before invoking the CLI from this skill so the default sync direction is codex -> claude.
• The connect command initializes the user config root at $HOME/.ai-config-sync-manager and creates $HOME/.ai-config-sync-manager/status-ignore.json when missing.
• Do not edit Codex, Claude, skills, commands, MCP, permissions, or hooks directly from this skill.
• If the bundled CLI is unavailable, report that the user must npm install -g ai-config-sync-manager (or run npm link from the repo) and re-run connect.
• Prefer explicit user confirmation before installing, registering, or writing anything outside the current plugin flow.
• Preserve the OSS purpose: this plugin is a thin open-source bridge to the bundled CLI, not a proprietary sync service.

Safety

• Treat host permissions, hooks, and custom commands as manual-review areas.
• When the CLI proposes changes, show the summary and ask for confirmation before continuing.
• If the CLI reports backups, mention their location before any apply step proceeds.