Agent Manager TUI

Agent Manager TUI is a keyboard-first terminal app for managing local AI agent customization assets. The MVP focuses on Claude Code, Cursor, and GitHub Copilot.

Install

npm i -g @cchez/agent-manager-tui

Run

agent-manager-tui

The TUI opens to a main menu. Backup scans supported local agents, previews found and missing customization groups, asks for a backup destination, remembers the five most recent destinations for quick reuse, handles existing backups with snapshot or overwrite choices, then writes per-agent folders and a manifest. Restore reads a prior backup manifest, previews restorable groups, and copies supported assets back into local agent locations. Skill sync and custom agent sync compare folders across supported agents and copy or update selected entries so all agents can share the same set. MCP sync compares configured MCP server names and copies safe missing entries across supported agents.

MVP Scope

Included:

• Claude Code, Cursor, and GitHub Copilot as named agent types
• Human-readable customization assets such as main guidance files, instructions, prompts, rules, skills, commands, settings, and supported config files
• Per-agent backup folders
• A human-readable manifest
• Restore supported customization files from a prior backup
• Skill counts and differences across supported agents
• Selective skill sync for agents missing a skill
• Custom agent counts and differences across supported agents
• Selective custom agent sync for agents missing a custom agent
• MCP server counts and differences across supported agents
• Selective MCP setting sync for safe entries without auth-sensitive fields
• Complete, partial, failed, cancelled, and no-supported-assets result states

Not included:

• Dry-run restore
• Cloud sync, encryption, scheduling, or diffing
• Editing agent settings from the TUI
• Unknown-agent discovery
• Copying database-like or volatile storage

Restore

The restore workflow reads agent-manager-manifest.json from a backup root, latest/, or the newest snapshot under snapshots/, previews supported groups with backup content, then copies them back into local agent locations. Restore overwrites existing supported customization files for the selected groups. Unsupported storage is skipped.

Skill Sync

The sync workflow compares the direct children of each supported agent's skills directory:

• Claude Code: ~/.claude/skills
• Cursor: ~/.cursor/skills
• GitHub Copilot: ~/.copilot/skills

If one agent has a skill folder or file that another supported agent is missing, the TUI shows that difference. Same-name skills are also compared by content hash. When content differs, the newest modified version is listed as the source and selected outdated targets are updated. Same-name skills with identical content are left untouched.

Custom Agent Sync

The sync workflow compares the direct children of each supported agent's custom agents directory:

• Claude Code: ~/.claude/agents
• Cursor: ~/.cursor/agents
• GitHub Copilot: ~/.copilot/agents

If one agent has a custom agent file or folder that another supported agent is missing, the TUI shows that difference. Same-name custom agents are also compared by content hash. When content differs, the newest modified version is listed as the source and selected outdated targets are updated. Same-name custom agents with identical content are left untouched.

MCP Sync

The MCP sync workflow compares user-level MCP configuration files:

• Claude Code: ~/.claude.json, using the mcpServers object
• Cursor: ~/.cursor/mcp.json, using the mcpServers object
• GitHub Copilot / VS Code: VS Code user mcp.json, using the servers object

Only missing server names are copied. Existing server names are never overwritten.

Auth-sensitive entries are blocked from automatic sync and shown for manual review. This includes entries with env, envFile, headers, headersHelper, oauth, ${input:...} references, or token/secret/password/API-key-like fields. This is deliberate: each agent handles authentication slightly differently, and copying credentials blindly is unsafe.

Safety

The backup engine rejects destinations that contain a source path or are contained by a source path. Restore rejects backup sources that overlap agent paths for the same reason. Symlinks are preserved as links and are not followed to external targets. Skill and custom agent sync workflows compare content hashes before updating same-name entries. MCP sync only copies missing server names and does not overwrite existing MCP servers.

See docs/backup-layout.md and docs/supported-agents.md for details.