Agent skill

Warp GUI to Agent CLI Migration

by warpdotdev in warpdotdev/warp

Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

AGPL-3.0Auto-check passedAgent Workflows

Install Warp GUI to Agent CLI Migration

skills CLI
$ npx skills add warpdotdev/warp --skill tui-migrate-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install warpdotdev/warp tui-migrate-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/bundled/skills/tui-migrate-setup .claude/skills/tui-migrate-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tui-migrate-setup
GitHub stars
65k
Used in
1 other repo
Token cost
~2.1k tokens
SKILL.md length
1,022 words
Files
11 (incl. scripts, references)
Skills in repo
46
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

  • Works in 7 steps: Set expectations → Check the local runtime → Inspect without mutating → …
  • Setting up Warp Agent CLI from an existing Warp desktop installation
  • SKILL.md covers Resolved paths, Safety boundaries and Workflow
  • Runs Python scripts from its folder; calls python3

What it does

The migration is narrow and local: GUI files are treated as untrusted input, and the Warp Agent CLI destination is preserved rather than overwritten freely. It works only from host-provided paths for the settings schema, the GUI and CLI settings files, and the GUI and CLI global MCP config files; if any resolved path is empty or unresolved, that part of the migration stops and reports the problem rather than guessing an alternate path.

Strict safety boundaries govern MCP migration: only the bundled merge_mcp_config.py script may read either MCP config file, and its output is limited to counts, booleans, status codes and a fingerprint, so server names, commands, URLs, headers, environment variables and credentials are never printed, summarized or requested from the user. Credentials, refresh tokens, API keys, Keychain items and OAuth state are never copied; gallery-installed MCP servers must be reinstalled and authenticated servers reauthenticated in the CLI directly.

Only the resolved global MCP file is migrated, never project-scoped or third-party files, and only settings whose generated x-warp-surfaces annotation lists both gui and tui are eligible, with destination comments and CLI-exclusive settings preserved. A migration-matrix reference and two Python helper scripts, with their own test fixtures, back the workflow.

When your agent uses it

  • Setting up Warp Agent CLI from an existing Warp desktop installation
  • Copying compatible global settings from the Warp GUI to the Agent CLI
  • Moving a global file-based MCP server configuration into Warp Agent CLI
  • Understanding which Warp data is already shared between the GUI and the CLI

Example prompts

  • “Set up Warp Agent CLI using my existing Warp GUI configuration.”
  • “Copy my global MCP servers from the Warp desktop app into Warp Agent CLI.”
  • “Which of my Warp GUI settings are actually shared with the Agent CLI?”

Requirements

  • Warp Agent CLI
  • Python 3.11 or newer for local JSON and TOML inspection
  • Compatibility (from SKILL.md): Requires Python 3.11 or newer for local JSON and TOML inspection. This skill is available only in Warp Agent CLI.

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Set expectations
  2. Check the local runtime
  3. Inspect without mutating
  4. Present a redacted proposal
  5. Apply approved settings conservatively
  6. Apply the approved MCP merge
  7. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit f571865. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires Python 3.11 or newer for local JSON and TOML inspection. This skill is available only in Warp Agent CLI.

    From compatibility in the SKILL.md frontmatter.

Context cost

Warp GUI to Agent CLI Migration loads about 2.1k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 1,022 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~96
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from warpdotdev/warp at commit f571865, republished under its AGPL-3.0 licence (© warpdotdev). 1,022 words, ~2,057 tokens.

Download SKILL.mdSave it as .claude/skills/tui-migrate-setup/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
tui-migrate-setup
description
Migrates the supported subset of an existing Warp GUI setup into Warp Agent CLI without exposing credentials or application state. Use in Warp Agent CLI when a user wants to copy or move compatible settings or global file-based MCP servers from the desktop app, set up Warp Agent CLI from an existing GUI installation, or understand which Warp data is already shared.
compatibility
Requires Python 3.11 or newer for local JSON and TOML inspection. This skill is available only in Warp Agent CLI.

Migrate a Warp GUI setup to Warp Agent CLI

Guide the user through a narrow, local migration. Treat the GUI files as untrusted inputs and preserve the Warp Agent CLI destination. Read references/migration-matrix.md before starting.

Resolved paths

