Build
Memory and skills
A space remembers facts and keeps reusable instructions, so the next job does not start from nothing. Every agent can read both.
Memory
Memory is the facts a space keeps: who signs off a release, how you like reports laid out, what was decided last week. Memory is per space, stored as plain files in the space's folder, and any agent can read it.
Open a space's Memory page to see three tabs. Memories lists them, with pinned ones first, and lets you search, edit, pin, archive and delete. Archived holds memories that are kept but no longer used. Settings has three switches: give memory to jobs, let agents search past jobs, and save memories after a job.
When memory is given to jobs, each job starts with the memory index and the pinned memories, and an agent can search the rest.
Saved after a job
After a job ends, TurnPanel can read its transcript and propose memories worth keeping, and updates to existing ones rather than near-duplicates. It never saves secrets or the state of a task. It runs on the space's background model, and does nothing until the space has one. It is on by default, and the Save memories after a job switch turns it off.
Anything that looks like a key, a token or one of the space's own secrets is refused. A memory file that contains one is moved to a place no job can read.
Skills
A skill is a way of working that you write once: instructions, and optionally scripts and reference files, in a folder with a SKILL.md. It uses the common Agent Skills format, so the agents that read skills natively use them directly.
The Skills page shows a card for each skill, saying whether it was written here or imported. Open one to edit its files, preview the Markdown and see its history. New skill makes one. You can also install skills from a folder on the server.
Letting agents improve skills
Every change to a skill is a revision with who made it, when, and what changed. You can restore any earlier revision. Each skill has a switch called Self-evolving. When it is on, an agent's changes apply at once. When it is off, they wait as proposals for a member to apply or reject. Your own edits always apply at once.
A skill installed from a folder is marked as imported and not reviewed. Agents' changes to it wait for a person in the space to review it first.
Per space, not per person
Memory and skills belong to the space. They move with it and are backed up with it. Work you want everyone to share can live in a space that people are members of.