I built a global session browser for Codex CLI because I got tired of losing the thread

When you use Codex CLI across multiple projects, sessions start to pile up. At first, that is fine. Then a few days later you remember that one useful conversation exists somewhere, but you do not remember which repo you were in, what you named the session, or whether you even renamed it at all. That friction is small, but it compounds. I built Codex Session Hub to remove that problem. It is an open source CLI tool that gives Codex a global session browser, so instead of jumping between folders and trying to manually recover context, I can open one command, search every session on my machine, preview the context, and resume the right one immediately. The project is a PowerShell 7 tool built around fzf, and the current release already supports browsing, resuming, renaming, resetting titles, deleting sessions, previewing context, and a one-line installer. The problem was not Codex itself Codex already lets you resume sessions. The annoying part was everything around that. The real issue