fix-stuck-session

Diagnose and clear orphaned Cowork session files or processes after user confirmation.

8|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill fix-stuck-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-stuck-session
Source: https://github.com/MSApps-Mobile/claude-plugins/tree/main/plugins/cowork-session-fixer/skills/fix-stuck-session
Command: npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill fix-stuck-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Resolves the "RPC error: process with name already running" failure that prevents Claude Cowork sessions from loading or accepting follow-up messages by diagnosing orphaned session state files and orphaned processes.

Core Features & Use Cases

  • Tiered diagnostic workflow: Identify stuck sessions, cross-reference with session listings, and map errors to root causes.
  • Safe remediation options: Propose and perform non-destructive fixes first (archive session JSON), escalate to graceful process termination, and only use full cache resets as a last resort.
  • Supervised operations: Always require explicit user confirmation before any destructive action and provide a structured report of actions taken.
  • Cross-platform support: Guidance and commands for macOS, Windows, and Linux environments to recover local Claude Cowork sessions.
  • Use case: Recover an orphaned Cowork session named in an RPC error so users can resume their task without losing other active sessions.

Quick Start

Run the fix-stuck-session skill to scan local Cowork sessions, present findings, and, after your confirmation, archive the stuck session or terminate the orphaned process to restore normal operation.

Frequently Asked Questions about fix-stuck-session

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

FAQPage Schema
How do I fix the RPC error process with name already running in Claude Cowork?

A Cowork session becomes stuck and triggers an RPC error when orphaned session JSON files or background processes conflict with the active session name. This blocks follow-up messages and prevents the local Claude session from loading properly on your machine.

How do I recover an orphaned Cowork session without losing other active sessions?

The skill applies to local Claude Cowork sessions across Windows, macOS, and Linux. It provides cross-platform commands and guidance to diagnose and clear orphaned processes wherever your desktop sessions are running.

What steps are involved in resolving a blocked Cowork desktop session?

Resolving a blocked Cowork session involves scanning local sessions, presenting diagnostic findings, and after explicit confirmation, archiving the stuck session JSON or terminating the orphaned process. It verifies success by listing sessions afterward.

Is it safe to terminate orphaned Cowork processes to clear an RPC error?

You should avoid full cache resets for Cowork RPC errors unless graceful process termination fails. The skill uses cache resets only as a last resort, prioritizing session JSON archiving and graceful process termination to preserve session state.