pradiptasarma

I have a codebase that is so large that after of couple of weeks this and after working on similar stuff all over the place this becomes impossible, and expensive.

Lol, I understand. I was reading the book and I was at the part where the wallfacer project was announced. I did not want to think too much more :D

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.

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.

Exactly, the following is fine:

  try {
    ...
  } catch (Exception up) {
    ...
    throw up; //hehe
  }

The GodComponent as a name is not.