claude-remote:debug

Diagnose failing Claude remote sessions by analyzing setup logs and repository configuration.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/fabn/claude-plugins --skill claude-remote-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-remote:debug
Source: https://github.com/fabn/claude-plugins/tree/main/plugins/claude-remote/skills/debug
Command: npx skills add https://github.com/fabn/claude-plugins --skill claude-remote-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps users who cannot get a Claude Code cloud session running after executing the remote setup, by pinpointing why the setup scripts or logs failed.

Core Features & Use Cases

  • Log‑first diagnostics: Reads /tmp/claude-user-setup.log and matches patterns against a built‑in troubleshooting reference.
  • Repo‑state audit: Checks the presence, executability, and correctness of .claude/scripts/* and .claude/settings.json.
  • Canonical drift detection: Compares the pasted web‑UI setup script with the plugin’s canonical template.
  • Optional environment dump: Generates a full environment snapshot when simpler checks don’t resolve the issue.

Quick Start

Ask the skill to debug the current remote session and receive a concise remediation plan.

Frequently Asked Questions about claude-remote:debug

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

FAQPage Schema
Why is my Claude Code cloud session failing after running the remote setup script?

Claude remote session setup failures are typically caused by script execution errors or misconfigured repository settings. The diagnostic process analyzes the /tmp/claude-user-setup.log file to match error patterns against known issues and generate a targeted remediation plan.

How do I debug Claude remote setup errors using log files?

Debug Claude remote setup errors by reading the /tmp/claude-user-setup.log file and matching identified patterns against a built-in troubleshooting reference. This log-first diagnostic approach pinpoints specific script failures and suggests applicable fixes for the cloud environment.

What does a repository configuration audit check for in Claude Code remote environments?

A repository configuration audit checks the presence, executability, and correctness of .claude/scripts/* files and .claude/settings.json. It verifies that the repository state matches the expected structure required for Claude Code cloud sessions to operate correctly.

How do I detect configuration drift in my Claude Code web-UI setup script?

Detect configuration drift by comparing your pasted web-UI setup script against the plugin's canonical template. This comparison identifies deviations from the standard configuration that may cause remote session initialization failures.

What should I do when standard log checks do not resolve Claude remote session issues?

When standard log checks fail to resolve Claude remote session issues, generate a full environment dump. This optional snapshot captures comprehensive environment state data to diagnose complex setup failures that simpler checks cannot identify.

Can I use this troubleshooting process for local Claude Code installations?

This troubleshooting process is designed for cloud-based Claude Code environments where users run remote setup scripts. It specifically requires access to /tmp/claude-user-setup.log and .claude configuration files typical of remote sessions.