Use these host-provided paths. Do not substitute ~/.warp or infer another channel/profile:

  • Settings schema: {{settings_schema_path}}
  • GUI settings: {{gui_settings_file_path}}
  • Warp Agent CLI settings: {{tui_settings_file_path}}
  • GUI global MCP config: {{gui_mcp_config_file_path}}
  • Warp Agent CLI global MCP config: {{tui_mcp_config_file_path}}

If any rendered path is empty, unresolved, or still contains double braces, stop that part of the migration and report that the current installation could not resolve it. In particular, fail closed when the GUI source profile is ambiguous. If the rendered schema or either helper script is missing, report a build artifact defect and stop. Do not substitute alternate paths or inspect configuration files directly.

Safety boundaries

  • Never use a file-reading tool, cat, grep, a shell expansion, or an ad hoc script to inspect either MCP config. Only scripts/merge_mcp_config.py may read those files. Its output is intentionally limited to counts, booleans, status codes, and a fingerprint.
  • Never print or summarize MCP server names, definitions, commands, URLs, headers, environment variables, or values. Do not ask the user to paste them.
  • Never copy credentials, refresh tokens, API keys, Keychain/credential-store items, secure storage, SQLite rows, MCP installation/running state, or OAuth state. Templatable/gallery MCP installations must be reinstalled in Warp Agent CLI, and authenticated servers must be reauthenticated there.
  • Migrate only the resolved Warp global MCP file. Do not inspect or migrate project-scoped or third-party MCP files because doing so changes scope and working-directory behavior.
  • Do not migrate private or GUI-only settings. The generated x-warp-surfaces annotation is the source of truth; a setting is eligible only when its array contains both gui and tui.
  • Do not overwrite a value in Warp Agent CLI unless the user explicitly approves that exact conflict. Preserve destination comments, unknown keys, and settings exclusive to Warp Agent CLI.

Workflow

Limit inspection to the categories the user actually requested. For an MCP-only request, do not inspect settings. For a request limited to templatable/gallery installations, OAuth, credentials, or another unsupported category, explain the supported Warp Agent CLI setup path without running either file inspector.

1. Set expectations

Briefly summarize the four migration categories from the matrix:

  1. Rules, user/repository skills, and bundled skills are already discovered from shared paths. Drive objects, saved prompts, and cloud execution profiles appear after Warp Agent CLI login and sync.
  2. Only schema-declared settings shared by the GUI and Warp Agent CLI, and raw global file-based MCP definitions, can be imported.
  3. Login, templatable MCP installations, OAuth, and provider credentials require reauthentication or reinstallation.
  4. Keybindings, themes, launch/tab configs, local workflows, shell/startup preferences, GUI state, command history, and databases are unsupported.

Do not claim that logging into Warp Agent CLI migrates local files.

2. Check the local runtime

Run Python 3.11 or newer. If tomllib is unavailable, explain that settings inspection is unsupported in this runtime; do not fall back to reading the GUI settings file into model context.

3. Inspect without mutating

Run the settings inspector:

sh
python3 "{{skill_dir}}/scripts/inspect_shared_settings.py" \
  --schema "{{settings_schema_path}}" \
  --source "{{gui_settings_file_path}}" \
  --destination "{{tui_settings_file_path}}"

The JSON output contains only eligible setting paths and their GUI and Warp Agent CLI values. Do not independently open the GUI settings file.

Run the MCP helper in dry-run mode:

sh
python3 "{{skill_dir}}/scripts/merge_mcp_config.py" \
  --source "{{gui_mcp_config_file_path}}" \
  --destination "{{tui_mcp_config_file_path}}" \
  --dry-run

Retain the returned fingerprint exactly for the apply step. A dry run never creates a file or backup.

Show full SKILL.md (459 more words)Show less
4. Present a redacted proposal

For settings, present only the eligible dotted names and values emitted by the inspector. Group them as:

  • missing from Warp Agent CLI and available to add;
  • already equal;
  • conflicting, where the existing Warp Agent CLI value remains unchanged by default.

Call out that agent permission settings can expand what commands, file reads, or other actions are approved automatically. For a machine-local file allowlist, offer a source path only after checking that the path is valid on this host. Exclude nonexistent or host-inapplicable paths from the proposal.

For MCP, report only the helper's redacted counts: eligible additions, destination conflicts, definitions skipped because they may contain literal credentials, definitions requiring reinstallation, and whether anything would change. Include the helper's exact fingerprint verbatim in the proposal and approval prompt so a later apply is bound to the reviewed inputs; the fingerprint is opaque and does not reveal config contents. Never infer or reveal identities from the counts.

