How do I use the session ID in my custom skills?

Simply use the ${CLAUDE_SESSION_ID} placeholder in your skill or command markdown files; Claude Code will automatically substitute it with the actual UUID when the skill loads.

Can I access the session ID from a bash script?

Yes, bash hooks receive the session ID via stdin JSON. You can extract it using tools like jq by reading the '.session_id' field from the input.

What is the primary purpose of the Session ID in Claude Code?

The Session ID uniquely identifies a conversation, enabling the system to track history files, coordinate hook scripts, and manage task ownership across different instances.

Where are the session history files stored?

Session history is typically stored in the project workspace configuration directory, following the naming convention of {session-id}.jsonl.

Session ID Access

Name: Session ID Access
Author: cowwoc

bycowwoc

•

Herramientas para Desarrolladores

Enables automatic identification and tracking of unique Claude Code conversation sessions through variable substitution.

Acerca de

The Get Session ID skill provides a standardized way to reference and utilize unique session identifiers (UUID v4) within the Claude Code environment. By automatically substituting the ${CLAUDE_SESSION_ID} placeholder in skill templates and commands, this utility allows developers to programmatically access conversation history files, coordinate bash hooks via stdin JSON, and maintain session-specific TODO lists. This is essential for building complex agents that require persistent context or multi-instance task coordination.

Características Principales

Integration with Bash hooks via stdin JSON extraction
Unique UUID v4 generation for every independent conversation session
Direct path mapping to session-specific history and log files
Automatic substitution of ${CLAUDE_SESSION_ID} in markdown templates
2 GitHub stars
Enhanced user visibility via SessionStart context injection

Casos de Uso

Coordinating task ownership and state across multiple concurrent AI instances
Developing custom bash scripts that require session-persistent data storage
Programmatically accessing and analyzing local session history JSONL files

Acerca de

Características Principales

Integration with Bash hooks via stdin JSON extraction
Unique UUID v4 generation for every independent conversation session
Direct path mapping to session-specific history and log files
Automatic substitution of ${CLAUDE_SESSION_ID} in markdown templates
2 GitHub stars
Enhanced user visibility via SessionStart context injection

Casos de Uso

Coordinating task ownership and state across multiple concurrent AI instances
Developing custom bash scripts that require session-persistent data storage
Programmatically accessing and analyzing local session history JSONL files