What problem does it solve?
Moving from the Warp desktop app to Warp Agent CLI normally means manually recreating settings and MCP server configurations, with the risk of leaking credentials or overwriting existing CLI state. This Skill performs a narrow, redacted migration of only the supported subset of data.
Core Features & Use Cases
- Shared Settings Inspection: Uses the generated JSON Schema's
x-warp-surfaces annotation to find settings valid in both GUI and CLI, then reports missing, equal, and conflicting values without exposing unrelated data.
- Redacted MCP Merge: Merges global file-based MCP server definitions with destination-wins conflict handling, skipping definitions that contain literal credentials or managed/template installation markers.
- Fingerprint-Bound Approval: Dry-run output includes a SHA-256 fingerprint that must be passed to the apply step, so the merge only executes against the exact reviewed inputs.
- Use Case: A developer installs Warp Agent CLI on a machine that already runs the Warp desktop app and wants their compatible settings and global MCP servers carried over without copying tokens, OAuth state, or GUI-only preferences.
Quick Start
Ask Warp Agent CLI to migrate your existing Warp GUI setup into the CLI, then review and approve the redacted settings and MCP merge proposal it presents.