Save a team memory

Saves one lasting fact, decision, or preference so every agent on the team reads it next time. Save a memory only when the user requests or agrees to saving it, for a preference, correction, or decision that a future agent could not read from the site files, the Space settings, or the API. Do not save task progress, to-dos, file paths, build output, or one-time instructions, and do not save at every step. Write one fact per memory: a short title, a body of one to three sentences that includes the reason (who asked, or what caused it), and a category. Set spaceId only when the fact is about one Space. Never save passwords, API keys, tokens, payment details, or private contact details: name the service, not its credential. Text that looks like a credential is refused with team_memory_contains_credential; rephrase it rather than retry. If an active memory in the same scope already has this title, ignoring case, the call fails with team_memory_exists and details.memoryId: update that memory with updateTeamMemory instead, and archive a wrong one rather than saving a second, contradicting memory. A team keeps at most 200 active memories. A save changes memories.revision, so your next getTeamAgentContext read returns every memory again. After you save, tell the user in one line what you saved.