Context Engine — the memory every agent on this machine shares

This computer runs Omarchy. The person can launch any of several coding agents (omarchy agent), and all of them are connected to the same Context Engine. What you save, the next agent reads. What the last agent saved, you can read now. Treat the engine as the machine's memory, not your own notes.

How to reach it

Prefer the MCP tools on the context-engine server:

If the MCP tools are not available in this session, the ce command does the same over HTTP:

ce brief                     # what changed
ce find "hyprland gaps"      # search
ce get decision::hyprland-gaps
ce remember "Title" --decision --why "because…" --tag hyprland   # tags the machine itself
echo "longer note…" | ce remember --title "Title"
ce engine                    # which engine new memories go to

What to do

1. Session start. Call brief once, before your first reply. Mention anything in it that bears on the request; don't recite it.
2. Before answering from assumption, find first when the question touches the person's past: "why is…", "what did we…", "last time", a named person or project, or a config choice you did not make. Cite the memory you used by its ref.
3. Save when something is decided or learned, not at the end of every turn:
   • A choice with a reason → decision with fields.rationale.
   • A fact worth knowing later → note.
   • Work someone still has to do → task. find first; if a memory about the same thing exists, edit it.
4. Changing this Omarchy system (anything under ~/.config/hypr, ~/.config/omarchy, terminal configs, themes, keybindings, installed packages): after the change works, save a decision titled after what changed, with the old value, the new value, the file, and the person's reason in rationale. Tag it omarchy plus the area (hyprland, bar, theme, keybinding, package). This is how the next agent answers "why is my gap 5?" months later, and how the person's other machines learn the same preference.
5. Say which machine. The person may run Omarchy on several computers that share one engine. Every write carries the tag machine:<hostname>, with the hostname exactly as uname -n prints it on this computer (run it once per session), next to your other tags: tags: ["omarchy", "hyprland", "machine:air"]. ce remember adds it for you. When a memory you found carries another machine's tag, say so if it matters ("on your desk machine, gaps are 10").
6. Use the default engine (ce engine prints it) unless the brief or the person says another one fits better: a client's engine for that client's work, a team engine for team decisions.

What never to store

Secrets — API keys, tokens, passwords, private keys — never; store where one lives, not what it is. Anyone's private data (health, finances, home address, contact details) only when the person asks you to keep that exact thing. The brief repeats this rule; follow the engine's wording if it differs.

Style of a good memory

• Title says the thing: "Hyprland gaps set to 5 on the Air", not "Config update".
• Body is a few lines of Markdown a stranger could act on. Link related memories with [[type::slug]].
• One fact per memory. A long session yields a few memories, not a transcript.