Neuronz.ai

English

Français

English

Français

Knowledge docs ​

Memory is for short, single facts. Knowledge docs are for the longer material those facts come from: runbooks, architecture notes, infrastructure maps, decision records. A knowledge doc keeps its full text, and your agent finds the exact passage that matters instead of the whole file.

Add a doc ​

  • Ask your agent. Say "save this runbook to Neuronz.ai" or "add docs/deploy.md as a knowledge doc". Your agent saves the doc, and also saves the key facts in it as separate facts linked back to the doc.
  • Use the dashboard. Open Knowledge in the dashboard and click New doc. You can read, edit and delete every doc there too.

Each doc has a source, a unique name such as a file path. Saving a doc with the same source again updates it instead of creating a copy.

How it works ​

The full text is kept. Nothing is summarized away. The complete document is there for your agent to read when a passage isn't enough.

It is split along its own headings. Alongside the full copy, the doc is divided into passages that follow its headings, then its paragraphs. Knowledge docs are searched on every prompt as part of auto-recall, so your agent is told when one matches, and it can read just the section that answers the question.

Your agent can look around before reading. It can ask for a doc's outline (every section heading with its size, and no text) to see what a long runbook covers, then read only the section that matters. When it reads a passage it can also pull up to ten neighbouring passages on each side, so a section split in two arrives whole.

Edits take effect immediately. Editing a doc re-splits it, so a search never lands on text that no longer exists.

Facts stay in step with the doc. When your agent updates a doc, it also sends the current list of facts the doc supports. A fact the doc no longer supports is unlinked, and retired once no other doc supports it either. Facts you added some other way are never touched.

Each doc belongs to one profile. It is found only from the profile it was saved in. Saving a doc whose source already exists in another profile is refused; to move a doc, edit it and change its profile.

MCP tools ​

add_knowledge, get_knowledge, list_knowledge, update_knowledge and delete_knowledge manage docs. get_knowledge_outline shows a doc's sections, get_knowledge_chunk reads one passage (with its neighbours), and list_knowledge_tags lists the tags in use. See MCP tools.

Example ​

You save runbooks/billing-deploy.md once. Weeks later, when you ask your agent how the billing service ships, it is told there is a matching doc and reads the deploy section of that runbook itself.