Show HN: Wallfacer – A terminal session manager for Claude Code, and more

Wallfacer is a terminal session manager for Claude Code, Cursor CLI, Kiro CLI, and Codex that surfaces every AI coding session you have started and lets you name, tag, group, search, resume, or delete them from a full-screen browser or the command line. It was posted as a Show HN on the Hacker News front page.

The problem it targets is how each tool stores sessions without a shared catalog. Claude Code writes every conversation as an untitled JSONL file under ~/.claude/projects/, keyed by the directory you were in. Kiro CLI keeps sessions in a single flat ~/.kiro/sessions/cli/ folder. Cursor CLI puts each chat in a hash-named directory under ~/.cursor/chats/. Codex stores rollouts by date under ~/.codex/sessions/. Wallfacer reads across those layouts so you can treat sessions as first-class objects instead of hunting files by path, hash, or date.

For engineers who run many agent sessions across repos, that local sprawl is the real friction. Without names or tags, an old debugging thread, a failed refactor, or a useful multi-file plan is hard to find and harder to resume. A single place to search, group, and resume sessions cuts the cost of treating the terminal agent as a long-lived work log rather than a one-shot chat.

Competitive context is the growing set of CLI coding agents that each ship their own on-disk format and no cross-tool history UI. Claude Code, Cursor CLI, Kiro CLI, and Codex all solve generation; none of them unify session inventory. Wallfacer sits above those clients as session infrastructure, not as another model frontend.

Practical takeaway: if you already keep work in those four CLIs, inspect how your own ~/.claude/projects/, ~/.kiro/sessions/cli/, ~/.cursor/chats/, and ~/.codex/sessions/ trees look after a few weeks of use, then try Wallfacer against a real backlog of untitled or hash-named sessions. Watch whether resume and delete stay reliable as those local formats change, and whether naming and tagging become part of your daily agent workflow or stay optional metadata.