Claude Code Session Recording And Serialization

via “jsonl session log parsing with per-turn reconstruction”

The missing DevTools for Claude Code — inspect session logs, tool calls, token usage, subagents, and context window in a visual UI. Free, open source.

Unique: Implements streaming JSONL parsing with multi-level caching (file-level and turn-level) to reconstruct per-turn context windows without requiring full session file loads, combined with path encoding scheme (Project IDs) to handle complex project hierarchies and remote SSH paths uniformly

vs others: Provides deeper execution visibility than Claude Code's native --verbose output by structuring raw logs into queryable turn-by-turn traces, while avoiding the terminal flooding and raw JSON noise of verbose mode

I got tired of sharing AI demos with terminal screenshots or screen recordings.Claude Code already stores full session transcripts locally as JSONL files. Those logs contain everything: prompts, tool calls, thinking blocks, and timestamps.I built a small CLI tool that converts those logs into an int

Unique: Specifically targets Claude Code IDE sessions rather than generic terminal/editor recording, capturing LLM-specific interactions (prompt-response pairs, code suggestions, edits) as first-class events in the replay format

vs others: More semantically rich than generic screen recording tools because it understands Claude Code's domain-specific events (LLM turns, file diffs, terminal commands) rather than pixel-level replay

via “claude api session conversation capture and persistence”

We built rudel.ai after realizing we had no visibility into our own Claude Code sessions. We were using it daily but had no idea which sessions were efficient, why some got abandoned, or whether we were actually improving over time.So we built an analytics layer for it. After connecting our own sess

Unique: Implements transparent session capture via SDK middleware that requires zero changes to existing Claude API client code, automatically logging all conversation state without application-level instrumentation

vs others: Captures full Claude conversation history with metadata in a single integrated tool, whereas manual logging or generic API proxies require custom instrumentation per application

via “session management, logging, and observability”

A tremendous feat of documentation, this guide covers Claude Code from beginner to power user, with production-ready templates for Claude Code features, guides on agentic workflows, and a lot of great learning materials, including quizzes and a handy "cheatsheet". Whether it's the "ultimate" guide t

Unique: Provides the first comprehensive session management and observability guide for Claude Code, including diagnostic patterns and health check frameworks that enable debugging complex agentic workflows

vs others: Offers Claude Code-specific observability patterns that competitors don't document, enabling teams to monitor and debug AI-assisted development workflows at scale

via “claude session file extraction and parsing”

Claude Code deleted my research and plan markdown files and informed me: “I accidentally rm -rf'd real directories in my Obsidian vault through a symlink it didn't realize was there: I made a mistake. “Unfortunately the backup of my documentation accidentally hadn’t run for a month. So I b

Unique: Directly targets Claude's local session storage format to recover artifacts that exist nowhere else — most recovery tools focus on cloud backups or trash bins, but this exploits the fact that Claude caches full conversation state locally including all generated files

vs others: Recovers Claude-specific artifacts that generic file recovery tools cannot access because they're embedded in proprietary session serialization rather than stored as independent files

via “claude-code-integration-with-streaming-output-rendering”

(Crystal is now Nimbalyst) Run multiple Codex and Claude Code AI sessions in parallel git worktrees. Test, compare approaches & manage AI-assisted development workflows in one desktop app.

Unique: Wraps Claude Code CLI as a managed subprocess with PTY-based streaming output capture, enabling real-time response rendering without buffering. Integrates Claude's native capabilities directly into Crystal's multi-session architecture rather than using Claude API directly, preserving Claude Code's full feature set including file operations and terminal access.

vs others: Provides tighter integration with Claude Code's native CLI than REST API wrappers, enabling access to Claude Code's full capabilities (file system operations, terminal execution) while maintaining streaming output and multi-session isolation.

via “context serialization for persistence”

Show HN: Claude Cognitive – Working memory for Claude Code

Unique: Utilizes JSON serialization for easy context storage and retrieval, contrasting with alternatives that may use less flexible formats.

vs others: More flexible and easier to integrate with various storage solutions compared to binary serialization methods.

via “session sharing with unique link”

Hi HN,We use Claude Code a lot, and after a long session there isn't a simple way to share exactly what happened with someone else. Prompts, responses, file edits, and tool calls all stay inside the terminal.We built Claudebin to make that easier.It's a plugin that lets you export the curr

Unique: Utilizes a centralized session management system that allows real-time updates and state retrieval via unique links, which is not commonly found in similar tools.

vs others: More user-friendly than traditional version control systems, as it eliminates the need for complex setups and provides instant access to shared sessions.