Skip to content

Cora's memory

Cora’s memory works like the CLAUDE.md file in a coding project. Each scope has a memory area, and its main file is CORA.md. Cora reads CORA.md at the start of every run, so what is in it is always in mind. CORA.md is also the index: it says which other notes and folders exist, and Cora opens those only when it needs them (D0618).

CORA.md is your team’s standing instructions to Cora, in the same way CLAUDE.md is for a coding assistant. Cora follows it as part of how she is told to work, the organisation’s file first and then the mission’s, with the mission’s winning where they differ. It does not switch off her safety rules: write tools still wait for an approval card, her file paths are still guarded, the spend cap and each mission’s separation still apply, and what you type privately is still never stored. Those are enforced by the system, not by CORA.md, so no note can loosen them.

There are two scopes:

  • Your organisation’s memory. It lives in the memory/ folder of your organisation’s team folder. It is shared by every mission. Cora reads its CORA.md in every run, whether or not the run uses the team sandbox.
  • A mission’s memory. It belongs to one mission and is kept with that mission’s documents, in the mission’s own store, not in the team folder. In a mission run Cora reads the organisation’s CORA.md first and then the mission’s CORA.md.

Neither is in Artifacts any more: what Cora knows is kept apart from what your team makes (US-01M7PP0C, D0854).

  • The organisation’s memory is in Settings, under Cora’s memory (/settings/memory), in the Organisation group after Permissions. Every member can open it. It has three parts, each a view of the same memory/ folder:
    • CORA.md, marked Always read, with the date it was last changed. This is memory/CORA.md.
    • Reference files: facts Cora should rely on, such as price lists, product details and policies. This is the memory/reference/ folder.
    • What Cora has learned: everything else in the memory folder, files and folders. Choose a file to read it on the same page; Close takes you back to the list.
  • A mission’s memory is the Memory tab of that mission’s details, with CORA.md pinned at the top and marked Always read. The tab says: “Notes Cora keeps about this mission. Only she writes here; ask her in the chat to change something.”

An old link to a memory file, such as /files?path=memory/reference/prices.csv, opens that file on the Cora’s memory page.

Short, durable notes: how your organisation likes things done, names and facts Cora has learned, and a list of the other memory files with a line on what each holds. Each CORA.md is read up to 20,000 characters. If it is longer, Cora sees the first 20,000 and a note that the rest was cut, so keep it short and move detail into other files that CORA.md points to. A scope with no CORA.md simply has nothing to read.

Memory Who writes it Who reads it
Your organisation’s memory The organisation’s admins and the platform super admin. Cora, at the start of every run, and every member of the organisation in Settings, Cora’s memory.
A mission’s memory Only Cora, with her memory tools. Cora, and the mission’s members in the mission’s Memory tab.

Organisation memory is written by the organisation’s admins and the platform super admin (John’s decisions D0618 and D0855). It is standing instructions for every mission in your organisation, so the people who may change it are a small group we already trust: your organisation’s admins, who already look after its connections, tools and members, and the platform super admin (a person in the core-operators group of our sign-in service whose verified email ends in @commercelab.com.au). An admin changes only their own organisation’s memory. Members read it and cannot change it; if it needs changing, they ask an admin. Every change is recorded in the organisation’s audit history with who made it, the file’s path and its size, never its text.

Cora reads it and cannot change it: her worker refuses any write, edit or delete under /workspace/memory/, and the files are read-only to her sandbox as well. That is on purpose. Cora reads organisation memory at the start of every run and also reads things from outside (web pages, emails, files), so if she could write it, one bad input could become a standing instruction for every mission.

A mission’s memory is owned by Cora. She writes it through memory tools of her own, only for the mission the run belongs to, and she cannot delete. People, including organisation admins and the super admin, read it in the mission’s Memory tab and cannot change it: the tab shows no Upload or New folder button, and the service refuses a person’s edit, upload, new folder or delete.

If a mission note is wrong or out of date, tell Cora in the mission’s chat, for example “Cora, Larkspur’s spring range now has four blends, not three. Please update your notes.” Cora changes her own note.

Changing it: Settings, or the pnpm cora:memory command

Section titled “Changing it: Settings, or the pnpm cora:memory command”

Settings, Cora’s memory shows Edit on CORA.md, Add a file under Reference files and Remove on a reference file or a file under What Cora has learned only to someone who may write: an organisation admin, or the super admin. Everyone else reads “Members can read it. Org admins can change it.” The page follows the service’s own answer, and the service checks every change again (D0854, D0855). Edit opens the whole of CORA.md in a box and saves it whole. Add a file takes one text file (.md, .markdown, .txt or .csv, up to 60,000 characters) into reference/, making the folder if it is not there. The same changes, and more, can be made from a terminal in the mission’s repository:

pnpm cora:memory list --org <orgId> [--path <folder>]
pnpm cora:memory get --org <orgId> --path CORA.md
pnpm cora:memory put --org <orgId> [--path <memory path>] ./CORA.md
pnpm cora:memory mkdir --org <orgId> --path notes
pnpm cora:memory rm --org <orgId> --path notes/old.md

put sends a local text file (.md, .markdown, .txt or .csv) to a memory path, and uses the file’s own name when you give no --path. The command asks for your email and a hidden password, and for a code if your account asks for one. It signs in the way the console does, keeps nothing, and never prints your password or tokens. It signs in to the live console’s user pool and app client by default (both are public ids); --client-id <id> or CORA_CLIENT_ID overrides the client. Add --base-url http://127.0.0.1:4311 to try it against the local stack. If you may not change that organisation’s memory, it says “You may not change this organisation’s memory (403)”.

The organisation’s memory is shared by every mission, and every member of the organisation can read it. A standing instruction set for the organisation applies to the Spring launch campaign and to the website refresh next month alike (D0528).

A mission’s memory is seen only by that mission’s members. The sandbox folder is shared by all of an organisation’s missions, so mission memory is kept out of it on purpose: a run in one mission can never read another mission’s memory (D0619). Anything only one mission’s members should see belongs in that mission’s memory or documents, not in the organisation’s memory.

The old Reference section is gone. Files that were in reference/ are moved once into memory/reference/, so they are now part of the organisation’s memory, and CORA.md can point to them. Nothing is deleted that was not first copied (D0618).

Cora’s memory holds the notes Cora chose to write, not a copy of your conversations. The mission’s messages stay in the mission’s chat. What you type when you polish a message with Cora is never stored (D0547).

The organisation’s memory counts towards the team folder’s 5 GB, shown on the storage meter on the Artifacts page. When the folder is full, new organisation memory cannot be added until space is freed (D0531). A mission’s memory is kept in the mission’s store and does not count towards the 5 GB.

Decisions: D0528, D0531, D0547, D0567, D0618, D0619, D0854.