u/Least-Post9099

I kept hitting the same wall. Every time I started a new LLM project, I'd spend the first week writing the same infrastructure: vector store, embedding pipeline, retrieval logic, deduplication so the same fact doesn't get stored fifteen times. The actual product would sit there waiting while I plumbed this together again.

After the fourth time I just stopped and built it once as a standalone thing.

It's called Torqon. The idea is simple:

POST /memory/store    # save something worth remembering
GET  /memory/retrieve # pull relevant context before your model call

Works with Claude, GPT, Llama, anything. You stop feeding full conversation histories into prompts and just inject what's actually relevant for the current message. My own context sizes dropped a lot once I started using it, and the responses got noticeably better because the model wasn't wading through noise.

Free tier is live at torqon.dev, no card needed. I'm still early and genuinely trying to figure out what to build next, so if you're working on anything with agents or persistent sessions, I'd really love to hear what memory-related stuff has been annoying you most.

What's the dumbest thing you've had to build from scratch just to get LLM memory working?

You know the loop where you ask Claude to build something, the prompt's missing stuff it actually needs, and it either dumps five clarifying questions on you or just guesses and you find out two messages later it picked the wrong thing.

​

Got annoyed enough at this last week to actually build something for it. The skill figures out what's missing, but only the stuff that would change the output, asks about that specifically, and if you just want to say "use your best judgment" it goes ahead but tells you exactly what it assumed. So fixing a bad guess is one line instead of starting the whole prompt over.

​

Someone's going to bring up grill-me in the comments so I'll just say it now, yeah I know it exists. That one interviews you on everything before it starts, which is great when you want to think through a plan. This is for when you don't want that, you want one shot and you still want to see what got invented.

​

Quick example. Prompt was "build me a website for my dental practice," I said just guess, got this at the top of the response:

Assumptions made (no info given, so I picked defaults):

Services: general + cosmetic dentistry, most common combo for a small practice

Tone: warm and reassuring, typical for patient facing sites

Colors: blue/white, common trust signal in healthcare

Swap any of these out and it redoes just that part.

Repo's here if you want to poke at it: github.com/ahirmaan/show-your-work. MIT, two examples in the repo. It's a v1 I built solo, so if you throw something weird at it and it asks the wrong question or misses something obvious, open an issue, genuinely want to know where it breaks.