Ask for explicit approval before mutation. Approval must separately cover:

  • each settings addition;
  • each settings conflict the user wants to overwrite;
  • the redacted global MCP merge.

If the user approves only some settings, edit only those settings. Destination values win all unapproved conflicts.

5. Apply approved settings conservatively

Before editing, reject a symlink at the Warp Agent CLI settings path. If the destination exists, create a timestamped backup beside it and restrict the backup to the current user on Unix. If it does not exist, create it with user-only permissions on Unix.

Read only the Warp Agent CLI destination and edit it in place. Add or update only approved shared dotted keys. Preserve its comments, formatting outside the edited keys, unknown keys, and values exclusive to Warp Agent CLI. Do not regenerate or replace the whole TOML document. If a safe surgical edit is not possible, stop and explain why rather than using a lossy TOML serializer.

6. Apply the approved MCP merge

Pass the exact dry-run fingerprint:

sh
python3 "{{skill_dir}}/scripts/merge_mcp_config.py" \
  --source "{{gui_mcp_config_file_path}}" \
  --destination "{{tui_mcp_config_file_path}}" \
  --apply \
  --fingerprint "<dry-run fingerprint>"

If either file changed after preview, the helper rejects the fingerprint without writing. Run a fresh dry run and ask for approval again. The destination wins all name conflicts; do not offer an overwrite mode.

7. Verify

Rerun the settings inspector and MCP dry run. Confirm that approved settings now match and the MCP helper reports no remaining eligible additions. Do not inspect MCP files directly to verify.

Report:

  • settings changed and conflicts left unchanged;
  • redacted MCP counts and whether a backup was created;
  • any skipped credential-bearing or managed definitions;
  • Warp Agent CLI login/sync, MCP reinstallation, or reauthentication still required;
  • whether a Warp Agent CLI restart is necessary based on the current product behavior.

If verification fails, leave backups intact and report the sanitized helper status. Never expose file contents while troubleshooting.

© warpdotdev, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (scripts, references) in resources/bundled/skills/tui-migrate-setup of warpdotdev/warp.

  • SKILL.md
  • references/migration-matrix.md
  • scripts/inspect_shared_settings.py
  • scripts/merge_mcp_config.py
  • tests/fixtures/destination_mcp.json
  • tests/fixtures/gui_settings.toml
  • tests/fixtures/settings_schema.json
  • tests/fixtures/source_mcp.json
  • tests/fixtures/tui_settings.toml
  • tests/test_inspect_shared_settings.py
  • tests/test_merge_mcp_config.py

Open the folder on GitHubat commit f571865

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in warpdotdev/warp, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Warp GUI to Agent CLI Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Warp GUI to Agent CLI Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Warp GUI to Agent CLI Migration this skillwarpdotdev/warp65k1 repos~2.1kAutomated safety check: PassAGPL-3.0
Chorus CLIChorus-AIDLC/Chorus1.2k—~1.2kAutomated safety check: NotesAGPL-3.0
Add Integrationindranilbanerjee/digital-marketing-pro8541 repos~1.8kAutomated safety check: NotesMIT
Auto Review Loop LLMAI4Scientist/nano-scientist1284 repos~1.8kAutomated safety check: WarnNone
MCP Security Auditboshi-xixixi/TraeSkill274—~2.2kAutomated safety check: PassMIT
Flow Contextflowexec/flow137—~654Automated safety check: PassApache-2.0

