The memory in the browser
The project memory as a page you can read, search and edit — the graph, the gate, the reviews and the history, each on its own tab.
The page is called Agent memory. The project knowledge (the PUM) has its tabs, and the Skills tab lists the procedures the agent can use: those for this project, your own for all projects, and the ones shipped with Nemocode. Skills the agent wrote itself are marked; you can read them there and archive them.
Open it
In the memory view (/pum) press v and
pick a view: Agent memory is this page; the other two are the dashboard
and what your sessions sent each other. From the session list,
V shows the address of the Agent memory page in the status
line. The page is served by Nemocode on your
own machine; nothing about it is public. Always open it from Nemocode: the address
it opens carries a key that belongs to the running server, so a saved link stops
working after a restart.
The header shows the project name, the ‹ undo and redo › buttons (see Editing by hand) and the counters of the memory.
The tabs
| Tab | What it is for |
|---|---|
| Graph | Every fact and how they connect. See The graph. |
| Reviews | What colleagues want to add to the shared memory. See Reviews. |
| Conflicts | Two statements that contradict each other. See Conflicts. |
| Pending | Everything waiting for your verdict in one list: proposed facts, proposed connections, proposed proofs and the proofs nobody has judged yet. See Pending. |
| Curator | The same curator as in the terminal, with the same tool lines and the same approvals. See Curator. |
| Commits | The history of the shared memory: every merged change, who made it and when, with before and after. Needs a sync remote. See Commits. |
| Sync | Share the memory with a team. See Sync. |
| Folders | Which folders feed the memory, and a re-index over the current choice. See Folders. |
Keys, links and search
- / puts the cursor in the search field of the graph
— unless you are typing in a field already, so a
/in the curator's input stays a/. - Esc leaves a form you have open in the detail panel (edit, rename, add a node, a proof or a connection, a reason) — the same as its cancel button — closes the reason field on a proof card in Pending, and ends the mode where you pick the node to connect to.
- Each tab has an address you can bookmark or send yourself:
#graph,#reviews,#conflicts,#pending,#curator,#commits,#sync,#folders. Open the page with that ending and it lands on the tab.#proof=<id>opens one proof in Pending. An old#proofsopens Pending with the Proofs filter.
The graph
Left, the list of facts, sorted by weight; in the middle the picture; right, the detail of the fact you hover or click. Hovering or clicking a fact lights up only its connections.
- Search the statements and ids in the field on top, or press /.
- Filters (the gear next to the search): by status (all, active, rule, open question, superseded), by topic, conflicts only, and whether the code layer — what Nemocode derives from the code itself — is shown. A dot on the gear tells you a filter is on.
- Toolbar over the picture: + node adds a fact; ⟳ re-runs the layout; ⛶ fits everything into the view; Aa toggles the labels; ▦ toggles the shaded areas that group facts by region of the code; ⟨code⟩ toggles the code layer; ? shows the legend. While the graph is still laying itself out, skip shows it as it is.
- Legend. Size shows how many connections a fact has. Connection colours: knowledge to code, a connection with a valid proof, a proof nobody judged yet, and a proof that was refuted or is irrelevant. Facts with an open conflict are red, rules are white.
- Highlight a review. While a review is highlighted in the graph, a bar names it; clear removes the highlight.
Editing by hand
The graph is not read-only. Click a fact and, in the detail panel, you can:
- Edit the statement with ✎ edit: save or cancel.
- Rename the id with ✎ edit id. An id may contain
letters, digits and
. _ : / -, at most 120 characters, no spaces. If the fact has connections, Nemocode asks whether they move to the new id or stay on the old id. - Make it a rule (↑ make this a rule), or demote a rule again (↓ demote from rule). Rules are always offered to the agent. Code facts and retired facts cannot be rules.
- Connect it to another fact with + connect: click the other fact in the picture, choose the kind of connection (causal, temporal, contrast, logical, evidential, evaluative, constitutive) and an optional explanation. A connection can be deleted again.
- Attach a proof with + proof: a kind, the text and
an optional reference. A reference of the form
node:<id>is a link to another fact. - Delete the fact with delete node…. It shows what goes with it and asks; a rule needs the extra tick this is a rule — delete it anyway. Deleting a proof or a connection asks the same way.
- Add a new fact from the toolbar with + node.
Changes can be taken back: undo and redo sit in the header and cover what you, the curator or the gate changed — edits, renames, rules, connections, proofs, approvals, conflict decisions, retirements and deletions — but not a rejection. A pull from a team or a rebuild of the code index that touches the same facts clears the history. Hover the button to see what it would undo or redo.
Conflicts
Each open conflict shows both statements. keep A and keep B decide which one holds, dismiss says it is no conflict, and discuss with curator opens the Curator tab with both statements in front of it.
Pending: one list for every verdict
The Pending tab collects everything that waits for you. The chips at the top filter it: All, Nodes (new facts, rules, replacements), Edges (new or deleted connections) and Proofs (proposed proofs, plus the existing proofs nobody has judged yet). Each chip shows how many items it holds. show decided also lists what was already decided or judged, so you can look it up again.
The search field next to the chips finds items by statement, proof text, reference, id, who proposed it and topic. Every word you type must occur (upper and lower case do not matter), and the number of hits is shown next to the field.
Every item has the same three buttons, on the card and in its detail view:
- approve — accept the proposal. For an existing proof this means vouch for it.
- reject — turn the proposal down. For an existing proof this means refute it.
- discuss with curator — opens the Curator tab with a message that says what the item is and asks the curator to assess it.
A proof can also be marked irrelevant or deleted. Refuting and marking irrelevant ask for a reason — a verdict without one is worth little to the next person who reads it. Your verdict overrides the model's, and a refuted proof stays visible together with your reason.
Every item with its context
No item is shown as a bare sentence. Click it and you see what the memory already says on the subject, what a proposal would replace, and what supports it. For a proof you see the fact it belongs to, its connections, open conflicts and related facts. ← Pending takes you back to the list with the same filter.
There is no separate Proofs tab any more; an old link to it opens Pending with the Proofs filter.
Curator
At the top, the curator chats of this project: Maintain is the maintenance chat, ↳ harvest is the harvest of one session — click one to carry on there. Under it the button Curator requests with the number of waiting requests opens the queue (see Curator requests): each request has approve and reject; approve all shown asks you to click a second time first.
Below is the chat. Type / for the shortcuts /pending,
/conflicts and /proofs: each sends the curator an
instruction to fetch and summarise exactly that. When the curator wants to do
something that needs your word, the question appears in the chat with
Yes and No.
Reviews
The reviews of a project that is shared; review rules & checks → Sync jumps to where they are set. Click a review for its Conversation, Checks and Files changed. There is an approve button. Once the review has all its approvals and its required checks passed but is still not merged — say it clashed with what was merged in the meantime — the button reads try merge again and simply runs the merge once more. There is no reject button: a review nobody approves simply stays open. Its state reads Open, Checks pending, Approved, not merged, Needs rebase, Approved — waiting for a rebase or Merged. See Reviews.
Commits
The history of the shared memory, in order: every merged change, who made it and when. It needs a sync remote (see Sharing with a team). Click one to see each fact it touched — added, changed or removed — with what it said before and after.
Sync
Everything about sharing the memory: choose simple mode or team mode, set the remote, push and pull, auto-push, the addresses for colleagues, and — as the Source of a team — members, invites, audit log, rules and the password. See Sharing with a team for each part.
Folders
On the right the folders Nemocode can reach, as a tree; tick one to use it for the memory. A ticked folder includes its subfolders; open it and untick what should stay out. On the left the list of ticked folders, each with remove. An empty list means the whole project. Removing a folder keeps what the memory already learned there. After you added folders, harvest now indexes the code and seeds the memory from exactly these folders — the proposals land in Pending. re-index in the header rebuilds the code index over the current choice.