remote-control-compatibility

Diagnoses and toggles model-gateway remote-control compatibility via hosts-file edits on Windows, macOS, Linux.

15|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill remote-control-compatibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remote-control-compatibility
Source: https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/model-gateway/skills/remote-control-compatibility
Command: npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill remote-control-compatibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when Claude Code's /remote-control command is unavailable because model-gateway is managing the connection and the required hosts-file mapping is missing or needs repair.

Core Features & Use Cases

  • Compatibility Diagnosis: Checks the current model-gateway state before making any changes so you can see why remote control is blocked.
  • Controlled Enable/Disable Flow: Adds or removes only the marker-delimited hosts-file block needed for /remote-control compatibility.
  • Safety Guardrails: Requires direct user confirmation before any elevated hosts-file write and avoids touching unrelated host entries.
  • Recovery Handling: Stops cleanly on write failures, port conflicts, malformed blocks, or failed gateway recovery and reports the next safe step.

Quick Start

Ask the assistant to diagnose model-gateway remote-control compatibility and, if you approve the change, enable it so /remote-control becomes available after restarting Claude Code.

Frequently Asked Questions about remote-control-compatibility

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

FAQPage Schema
Why does Claude Code /remote-control not work when model-gateway is managing the connection?

The /remote-control command becomes unavailable when model-gateway manages the connection and the required hosts-file mapping is missing. Diagnosing compatibility checks the current gateway state to identify why remote control is blocked.

How do I enable remote-control compatibility for model-gateway on Windows, macOS, or Linux?

To enable remote-control compatibility, the assistant diagnoses the model-gateway state, requests user confirmation for elevated hosts-file writes, and applies marker-delimited loopback remapping blocks to restore /remote-control access across Windows, macOS, and Linux.

Can I disable model-gateway remote-control compatibility without affecting unrelated hosts file entries?

Yes, you can disable model-gateway remote-control compatibility safely. The controlled enable/disable flow removes only the marker-delimited hosts-file block needed for /remote-control, avoiding touching unrelated host entries.

What happens if hosts-file write failures or port conflicts occur during gateway recovery?

During gateway recovery, the process stops cleanly on hosts-file write failures, port conflicts, or malformed blocks. It reports the specific failure and indicates the next safe step for troubleshooting remote-control compatibility.

Do I need privileged access to repair model-gateway hosts-file mapping for /remote-control?

Yes, privileged file writes are required. Before applying any elevated hosts-file edits for loopback remapping, the system requires direct user confirmation to ensure safe, marker-delimited changes for gateway recovery.