cc-mid-session-registry-staleness

Diagnose Claude Code registry staleness blocking mid-session agent and workflow updates.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill cc-mid-session-registry-staleness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-mid-session-registry-staleness
Source: https://github.com/cajias/claude-skills/tree/main/plugins/cc-authoring/skills/cc-mid-session-registry-staleness
Command: npx skills add https://github.com/cajias/claude-skills --skill cc-mid-session-registry-staleness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fixes two Claude Code caching traps that make newly created agents and edited workflows appear broken during the same session.

Core Features & Use Cases

  • Mid-session agent visibility: Explains why .claude/agents files created after session start cannot be resolved by agentType or subagent_type until restart.
  • Stale workflow execution: Shows how Workflow name lookup can keep running an older snapshot even after the underlying .claude/workflows file changes.
  • Reliable workaround patterns: Recommends scriptPath-based invocation for live file loading and a registry-independent fallback persona for workflows that need to work immediately.

Quick Start

Use this Skill to diagnose a Claude Code workflow that is failing instantly because its agent or saved workflow was loaded from a stale session registry.

Frequently Asked Questions about cc-mid-session-registry-staleness

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

FAQPage Schema
Why does Claude Code fail to resolve newly created agents mid-session?

Claude Code fails to resolve newly created agents mid-session because the active session registry caches agent types, preventing recognition of new .claude/agents files until a restart.

How do I fix stale workflow execution in Claude Code without restarting?

To fix stale workflow execution without restarting, use scriptPath-based invocation to load live file changes directly, bypassing the cached workflow name lookup in your Claude Code session.

What causes Claude Code workflow registry staleness during automation?

Claude Code workflow registry staleness occurs during automation when cached name resolution preserves outdated workflow snapshots, ignoring live updates to .claude/workflows files until session restart.

Can I invoke a workflow by file path to bypass registry staleness in Claude Code?

Yes, you can invoke a workflow by file path using scriptPath-based invocation to bypass registry staleness, ensuring the live file version loads without needing a Claude Code session restart.

How do I set up a registry-independent fallback for Claude Code workflows?

Set up a registry-independent fallback by defining a persona that loads directly via path-based invocation, allowing workflows to execute immediately despite mid-session agent registration failures.