warmup-sid-separator

Name: warmup-sid-separator
Availability: InStock
Author: tankygranny05

Distinguish ephemeral warmup SIDs from persistent session SIDs in sse_lines.jsonl.

2|Updated Jan 30, 2026

Search Tags:#debugging #logging #claude #session #warmup #sid #pid mapping

Ready to run

npx skills add https://github.com/tankygranny05/agent-box --skill warmup-sid-separator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: warmup-sid-separator
Source: https://github.com/tankygranny05/agent-box/tree/main/agent-box/vendor/agent-box-v1/apps/agent-hq-ui/.claude/skills/warmup-sid-separator
Command: npx skills add https://github.com/tankygranny05/agent-box --skill warmup-sid-separator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps distinguish between temporary SIDs generated during Claude Code's warmup phase and the actual session SIDs used for real interactions, preventing confusion in logs and ensuring accurate process-to-session mapping.

Core Features & Use Cases

SID Classification: Differentiates claude.warmup SIDs from claude.session_start or claude.user_prompt SIDs.
Accurate PID-to-SID Mapping: Enables reliable attribution of sessions to their corresponding process IDs (PIDs).
Debugging Resume Issues: Helps identify if a "resume created a new SID" report is a true fork or just a warmup artifact.
Use Case: When debugging why a resumed Claude session appears to have a new ID, this skill can confirm if the initial SID was just a warmup SID and the subsequent one is the correct, resumed session SID.

Quick Start

Run the verification script to see how warmup SIDs are separated from real session SIDs.

Frequently Asked Questions about warmup-sid-separator

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

FAQPage Schema

What is a Claude warmup SID and how does it differ from a real session SID?▼

Distinguishing warmup SIDs from real session SIDs prevents confusion in `sse_lines.jsonl` logs and ensures accurate PID-to-SID mapping. It confirms whether a resumed Claude session generated a true fork or just a temporary warmup artifact.

How do I separate warmup SIDs from real session SIDs in Claude logs?▼

You can separate warmup SIDs from real session SIDs by running the bundled verification scripts to inspect `sse_lines.jsonl` files, classifying `claude.warmup` events separately from `claude.session_start` events for accurate log analysis.

Why does a resumed Claude session appear to have a new SID?▼

You need to parse `sse_lines.jsonl` log files containing `claude.warmup`, `claude.session_start`, or `claude.user_prompt` event records to classify SIDs and map them to their corresponding process IDs.

Can I use these scripts to verify PID-to-SID mapping for agent monitoring?▼

Yes, you can use the bundled scripts to inspect log files and verify PID-to-SID mapping. This ensures reliable attribution of process IDs to persistent session SIDs during agent monitoring and debugging operations.

What is the best way to debug Claude resume operations and session forks?▼

The best way to debug Claude resume operations is to classify SIDs using verification scripts to filter out `claude.warmup` artifacts, ensuring accurate process-to-session mapping and identifying true session forks versus temporary warmup identifiers.