What Files Are Removed During Agent Reach Uninstall?

Running agent-reach uninstall deletes the local configuration directory at ~/.agent-reach, skill directories for OpenClaw, Claude Code, and Agent platforms, and MCP entries from the mcporter tool, while preserving the Python package and auxiliary CLI tools for manual removal.

When you need to completely remove Agent Reach from your system, understanding exactly which files are deleted helps prevent accidental data loss. The agent-reach uninstall command, implemented in the Panniantong/Agent-Reach repository, targets specific directories and configurations created during installation and normal usage. This command systematically cleans up three main categories of data while leaving the core package installation for optional manual removal.

Configuration Directory Removal

The uninstall command permanently deletes the ~/.agent-reach directory, which houses the config.yaml file containing all stored tokens, cookies, and API keys. This removal occurs in agent_reach/cli.py at lines 1364-1379, where the logic checks for the directory existence and performs a recursive deletion.

To preserve your configuration data during uninstallation, use the --keep-config flag:

agent-reach uninstall --keep-config

When this flag is supplied, the command skips the configuration directory removal while still processing other cleanup steps.

Skill Files and Directories

The command removes skill directories installed for three supported platforms. According to the implementation in agent_reach/cli.py (lines 1383-1395), the following paths are targeted for deletion or unlinking:

• ~/.openclaw/skills/agent-reach (OpenClaw platform)
• ~/.claude/skills/agent-reach (Claude Code platform)
• ~/.agents/skills/agent-reach (Agent platform)

If these directories are symlinks, the command unlinks them rather than recursively deleting the contents. This ensures that any system-wide or shared installations remain intact while removing the local references.

MCP Entry Cleanup

For users who have the mcporter tool installed, the uninstall command removes specific MCP entries added by Agent Reach. In agent_reach/cli.py at lines 1406-1424, the code identifies and strips out the exa and xiaohongshu entries from the mcporter configuration files. This prevents orphaned MCP server configurations from persisting after the main Agent Reach data is removed.

Components Left for Manual Removal

The command explicitly does not uninstall the Python package itself or auxiliary tools that may have been installed alongside Agent Reach. Instead, it prints optional removal instructions at the end of execution (sourced from agent_reach/cli.py, lines 1378-1385):

# Remove the Agent Reach Python package

pip uninstall agent-reach

# Remove tools installed by Agent Reach

npm uninstall -g mcporter
pipx uninstall twitter-cli
npm uninstall -g undici

These steps remain the user's responsibility to execute manually if they desire a complete system purge.

Previewing Changes With Dry-Run Mode

Before executing destructive operations, you can preview exactly which files are removed during Agent Reach uninstall using the --dry-run flag. This mode simulates the uninstallation process without making any actual changes to your filesystem.

agent-reach uninstall --dry-run

Typical output shows the specific paths and entries that would be affected:

Agent Reach Uninstaller
========================================
[dry-run] Would remove config directory: /home/user/.agent-reach
[dry-run] Would remove OpenClaw skill: /home/user/.openclaw/skills/agent-reach
[dry-run] Would remove Claude Code skill: /home/user/.claude/skills/agent-reach
[dry-run] Would remove Agent skill: /home/user/.agents/skills/agent-reach
[dry-run] Would remove mcporter entry: exa
[dry-run] Would remove mcporter entry: xiaohongshu
Dry run complete. No changes were made.
Run without --dry-run to actually remove the above.

Summary

• Configuration data: The ~/.agent-reach directory is deleted unless --keep-config is specified.
• Skill directories: Platform-specific paths under ~/.openclaw, ~/.claude, and ~/.agents are removed or unlinked.
• MCP entries: exa and xiaohongshu entries are purged from mcporter configuration.
• Package binaries: The Python package and auxiliary tools (mcporter, twitter-cli, undici) require manual uninstallation via pip, npm, or pipx.
• Safety feature: Use --dry-run to preview all targeted files before actual deletion.

Frequently Asked Questions

Does agent-reach uninstall remove the Python package itself?

No, the command only removes local data directories and configuration files. The Agent Reach Python package remains installed in your environment. You must manually run pip uninstall agent-reach to remove the package binaries and entry points.

What happens if I use the --keep-config flag?

When you supply the --keep-config flag, the command preserves the ~/.agent-reach directory and its contents (including config.yaml with stored credentials) while still removing skill directories and MCP entries. This is useful when you plan to reinstall Agent Reach later without reconfiguring API keys.

Are symlinks to skill directories handled differently?

Yes, according to the source code in agent_reach/cli.py, if a skill directory is a symlink, the command unlinks it rather than recursively deleting the directory contents. This prevents accidental deletion of files that might be shared across multiple installations or managed by other package managers.

How can I verify what will be deleted before running the uninstall command?

Run agent-reach uninstall --dry-run to simulate the process. This displays every file, directory, and configuration entry that would be removed during a real uninstallation, allowing you to confirm the scope of changes before committing to them.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}