I work in a massive monorepo with a bunch of different services. Over the last month, I realized I was starting Claude Code sessions everywhere. I would hit a weird issue, remember I had already solved it with the agent a few days ago, and then realize I had no way to easily find that specific session. CC stores these as JSON files, keyed by the directory you happened to be in at the time.

I built Wallfacer because I needed a way to search and resume these sessions without messing with the source of truth. It operates as a strictly read only overlay. It just reads the local files, extracts the working directory and first prompt, and lets you manage the metadata in a local SQLite database.

The name is pretty ominous if you've read the Three Body Problem series. I don't want my agents planning against me in secrecy.

Just out of curiosity, why did you pick that name? Is there anything wallfacey about this project I'm not getting?

you can name Claude sessions using /rename. also tmux is your friend.

I see the need for such a tool. I just ask myself: why should I use a brand-new vibe-coded tool if I can just vibe-code my own? One that's fine-tuned exactly for my use case?

That's not a rant against Wallfacer. It's just an observation about the state of the open-source world in 2026...