██╗ ██╗█████╗ ██╗ ██╗ ███████╗█████╗ ██████╗███████╗██████╗ ██║ ██║██╔══██╗██║ ██║ ██╔════╝██╔══██╗██╔════╝██╔════╝██╔══██╗ ██║ █╗ ██║███████║██║ ██║ █████╗ ███████║██║ █████╗ ██████╔╝ ██║███╗██║██╔══██║██║ ██║ ██╔══╝ ██╔══██║██║ ██╔══╝ ██╔══██╗ ╚███╔███╔╝██║ ██║███████╗███████╗██║ ██║ ██║╚██████╗███████╗██║ ██║ ╚══╝╚══╝ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝ ╚═╝ ╚═╝ ╚═════╝╚══════╝╚═╝ ╚═╝
wallfacer
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/ . After a few weeks you have dozens of transcripts, across four agents, that you can't tell apart and no way to find the one you need.
wallfacer indexes them all — read-only, it never touches the agents' files — and keeps your titles, tags, and projects in its own local SQLite database.
Features
One view of everything — every session, from every directory and every agent, sorted by recency
— every session, from every directory and every agent, sorted by recency Organize — rename sessions, tag them, group them into projects
— rename sessions, tag them, group them into projects Search — across titles, first prompts, directories, projects, and tags
... continue reading