I built a global session browser for Codex CLI because I got tired of losing the thread
Source: Dev.to
⚠️ Collection Error: Content refinement error: Error: 429 429 Too Many Requests: you (bkperio) have reached your weekly usage limit, upgrade for higher limits: https://ollama.com/upgrade
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. Codex already lets you resume sessions. The annoying part was everything around that. The real issue was session sprawl: sessions spread across different projects weak memory of where a conversation happened no fast global view across all work too much folder switching for something that should be instant That is the gap Codex Session Hub tries to close. The tool exists specifically to browse Codex sessions across projects from one command, resume directly into the correct project directory, rename sessions with persistent aliases, bulk delete sessions, and preview context before resuming. It is intended to work on Windows, macOS, and Linux as long as PowerShell 7 is available. Open to suggestion and contribution to expand the compatibility. The core idea is simple: treat all Codex sessions on your machine like a searchable workspace instead of isolated per-project artifacts. With csx, I wanted the flow to feel closer to a fuzzy finder for thought history: open one browser search by folder, project, session number, or title inspect enough context to avoid guessing jump back into the right place The current command set includes: csx csx browse csx browse desktop csx rename —name “My friendly alias” csx reset csx delete csx doctor
The interactive browser also supports keyboard actions like resume on Enter, multi-select with Tab, delete on Ctrl-D, rename on Ctrl-E, and reset on Ctrl-R. Search supports text queries, numeric session prefixes, and title filters such as title: or t:. I did not want a heavy wrapper around Codex. I wanted a tool that stays close to the terminal, does one job clearly, and fits into an existing CLI workflow. That is why the stack is straightforward: PowerShell 7 for portability and shell integration fzf for fast selection and interaction a user-local install flow so setup is minimal The repo documents PowerShell 7, Codex CLI in PATH, and fzf in PATH as the main requirements. It also includes a self-bootstrapping install.ps1, a self-contained uninstall.ps1, and a doctor command to verify setup. If you already have PowerShell 7, Codex CLI, and fzf, the recommended install is: irm https://raw.githubusercontent.com/vinzify/Codex-Session-Hub/master/install.ps1 | iex . $PROFILE csx doctor
The README lists default install locations as %LOCALAPPDATA%\CodexSessionHub on Windows and ~/.local/share/codex-session-hub on macOS and Linux. It also documents uninstall via a matching one-line script. The first tagged release is v0.1.0, published on March 20, 2026 on GitHub. The changelog describes it as the initial modular fzf-based release and lists global session browsing grouped by project, browser actions for resume/rename/reset/delete, direct CLI commands, preview panes, install and uninstall scripts, and CI updates. For a first public version, that is enough surface area to be useful without pretending the project is more mature than it is. The project is still early. What matters now is whether it actually reduces recovery time when switching between projects and whether the browser model is the right abstraction for how people use Codex day to day. That means the next useful feedback is not vague praise. It is concrete friction: where session discovery still feels slow what metadata is missing in preview whether aliases are enough or tagging is needed where the install flow breaks on real machines whether PowerShell is the right default layer long term Because this is the kind of tool that gets better from real usage patterns. Everyone accumulates terminal scars a little differently. One person wants cleaner recovery. Another wants better naming. Someone else wants bulk actions because they treat sessions as disposable. Open source is the easiest way to let the tool meet actual behavior instead of my assumptions about behavior. If you use Codex CLI heavily and your session history is turning into junk drawer state, try it and tell me where it breaks: GitHub repo: https://github.com/vinzify/Codex-Session-Hub If the tool saves you time, good. If it reveals that the current model is wrong, that is useful too. That is the point.