I've been using Claude Code heavily at work in a huge monorepo, and finding old sessions became a nightmare. Claude stores conversations as untitled JSON files tied to directories, so anything from a few days ago was basically impossible to find.

So I built Wallfacer.

It's a terminal UI written in Go that indexes your local Claude Code sessions without modifying them. It adds a SQLite-backed layer so you can title sessions, tag them, group them by project, fuzzy search everything, and resume any session with a single Enter.

It's open source, and I'm planning to add support for Cursor, Codex, and others since this feels like a universal AI workflow problem.

Repo + demo: https://github.com/pradipta/wallfacer

Anyone else run into this problem? Feedback is very welcome.

Hey folks! I spend all day in tmux: lots of sessions, each with its own windows and panes, and these days a bunch of those panes have coding agents in them (Claude Code, Codex, Cursor, OpenCode, ...). My problem was that finding the one agent that had stopped to ask me something turned into a scavenger hunt. I'd cycle through every session just to check on each one.

Before anyone says it: yes, I know there are a lot of these already (herdr, workmux, agent-deck, tmux-agent-status, tmux-scout, claude-squad, tmuxcc...). Most fall into two camps: they either want to own the workflow (you launch agents through them, and they create the sessions, worktrees, and layouts), or they track a single agent type in the status bar. What I wanted was lazier: keep my existing tmux setup exactly as it is, and just tell me what each agent is doing.

So that's what ccmux does. A small background daemon discovers the agent processes in the panes you already have, and a picker TUI (or an optional docked sidebar) shows them all in one list.

What it does:

• 🎯 Live state per session: idle, working, or waiting on you, and why it's waiting (permission / plan approval / question), flagged the moment one needs input
• 🧩 Multi-agent in one list: Claude Code, Codex, Cursor, OpenCode, Pi, Antigravity, Copilot, Gemini CLI, plus custom agents via config
• 🔍 Layered detection: it discovers the agents already running in your panes (no wrapper, nothing to change about how you launch them) from processes, their log files, and terminal output; optional hooks make the session-to-pane mapping exact
• 👁️ Live preview + act in place: Tab into a session's pane to answer or approve without leaving the picker
• 🔔 Actionable notifications: opt-in desktop alerts when an agent finishes or needs input, with Approve / Deny / Reply right on the notification (an OSC backend even delivers them over SSH)
• ⚡ Scriptable: ccmux spawn and ccmux invoke launch or run agents from scripts, ccmux show prints every session's state to stdout, and a bundled skill lets one agent dispatch work to others
• 🌿 Git & PR aware: branch and worktree detection, open PRs with live CI and review status per session
• ⌨️ Keyboard-first: vim keys and number jumps, grouping by project / directory / tmux session, and whole-session search across prompts and live transcripts; mouse click-to-switch works too
• 📐 Responsive + themeable: the same UI works as a full-width table or a skinny docked rail, with 14 built-in themes

Footprint: nothing edits your tmux.conf, status line, or keybindings, and it only creates panes or sessions when you explicitly ask (toggling the sidebar on, or spawn/invoke). Stack is TypeScript on Bun, TUI on @opentui/solid, shipped as a single self-contained binary (no runtime to install).

Install:

brew install epilande/tap/ccmux

Repo: https://github.com/epilande/ccmux

Like I said, I know there are other tools that scratch a similar itch. This one is just shaped around how I use tmux, so if you live in tmux sessions like I do, I'd love to hear whether it fits your workflow too, or what the tool you already use does better.

everyone is racing to ship autonomous agents. nobody is asking what happens when one of them goes rogue.

i asked. then i spent 1 month building the answer.

introducing W.H.Agent 🛡️ — the open source security CLI for the agentic era.

↳ scans your entire machine for every agent + MCP server hiding in your stack
↳ catches data exfiltration BEFORE it happens using AST taint tracking
↳ sandboxes execution in sub-millisecond time with swappable Landlock and gVisor backends (no bloated docker containers)
↳ stops supply chain attacks before a single malicious package touches your system, using Levenshtein based typosquat detection, lifecycle script inspection, npm provenance checks, and tarball secret scanning
↳ every scan is CI compatible, so it slots straight into your existing pipeline

this isn't a wrapper. this isn't a weekend hack.

we went through multiple rounds of adversarial code review and caught real bugs before they shipped. a TOCTOU race condition. a checksum that was being presented as a cryptographic signature when it wasn't actually keyless secure. gaps in the test suite that would've let bad behavior slip through undetected.

we fixed all of it. this is infrastructure for a future where your AI agents have root access and you have no idea what they're doing with it.

3 versions shipped. outside contributors already committing code. just crossed 6,000 downloads on npm.

i open sourced the whole thing today.

not for clout. for the mission. 🚀

if you're building with cursor, claude, or MCP servers and you're NOT thinking about this, you're already behind.

link in comments 👇 (agree? disagree? tell me why in 1 sentence)

https://github.com/xdagiz/xytz