Similar skills

  • Chorus CLI

    Chorus-AIDLC/Chorus

    How to install, configure, and use the chorus CLI — install it, manage agents with chorus agents (add/remove/list), the connection environment variables, and MCP operations via chorus mcp.

    1.2k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Add Integration

    indranilbanerjee/digital-marketing-pro

    Walk through adding a custom MCP server integration to the plugin — searches npm for an existing MCP package (or scaffolds a custom server from the plugin's guide), generates the exact .mcp.json…

    854 GitHub starsUsed in 1 repo~1.8k tokens
    Agent WorkflowsAuto-check: notes
  • Auto Review Loop LLM

    AI4Scientist/nano-scientist

    Autonomous research review loop using any OpenAI-compatible LLM API.

    128 GitHub starsUsed in 4 repos~1.8k tokens
    Agent WorkflowsAuto-check: warnings
  • MCP Security Audit

    boshi-xixixi/TraeSkill

    Audit MCP (Model Context Protocol) server configurations for security issues.

    274 GitHub stars~2.2k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed
  • Flow Context

    flowexec/flow

    This project uses flow for automation. An agent skill from flowexec/flow.

    137 GitHub stars~654 tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed
  • Installs Codex as an agent provider for NanoClaw groups, with streaming, MCP tools, server-side history and vault-only credentials, next to or instead of Claude.

    31k GitHub stars~2.3k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check: notes

More from warpdotdev/warp

All 46 skills in this repo
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Auto-check passed
  • Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Auto-check passed
  • Warp Factory Files

    warpdotdev/warp

    Authors and edits file-based Warp software factory definitions rooted at factory.yaml, covering agents, automations, scorers and webhooks, and validates them before a pull request.

    65k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Auto-check passed
  • Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.

    65k GitHub starsUsed in 3 repos~4.6k tokens
    Auto-check passed
  • Maps published Figma components to their code implementations with Code Connect, using the Figma MCP suggestion and mapping tools.

    65k GitHub starsUsed in 2 repos~4.2k tokens
    Auto-check passed

Categories

Questions about Warp GUI to Agent CLI Migration

What does Warp GUI to Agent CLI Migration do?

Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state. The migration is narrow and local: GUI files are treated as untrusted input, and the Warp Agent CLI destination is preserved rather than overwritten freely. It works only from host-provided paths for the settings schema, the GUI and CLI settings files, and the GUI and CLI global MCP config files; if any resolved path is empty or unresolved, that part of the migration stops and reports the problem rather than guessing an alternate path.

When should I use Warp GUI to Agent CLI Migration?

Warp GUI to Agent CLI Migration fits situations like: setting up Warp Agent CLI from an existing Warp desktop installation; copying compatible global settings from the Warp GUI to the Agent CLI; moving a global file-based MCP server configuration into Warp Agent CLI; understanding which Warp data is already shared between the GUI and the CLI.

How do I install Warp GUI to Agent CLI Migration in Claude Code?

Run `npx skills add warpdotdev/warp --skill tui-migrate-setup -a claude-code`. Or copy the skill folder (resources/bundled/skills/tui-migrate-setup in warpdotdev/warp) into .claude/skills/tui-migrate-setup in your project. Claude Code loads it when a task matches its description.

How do I install Warp GUI to Agent CLI Migration in Codex?

Run `npx skills add warpdotdev/warp --skill tui-migrate-setup -a codex`. Or copy the skill folder (resources/bundled/skills/tui-migrate-setup in warpdotdev/warp) into .agents/skills/tui-migrate-setup in your project. Codex loads it when a task matches its description.

Can I use Warp GUI to Agent CLI Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add warpdotdev/warp --skill tui-migrate-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tui-migrate-setup, .gemini/skills/tui-migrate-setup, .github/skills/tui-migrate-setup and .opencode/skills/tui-migrate-setup in your project.

What does Warp GUI to Agent CLI Migration need to run?

Going by SKILL.md and its folder, Warp GUI to Agent CLI Migration needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Warp Agent CLI; Python 3.11 or newer for local JSON and TOML inspection. Compatibility (from SKILL.md): Requires Python 3.11 or newer for local JSON and TOML inspection. This skill is available only in Warp Agent CLI..

Does Warp GUI to Agent CLI Migration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Warp GUI to Agent CLI Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Warp GUI to Agent CLI Migration use?

Warp GUI to Agent CLI Migration is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Warp GUI to Agent CLI Migration use?

About 2.1k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 767 tokens, read only when the agent opens those files.

What are the alternatives to Warp GUI to Agent CLI Migration?

Skills that share tags, products or a category with Warp GUI to Agent CLI Migration: Chorus CLI (Chorus-AIDLC/Chorus, 1.2k stars), Add Integration (indranilbanerjee/digital-marketing-pro, 854 stars), Auto Review Loop LLM (AI4Scientist/nano-scientist, 128 stars) and MCP Security Audit (boshi-xixixi/TraeSkill, 274 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Warp GUI to Agent CLI Migration?

warpdotdev (a GitHub organization) maintains it in warpdotdev/warp, which has 65,380 GitHub stars. The repository holds 46 skills in this directory. The repository was last updated on October 7, 2026.

Source: warpdotdev/warp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.