██╗ ██╗█████╗ ██╗ ██╗ ███████╗█████╗ ██████╗███████╗██████╗ ██║ ██║██╔══██╗██║ ██║ ██╔════╝██╔══██╗██╔════╝██╔════╝██╔══██╗ ██║ █╗ ██║███████║██║ ██║ █████╗ ███████║██║ █████╗ ██████╔╝ ██║███╗██║██╔══██║██║ ██║ ██╔══╝ ██╔══██║██║ ██╔══╝ ██╔══██╗ ╚███╔███╔╝██║ ██║███████╗███████╗██║ ██║ ██║╚██████╗███████╗██║ ██║ ╚══╝╚══╝ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝ ╚═╝ ╚═╝ ╚═════╝╚══════╝╚═╝ ╚═╝ A terminal session manager for Claude Code , Cursor CLI , Kiro CLI and Codex — see every AI coding session you've ever started, then name, tag, group, search, resume, or delete them, from a full-screen browser or straight from the command line. Why Claude Code stores every conversation as an untitled JSONL file under ~/.claude/projects/ , keyed by whatever directory you were in. Kiro CLI does much the same in a single flat ~/.kiro/sessions/cli/ folder, Cursor CLI buries each chat in a hash-named directory under ~/.cursor/chats/ , and Codex files its rollouts by date under ~/.codex/sessions/ .…