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.
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.
$ npx skills add warpdotdev/warp --skill tui-migrate-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install warpdotdev/warp tui-migrate-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "tui-migrate-setup" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/tui-migrate-setup into .claude/skills/tui-migrate-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-migrate-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/tui-migrate-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add warpdotdev/warp --skill tui-migrate-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install warpdotdev/warp tui-migrate-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/bundled/skills/tui-migrate-setup .agents/skills/tui-migrate-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tui-migrate-setup" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/tui-migrate-setup into .agents/skills/tui-migrate-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-migrate-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add warpdotdev/warp --skill tui-migrate-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install warpdotdev/warp tui-migrate-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/bundled/skills/tui-migrate-setup .cursor/skills/tui-migrate-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tui-migrate-setup" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/tui-migrate-setup into .cursor/skills/tui-migrate-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-migrate-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/warpdotdev/warp.git --path resources/bundled/skills/tui-migrate-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add warpdotdev/warp --skill tui-migrate-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install warpdotdev/warp tui-migrate-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/bundled/skills/tui-migrate-setup .gemini/skills/tui-migrate-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tui-migrate-setup" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/tui-migrate-setup into .gemini/skills/tui-migrate-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-migrate-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install warpdotdev/warp tui-migrate-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add warpdotdev/warp --skill tui-migrate-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/bundled/skills/tui-migrate-setup .github/skills/tui-migrate-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tui-migrate-setup" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/tui-migrate-setup into .github/skills/tui-migrate-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-migrate-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add warpdotdev/warp --skill tui-migrate-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install warpdotdev/warp tui-migrate-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/bundled/skills/tui-migrate-setup .opencode/skills/tui-migrate-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tui-migrate-setup" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/tui-migrate-setup into .opencode/skills/tui-migrate-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tui-migrate-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
tui-migrate-setupMigrates 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.
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.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit f571865. It shows what the files ask for, not the result of running them.
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.
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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.
The full file from warpdotdev/warp at commit f571865, republished under its AGPL-3.0 licence (© warpdotdev). 1,022 words, ~2,057 tokens.
.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.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.
Use these host-provided paths. Do not substitute ~/.warp or infer another
channel/profile:
{{settings_schema_path}}{{gui_settings_file_path}}{{tui_settings_file_path}}{{gui_mcp_config_file_path}}{{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.
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.x-warp-surfaces annotation is the source of truth; a setting is eligible only
when its array contains both gui and tui.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.
Briefly summarize the four migration categories from the matrix:
Do not claim that logging into Warp Agent CLI migrates local files.
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.
Run the settings inspector:
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:
python3 "{{skill_dir}}/scripts/merge_mcp_config.py" \
--source "{{gui_mcp_config_file_path}}" \
--destination "{{tui_mcp_config_file_path}}" \
--dry-runRetain the returned fingerprint exactly for the apply step. A dry run never creates a file or backup.
For settings, present only the eligible dotted names and values emitted by the inspector. Group them as:
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:
If the user approves only some settings, edit only those settings. Destination values win all unapproved conflicts.
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.
Pass the exact dry-run fingerprint:
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.
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:
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
SKILL.md and 10 other files (scripts, references) in resources/bundled/skills/tui-migrate-setup of warpdotdev/warp.
Open the folder on GitHubat commit f571865
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Warp GUI to Agent CLI Migration this skillwarpdotdev/warp | 65k | 1 repos | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Chorus CLIChorus-AIDLC/Chorus | 1.2k | — | ~1.2k | Automated safety check: Notes | AGPL-3.0 | |
| Add Integrationindranilbanerjee/digital-marketing-pro | 854 | 1 repos | ~1.8k | Automated safety check: Notes | MIT | |
| Auto Review Loop LLMAI4Scientist/nano-scientist | 128 | 4 repos | ~1.8k | Automated safety check: Warn | None | |
| MCP Security Auditboshi-xixixi/TraeSkill | 274 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Flow Contextflowexec/flow | 137 | — | ~654 | Automated safety check: Pass | Apache-2.0 |
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.
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…
AI4Scientist/nano-scientist
Autonomous research review loop using any OpenAI-compatible LLM API.
boshi-xixixi/TraeSkill
Audit MCP (Model Context Protocol) server configurations for security issues.
flowexec/flow
This project uses flow for automation. An agent skill from flowexec/flow.
nanocoai/nanoclaw
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.
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
warpdotdev/warp
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.
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.
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.
warpdotdev/warp
Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.
warpdotdev/warp
Maps published Figma components to their code implementations with Code Connect, using the Figma MCP suggestion and mapping tools.
Works with
Categories
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.
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.
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.
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.
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.
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..
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.
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.
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.
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.
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.
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.