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.<p>Just out of curiosity, why did you pick that name? Is there anything wallfacey about this project I'm not getting?
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.<p>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.
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?<p>That's not a rant against Wallfacer. It's just an observation about the state of the open-source world in 2026...
In a world where code is cheap, code no longer equals effort. These days, I see consistency, attention to detail, long term support, and community engagement as the signals to read. Not to say this project will never become that, as it may! However until I see those signals as a clear sign of momentum, it's just noise.
Yes, absolutely.<p>I'll never vibe-code PostgreSQL. I don't want to maintain my own Kubernetes codebase. I happily pay for GitLab Enterprise and Authentik Enterprise.<p>That said, these small end-user console apps are just noise.<p>It's so cheap to build something that fits your exact use case that almost everyone does it instead of contributing to an existing project or reading through their AI generated documentation...<p>And posting it on Hacker News feels like the software developer equivalent of an influencer posting a picture of their lunch.
This is exactly what I did. I create tooling to make it easier for me to manage multiple multi-project swarms across multiple clis (claude, codex, opencode), with queuing, and team sharing.<p>It was.. surprisingly a little bit under a day's work. It's now heavily tied into our way of working and thinking. This is the upside of the current world.<p>What used to be time spent in personal, throwaway(ish) shell scripting has now become the same, but for more full fledged tooling. It doesn't need to be consumable by others - but it does need to make my/our life/ves better