Carry project facts, decisions, and handoff notes across approved clients without copying them between chats.
A project is a scope plus a path convention
For baseline memory scoping, XMemo does not require a separate project object: a project is expressed by the scope a memory is written under and the logical path namespace inside it, so the same account can carry many projects without cross-contamination. On top of that memory boundary, Project Workspaces add structured project state (Project API, TODO tracking, and recorded decisions) for cross-client collaboration.
- Write project facts under a stable path such as projects/<name>/decisions.
- Pass the project scope on both write and read so retrieval stays bounded.
- Project Workspaces layer structured project state—including Project APIs, durable TODOs, and recorded decisions—over the underlying memory boundary.
- Use team_id when the project boundary is a team rather than one owner.
Write a project decision
Attach the record to the project path and scope at write time; nothing else has to be configured first.
await client.recordDecision(
'Remote agents should use network MCP, not SSH stdio',
{ source: 'codex', scope: 'memory-os' },
);
Continue a project in another client
A second client recalls the same scope and gets the project context back without the user re-explaining it.
const context = await client.recallContext('recent agent integration progress', {
scope: 'memory-os',
maxItems: 6,
maxTokens: 1200,
});
Persona flows
ChatGPT user
Give ChatGPT durable access to your XMemo preferences, project facts, decisions, and TODOs without pasting bearer tokens into a chat.
Save a synthetic preference or project note, start a new chat, then ask ChatGPT to recall it through XMemo before continuing work.
Copilot / Codex developer
Carry repo decisions, coding conventions, bug-fix notes, and task history between IDE and CLI agents.
Record a codebase decision or bug fix, then ask the next IDE or CLI agent to recall the relevant XMemo context before editing.
Team / enterprise pilot owner
Evaluate shared memory with account controls, source attribution, export/delete workflows, and reviewer-safe setup evidence.
Have a pilot member save a synthetic team memory, confirm source attribution in XMemo, then review delete/export and support paths.