tui-migrate-setup

Migrates shared settings and global MCP configs from Warp GUI to Warp Agent CLI.

64.7k|5.5k|Updated Jul 8, 2021
One-click install
npx skills add https://github.com/warpdotdev/warp --skill tui-migrate-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tui-migrate-setup
Source: https://github.com/warpdotdev/warp/tree/main/resources/bundled/skills/tui-migrate-setup
Command: npx skills add https://github.com/warpdotdev/warp --skill tui-migrate-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about tui-migrate-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my Warp GUI settings to Warp Agent CLI?

Run this Skill inside Warp Agent CLI and it inspects only settings whose schema annotation lists both gui and tui surfaces. You review a redacted proposal and approve each addition or conflict overwrite before anything is written.

How do I copy MCP servers from the Warp desktop app to Warp Agent CLI?

The Skill's merge helper performs a dry run of the global MCP config, reporting only redacted counts and a fingerprint. After your explicit approval, it applies the merge with destination-wins conflict handling and creates a timestamped backup.

Does the migration copy credentials, tokens, or OAuth state?

No. Credentials, refresh tokens, API keys, Keychain items, OAuth grants, and MCP installation state are never copied. Definitions containing literal secrets are skipped, and authenticated servers must be reauthenticated inside Warp Agent CLI.

What Python version is required for the Warp setup migration?

Python 3.11 or newer is required because the settings inspector relies on the tomllib module for TOML parsing. If tomllib is unavailable, settings inspection is unsupported and the Skill will not fall back to reading the GUI settings file directly.

What Warp data cannot be migrated to Warp Agent CLI?

Keybindings, themes, launch and tab configs, local workflows, shell preferences, command history, GUI state, SQLite databases, and project-scoped or third-party MCP configs are unsupported. Rules, skills, and Drive objects are already shared or appear after login.

What happens if my MCP config changes between preview and apply?

The apply step requires the exact fingerprint from the dry run. If either file changed, the helper rejects the fingerprint without writing anything, and you must run a fresh dry run and approve again.