Yesterday a small drop landed on r/PromptEngineering, and it’s not the usual “I built a wrapper” post. The project is called “LIA”, and it’s a full personal assistant built on LangChain and LangGraph, open sourced end to end. The creator, a Redditor going by u/jeyjey9434, put the whole thing on GitHub with documentation and more than 30 prompts, no guesswork required.
What stands out first is how the project treats itself. Instead of a quick weekend hack with a readme that says “figure it out”, the author built it like an enterprise product. Clean code, structured docs, a clear architecture writeup. One commenter on the thread said exactly that: the docs alone are worth a star, because most open source AI projects skip that part entirely. Scroll through the repo and you’ll see separate pages for setup, prompt design, and the reasoning behind each subsystem, the kind of documentation you’d expect from a team with a technical writer on staff, not a solo builder posting on a Saturday.
Here’s the twist though. LIA isn’t just another chatbot wrapper with a nice UI. It runs its own emotional system, a distinct personality, and an evolving structured memory that changes based on how you actually talk to it. On top of that it keeps a separate reflective memory of your conversations, so it’s not just storing facts, it’s forming its own take on your history together. Say you mention a stressful work deadline three days in a row, LIA doesn’t just log “user has a deadline”, it starts factoring that pattern into how it responds, checking in on it unprompted the next time you talk. That’s a different design goal than “answer questions fast”, and it shows in how the whole system is structured around continuity instead of single-turn replies.
And there’s a second twist buried in the post. Once you self-host LIA, it can double as a family AI server. You become the admin, and you get a panel to track API usage across everyone using it, family, friends, whoever you invite in. Each sub-user gets their own memory and personality thread with LIA, so your partner’s conversations don’t bleed into your kid’s homework help sessions, but you as the admin can still see the aggregate spend across the household. That’s not something you see in most personal assistant projects, most of them assume a single user and stop there, leaving you to either share one account and one memory, or spin up separate installs and separate API keys for everyone.
Here’s how to actually try it if the concept clicks for you:
- ⚙️ Clone the GitHub repo and read the “how it works” page first, before touching any code. The architecture is the whole selling point here, and skipping straight to installation means you’ll miss why certain pieces are wired together the way they are.
- 🧠 Spin up the one-click interface and let it connect to your model provider, RAG setup, and any MCP tools you already run. This is also the point to decide which model you’re pointing it at, since the emotional and reflective memory layers will lean on that model for every interaction, so a cheaper model will feel noticeably flatter than a stronger one.
- 👨👩👧 If you’re setting it up for the household, add family members as sub-users right away instead of retrofitting it later. Migrating memory and conversation history after the fact is exactly the kind of cleanup you want to avoid.
- 📊 Check the admin panel after a few days. That’s where you’ll see who’s burning through API calls and on what, which is also a decent early warning system if someone in the house starts feeding it novel-length prompts.
A couple of things worth knowing before you commit an evening to this. The emotional system and reflective memory need real conversations to build up, so judging LIA after five test messages will feel flat. Give it a week of actual use before deciding if the personality layer adds anything for you. Treat the first few days like onboarding a new hire, short exchanges, some context about your routine, maybe a correction or two when it misreads your tone. That’s what feeds the reflective memory enough to start sounding like it actually knows you.
Also worth checking: the “why” page the author linked breaks down the reasoning behind wrapping image creation, RAG, skills, MCP, and scheduled tasks into one interface instead of stitching tools together yourself. If you’ve been duct-taping five different services into your own assistant setup, one for image gen, one for retrieval, one for scheduling, that page is the part to read closely, since it’s basically the author’s case for why the maintenance tax of running five tools outweighs the flexibility you lose by consolidating into one.
One caveat, and it’s a fair one. This is described by its own creator as “unapologetically vibe-coded”, so go in expecting a solo builder’s project, not a funded startup with an SLA. That’s not a knock, plenty of the best tools in this space started exactly that way. Just set expectations before you self-host it for six people and call it a business tool, and keep an eye on the issues tab before you lean on it for anything you can’t afford to have break mid-week.
Pro tip: star the repo before you forget, and skim the linked “story” page first if you’re curious how the whole thing came together. It gives you the reasoning behind the emotional system, which makes the rest of the docs click faster. Worth bookmarking the architecture page too, you’ll probably want to reference it again once you start customizing prompts.
If you’re the type who runs your own home AI stack anyway, this is worth an hour of your Saturday. Head over to the original thread, read the top comments, and see if the family server angle solves a problem you already have. 🚀
Frequently Asked Questions
Q: Will LIA’s personality become repetitive over long conversations?
LIA addresses this with reflective memory, a system that learns from past interactions rather than just storing history. This is specifically designed to prevent the repetitive looping other setups can fall into.
Q: Can non-technical family members actually use LIA without getting lost?
Yes. LIA has a one-click interface designed for ease of use. When self-hosted as a family server, you control the admin side (managing API consumption per user), while family members just interact with a simple interface without needing keys or worrying about billing.
Q: How customizable are the personality and emotional systems?
The personality and emotional systems are both highly customizable. The documentation guides you on what you can adjust, from light tweaks to deeper personality engineering.
Q: Is the codebase actually clean and maintainable?
Yes. The author treated this as an enterprise-grade project with serious attention to code structure and documentation, so you can confidently take ownership and build on it without inheriting technical debt.
LangChain+LangGraph – Free open source projet – Documentations + prompts (30+)
by u/jeyjey9434 in PromptEngineering