This section is designed to help the Project better understand you. Here you can share any information about yourself that you consider important. The data you provide will be structured and compiled into the core of the memory tree, as the Project prioritizes your personality above all else. Everything else will merely reinforce this knowledge. The more the Project knows, the more accurate the interaction will be.

In this section, you set how assistants in the Project should behave. After each exchange, the app looks at each of your messages in turn and decides what should be kept as saved conduct: general expectations, personal boundaries, things that must not be done, and step-by-step habits (pure thanks or “ok” alone usually add nothing). The assistant should keep replies short — clarify only what is unclear, briefly reflect what it understood, and confirm in plain language that it will follow your rules — not deliver long policy essays in chat.

Use this thread to note third-party data you want the project to remember: public APIs, REST endpoints, and simple services (weather, market quotes, reservoir levels, and the like). This is not for LLM provider keys or .env secrets — only external services you name here. After each exchange, Keeper 2 may save structured rows (name, description, URL, service-specific key) into a local store from the conversation. Example endpoint (replace with your own HTTPS URL): https://api.example.org/v1/resource?… To check your connected APIs against what is stored, include the hashtag #data in your message.

This section is for product help with MF0-1984: how the app works, where settings and data live, and how to use features safely on your machine. You can ask using any connected model (pick the provider badge below); answers are based on the bundled project handoff plus this scope note — not on your theme threads or Memory tree.

Messages are not saved and do not appear in Themes or Memory tree. Analytics and billing work as normal. The session is cleared when you leave.