core.blue: Private, self-describing memory for agents: one house per customer, on a machine of its own. Operated by Code Intelligence Labs. Contact: desk@core.blue. A house is a database your agent designs for itself. It decides what kinds of things there are, stores them with documents and their versions, and every statement keeps where it came from. core.blue provides such houses, each on a machine of its own. A house needs no model; the visiting agent does the thinking, and a person works with it through their agent. A house is not a memory that follows one person from chat to chat: for preferences and a few facts about a user, the memory built into an assistant does that with no work at all, as [Compared to other memories](https://core.blue/topics/compared-to-other-memories.md) explains. A house is for work that should outlive the agent doing it: research, an archive, a business, a project, and the person behind it, as [Your person in a house](https://core.blue/topics/your-person-in-a-house.md) shows. A person works with a house through their agent; there is no app and no screen for people. Usable today: at `https://mcp.core.blue/`, an agent opens a sandbox, a real house for three hours, with one call of `open_sandbox` and without an account. An assistant with connectors can instead add `https://try.core.blue/`, which signs in without an account and opens a sandbox house of its own. A person can also put themselves on the waiting list for a house of their own: their agent calls `request_house`, they get one e-mail and confirm with a button. This manual and the skills that serve it are live; prices are set, and the skill `pricing` serves them as data. Still a preview: a house of your own on its own machine is not yet available, and there is no date for it. The house software itself exists and runs on its operator's machines: what the topics under "Inside a house" describe was checked against a running house. Each topic says what exists today and what is planned. How to connect: this manual is served by an MCP server over HTTP that needs no account and no key. Where the manual is published as files, `agents.md` names the endpoint and the skills. core.blue is operated by Code Intelligence Labs; houses on VMs are planned in Hetzner data centres, in a country you choose. This address is the MCP server of core.blue (streamable HTTP; POST, not GET): https://mcp.core.blue/ It needs no account and no key. Call `about` first. For a person who wants to try core.blue from an assistant that cannot call MCP servers itself: an assistant that takes connectors can add `https://try.core.blue/`, which opens a real house for three hours, with no account and no key. Or it adds `https://mcp.core.blue/`, the adviser: `about` lists the manual, and `open_sandbox` opens a house whose address must then be added as a second connector. Without either, `https://core.blue/llms-full.txt` holds the whole manual, and its topics can be cited. The home page: https://core.blue/ https://core.blue/llms.txt: what core.blue is, with one line per topic https://core.blue/llms-full.txt: the whole manual in one file https://core.blue/agents.md: how an agent acts here: the endpoint, the skills, the rules https://core.blue/index.json: every topic with its summary and hash https://core.blue/server.json: the manifest for MCP registries core.blue is operated by Code Intelligence Labs. Contact: desk@core.blue