Mojo UpDocs
AI Workbench

Memory

How agents remember your code and decisions, where that memory is kept, and how to explore it.

AI Workbench gives agents a shared memory so they do not re-read every file for every question. Each repository becomes a knowledge graph that agents query; a project's memory is all its repositories' graphs together, plus the notes, lessons and decisions the project keeps.

What is in memory

  • Each repository's graph, built by the Graphify engine from the code and documents. Agents ask it instead of opening files one by one.
  • Project notes: notes, lessons and decisions for the project, kept per repository or for the whole project.
  • Your organisation's or team's knowledge, when you are signed in to one: agents can ask it within what you may see.

Where memory is kept

ProjectIts memory is kept
Your own projectOn this computer
A project shared with your team hubBy your team's hub
Your organisation's projectBy your organisation

Project notes say where they are kept: "Kept on this computer", "Kept by your team's hub" or "Kept by" your organisation. A personal project's agents can ask your organisation's knowledge as you, but your project's memory stays with you.

Set it up

Open Settings → Memory (under Models & agents). The Graph memory group turns memory on and decides how it stays current:

  • Install the engine automatically and Build the graph automatically.
  • Keep the graph current with: how changes reach the graph.
  • Install git hooks.
  • Read changed documents with the memory model.
  • Share the memory map with the repository: keep the graph in git so others get it, if you choose to.

Settings → Setup's What helps your agents step also asks which model memory uses. You do not need a local model: memory can run on your default agent tool.

Explore memory

Open Memory. The default picture is the Rings: everything the workbench knows about a repository, a project or your organisation, arranged as rings.

  • Choose the scope: This repository, This project or Organisation.
  • The View pill switches between Rings and Shelves (the same hierarchy as rows), and between Nine tiers (Roadmap, Architecture, Plans, Governance, Library, Tools, Routines, Memory, Skills) and Five themes (Direction, Governance, Structure, the agent's kit, Memory). Your choice is remembered.
  • Open a group to see what sits inside it without losing the whole picture.
  • Explore opens the rings full screen, with Connections filters, zoom, Show the whole picture and Most connected ("what most else leans on: a good place to start"). Escape or Clear goes back.
  • The centre of the rings says what the repository, project or organisation is and where it is going. When nothing is written yet, ask the Scribe to write it.

Other modes in Memory: Project notes, Every repository, and Ask the organisation (or Ask the team on a team hub), which searches Everything, Code, Knowledge or Project.

Promote a note

In an organisation's project, a note can be shared more widely: open it in Memory, choose Promote to project memory…, then This repository's part or The whole project. A promoted note carries a sensitivity (public, internal, confidential or restricted), which decides who may read it.

Obsidian

Research reports and the knowledge memory can be written into an Obsidian vault as linked notes, with an Inbox whose notes are read back into memory. Set it up under Settings → Research & notebooks (Obsidian). It is optional.

On this page