zhumy0323-hue/yanis-aicompanies-nsfw

This project is a self hosted backend for building a long term AI companion, driven by the Claude Code CLI. Its README is written in Chinese, and the core idea is that a Telegram bot and a web app both talk to the same backend, share the same memory, and present the same personality, no matter which one you use to say something. The author describes it not as a chatbot demo but as a skeleton for lasting companionship. The AI is meant to remember previous conversations, reach out to you on its own initiative, stay consistent across whichever entry point you use, and optionally connect to physical toys, voice input and output, and push notifications. Memory works in three layers: recent conversation history, automatic summaries that get saved over time, and a relevance based retrieval system with a fallback. The AI can also take real actions, since special markers embedded in its replies can control connected toys, update a task panel, record promises you made, or open a web page. Operators get basic commands like status checks, logs, restart, and shutdown, protected by a whitelist and a confirmation step, plus automatic alerts. What you get in this repository is described as a sanitized reference version. The full working code and documentation are here, but the original author's API keys, identity details, and private data have all been removed, with the personality replaced by a template you are expected to fill in yourself after forking. Setup takes roughly five minutes and requires the Bun JavaScript runtime, the Claude Code CLI already logged in, and tmux, with an optional reverse proxy for HTTPS if you want the Telegram Mini App or the web app to work fully. The README includes a fairly detailed troubleshooting section covering common self hosting problems, such as PATH issues under systemd, GitHub connection problems behind certain networks, and authentication token handling. All conversation data and memory files are stored locally in a SQLite database and JSON files on your own server, and are excluded from the git repository by default. The author suggests releasing your own fork under the MIT license or one of your own choosing.