skills.rest
kevinslin
kevinslinCOMMUNITY
Explore all skills by this author →
Website𝕏@kevins8GitHub

dev.llm-session

Parse Codex session metadata from history JSONL and resume the matching session.

21|Updated Jan 3, 2026
Search Tags:#codex#json#resume#history#scripts#session
One-click install
npx skills add https://github.com/kevinslin/skills --skill dev-llm-session
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev.llm-session
Source: https://github.com/kevinslin/skills/tree/main/active/dev.llm-session
Command: npx skills add https://github.com/kevinslin/skills --skill dev-llm-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Identify Codex session IDs from local history or session files and resume the correct interactive session quickly.

Core Features & Use Cases

  • Look up recent session IDs from ~/.codex/history.jsonl by text query or by last entry.
  • Inspect and extract session IDs from files under ~/.codex/sessions to map to a runnable session.
  • Resume a chosen Codex session with a simple command, even if cwd changed.

Quick Start

Find a matching Codex session ID from history or sessions and resume that session.

Frequently Asked Questions about dev.llm-session

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

FAQPage Schema
How do I resume a Codex session when my working directory has changed?▼

To resume a Codex session, you can look up the session ID from ~/.codex/history.jsonl or ~/.codex/sessions and execute a simple resume command, which maps the ID to the correct directory even if your cwd changed.

How do I find a specific Codex session ID from my local history files?▼

To find a specific Codex session ID, query the ~/.codex/history.jsonl file by text or inspect files under ~/.codex/sessions to extract the correct session metadata for the interactive session you need.

Can I extract session IDs directly from JSONL history and JSON session files?▼

Yes, you can extract session IDs from JSONL history and JSON session files by running included scripts that parse history JSONL and session metadata to derive the correct runnable session ID.

What is the best way to map a Codex session ID to a runnable working directory?▼

The best way to map a Codex session ID to a runnable working directory is to inspect session metadata files under ~/.codex/sessions and parse history JSONL to correctly identify the original working directory context.

Does resuming a Codex session require any external dependencies?▼

No, resuming a Codex session requires no external dependencies, relying solely on included scripts to parse local history JSONL and JSON session metadata to derive and resume the correct session.

Related Skills

Explore More Software Engineering Skills→
danielcopperdanielcopper
3

find-session

Search local Claude Code JSONL transcripts to find and resume past sessions.

Community
Intermediate
iamcxaiamcxa
3

kc-session-resume

Restore developer session context from journal handoffs and project checkpoints.

Community
Advanced
mahmoudimusmahmoudimus
6

memory-stats

Display session counts, knowledge areas, and facts from a persistent memory database.

Community
Basic
hongmaple0820hongmaple0820
9

session-logs

Parse JSONL session logs to extract messages by role with jq.

Community
Intermediate