session-atlas

Maps AI coding-agent sessions to their git worktrees via local file analysis.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/ilamanov/skills --skill session-atlas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-atlas
Source: https://github.com/ilamanov/skills/tree/main/skills/session-atlas
Command: npx skills add https://github.com/ilamanov/skills --skill session-atlas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @hono/node-server, hono, htm, preact, and includes scripts (resource) and assets (resource) and ui (resource) components.

What problem does it solve?

This Skill maps Codex and Claude Code sessions to their corresponding git worktrees, providing an interactive UI for visualizing and managing past AI coding-agent conversations and their associated worktrees.

Core Features & Use Cases

  • Session Mapping: Maps sessions to their respective git worktrees and provides session summaries.
  • UI for Management: Offers an interactive UI to view, search, audit, and clean up past AI coding-agent conversations and worktrees.
  • Use Case: After running a series of Codex and Claude Code sessions in different worktrees, use the Skill to visualize all sessions and their worktree context, identify which worktree contains conversations of interest, and archive or delete outdated sessions.

Quick Start

Launch the Session Atlas UI using the following command:

npm --prefix <this-skill>/app install   # first run only
npm --prefix <this-skill>/app start

The UI will open to a local port with a project picker to select the desired project.

Frequently Asked Questions about session-atlas

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

FAQPage Schema
How do I map AI coding-agent sessions to their git worktrees?

You can map AI coding-agent sessions to git worktrees using local file system analysis that reads your .codex and .claude directories alongside git metadata to link conversations to their worktree context.

What is the best way to visualize past Claude Code and Codex sessions across different worktrees?

Visualizing past Claude Code and Codex sessions is done through an interactive UI that maps sessions to their respective git worktrees, allowing you to view, search, audit, and clean up past conversations.

Do I need Node.js to visualize and manage Claude Code session worktrees?

Yes, you need Node.js and npm installed to run the UI hosting and project discovery packages required for mapping sessions to their git worktrees and visualizing the results.

Can I archive or delete outdated AI coding-agent conversations using a session mapping UI?

Yes, the session mapping UI allows you to identify which worktree contains conversations of interest and directly archive or delete outdated AI coding-agent sessions from the local interface.

How does session mapping handle git worktree discovery for post-mortem analysis?

Session mapping handles git worktree discovery by analyzing local file system paths and git metadata to accurately associate historical AI coding-agent conversations with their originating worktree for post-mortem analysis.

What are the limitations of using local file system analysis for session mapping?

The session mapping relies strictly on local file system analysis of the .codex and .claude directories and git metadata, meaning it cannot map sessions for worktrees or configurations that are not present on the local machine.