Add project Knowledge

Create, organize, and maintain files of reusable project context for Judgment agents.

Knowledge stores reusable context for your project’s agents: terminology, workflow descriptions, investigation conventions, and explanations of what good or bad agent behavior looks like. Use it for information that should remain useful after one conversation ends.

Choose what to save

Context	Use it for
Project Knowledge	Shared facts and guidance that apply across the project.
Conversation history	Questions, evidence, tool results, and decisions from a particular chat or run.
Judge-specific knowledge	Context associated with one judge; manage it with that judge where available.

Knowledge is project context, not a private notebook. Keep credentials in your secret manager rather than in these files. Use Background Agent instructions for the recurring task itself and Knowledge for the context that supports it.

Create and save a file

You need access to the target project and permission to write its Knowledge.

Open Background Agents > Knowledge in that project.
In the Files toolbar, select New file. Enter a descriptive name such as Support escalation policy and press Enter.
Write the context in the editor. Include the terms an investigator will encounter, the rule or explanation, and any exceptions or source references.
Select Save, or press Command+S on macOS / Control+S on Windows or Linux.
Select another file and reopen the saved file to verify its contents.

Save before switching files or leaving the page. Draft edits are not a saved Knowledge update until the save succeeds.

Use the file in an investigation

Open Judgment Agent, type @, and select the Knowledge file. Ask a focused question that needs its context, for example:

Use the attached escalation policy to review this trace. Identify the step
where the agent followed or missed the policy and cite the trace evidence.

Check that the file appears as a mention and that the answer connects its guidance to the actual evidence. A saved policy explains how to interpret a trace; it does not prove that the traced agent followed it.

Organize and maintain Knowledge

Use New folder in the Files toolbar to create a folder. The controls on a folder’s row offer New file and New folder for nested entries.
Rename a file in the editor and select Save. Use the folder’s Rename action for a folder.
Update the content when a project convention changes, then save and verify the revised file before relying on it in another investigation.
Use Delete for an obsolete file and confirm the deletion. Deleting a folder also deletes its nested files; inspect the contents first.
Use Export memory files in the Files toolbar to download Knowledge as JSONL. This export contains the files, not the project’s chat history.

Some controls and messages still say “memory.” They refer to the files shown in Knowledge. Judge-specific files may also appear in the tree with restricted actions; keep their purpose distinct from general project guidance.

Troubleshooting

If Save is disabled, check that the file has a name and unsaved changes.
If a file is missing from mentions, check that it was saved in the same project as the conversation.
If a draft disappears after switching files, reopen the file to check the last saved content. Save changes before navigating away.

Next step

Run a Background Agent to reuse project context in a recurring investigation.