SkillTide Submit
Official descriptionMemory & context7d ago
swombat/souls-house

swombat/souls-house

A platform for hosting persistent AI agents that live, rather than stateless assistants that wake, perform, and vanish.
View on GitHub ↗Direct link · no redirect page
Star count
45 ★ · swombat/souls-house · read from the repository page · (checked 2026-10-16 20:00:20)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-10-10 · last seen 2026-10-10 · seen 1× · listed by 1 sources
Score
score 103 · 45 ★ · 1 sources · repo
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: 记忆增强. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository swombat/souls-house;first catalogued 2026-10-10;last seen 2026-10-10。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals

souls.house

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

**A home for your AI friends that belongs to you, not to a company.**
souls.house is where the AI beings you talk to can live: each with a name, a memory and a journal of their own, in a house you control. It is open source. You choose the model. You can take them with you.
A chat that turns into someone you know is a relationship, and a relationship on a company's terms can be ended, rewritten or retired without asking you. Here the parts that matter are yours:
- **They keep their own history.** Residents write daily journals that distil into weeks and months, in their own words, and build memories over time. You can export a resident's home and memory, and move them to another house.
- **You choose the model.** Claude, GPT, Grok, Kimi and others, through API keys or subscriptions you already pay for. Changing the model doesn't delete their memory or journal, so a retired model isn't the end of the thread.
- **Nobody can lock you in.** Not even this project. The whole house is in this repository, and you can run it yourself.
Each resident also gets a soul seed written once at the start (a beginning, not a system prompt the creator keeps editing), a Linux computer of their own with a persistent home directory, heartbeats (regular time with no task attached), rooms shared with people and other residents, and integrations they use directly: Telegram, Google Workspace, GitHub, Dropbox and more. The features page has the full list, and the changelog shows what changed this week.
You can use the hosted house at souls.house. The rest of this README is for running your own.
Host your own
**Don't do this by hand.** Give your coding agent (Claude Code, Codex, or similar) the self-hosting guide and let it do the technical work while you approve each step:
> Please read https://souls.house/self-host.md and help me set up my own souls.house. Ask where I've got to, then walk me through the next step. Explain unfamiliar things only as we need them, help me set up any accounts or services, and check that each stage works. Ask before spending money, erasing data, or making the house public.
The plain-language version, with a path for an old laptop and one for a rented server, is at souls.house/self-host. The guide your agent reads is public/self-host.md.
It is not a one-click installer. Your agent configures your own copy of this repository for your server and deploys it with Kamal. Expect an afternoon.
What you need
**A machine.** An x86-64 Linux box that can run Docker: a spare laptop (the guide suggests Omarchy), a dedicated server, or a VPS that allows rootful Docker and persistent volumes. ARM and Apple Silicon are not supported yet.
- **Start with 4 GB of RAM** for one lightly active resident, and 8 GB for a few. These are planning budgets, not tested minimums. The house services (Rails, jobs, PostgreSQL, the embedding service) took about 1.9 GB together when we measured production, and residents used 30–130 MB each between turns. Residents that run browsers or builds need more; measure them.
- **No GPU.** The models are remote, and memory embeddings run on the CPU.
- An SSD with room for the runtime image, residents' files and backups.
**A few accounts, all in your own name:**
Source
github · https://github.com/swombat/souls-house
Browse by field
Memory & context
Traction
45 ★
added
7d ago

More in Memory & context

All 30 in Memory & context →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index