Bring your knowledge

If your team’s knowledge is a folder of markdown — a wiki export, an Obsidian vault, a docs repo, a pile of meeting notes in Drive — this is the shortest path to something the whole team can browse, search, and connect their agents to.

It does not have to be a folder. If your knowledge lives in Notion, Drive, Confluence, or Slack, the agent you already run has access to those, and that makes it the connector: hand it the import procedure and it will materialize those pages into the same faithful import pipeline. For a local folder or ZIP, direct upload is the shortest path and produces the same per-file receipt.

Either way this reads, and never writes back. Nothing in your existing tools is modified or moved, no sync is set up, and no credential of ours touches your systems. You get a copy, so trying costs you nothing. A copy drifts once people keep authoring somewhere else, so run both for a week or two, compare the answers, and then decide whether the Brain becomes the place you write.

Drag the folder in

Open app.nicia.ai, choose New Brain, and drop a folder or a .zip on the upload panel. Nicia scans first and creates nothing until you confirm the preview.

Scanning team-wiki.zip
  312 markdown files, 4.1 MB
  312 documents, 47 links

Creating Brain team:acme
Uploading  ████████████████████  312/312
Indexing   ████████████████████  done

Brain ready.

That is the whole thing, and nothing you already built is lost on the way in:

What you have	What it becomes
Folder structure	Each document’s source path, kept as metadata
Frontmatter keys	Preserved as document metadata
[[wikilinks]]	Kept in the document text; unresolved ones named
A type: you invented	Source metadata; classify it later if useful
Anything else	Prose, searchable and citable

Every file lands as a document: its own bytes, verbatim, with its path and frontmatter beside it. The import types nothing and writes no records, so a wrong type: in a source file can never put a wrong fact into the Brain. If you curated this by hand, had an LLM organise it, or brought it from GBrain, that work is all still there in the documents, and the Brain Agent can turn it into typed records afterwards, each one a proposal you review. Keys we do not recognise are stored, not dropped. See Schemas.

Re-run the same import any time. The receipt identifies unchanged files, versions edits, preserves unambiguous moves, and reports conflicts or missing source files without erasing either side.

Run the same import with your coding agent

Copy the import procedure into Claude Code, Codex, or Cursor. It uses the same API sequence as the app: provision the stable Brain handle, upload one ZIP for a read-only preview, show you the scan, wait for your confirmation, commit the durable import, and verify a cited answer.

The agent must account for every source entry and report partial results. It is told to ask one question when the source root or privacy scope is ambiguous and to stop truthfully when it cannot read the source. There is no separate CLI implementation with different fidelity rules.

What you get

A document per file, browsable immediately and indexed for search as the import settles. The built-in Brain Agent then proposes typed records from those documents, each grounded in a quote from the file it came from. Nothing it infers lands until a person accepts it in Review, and the document itself is never rewritten.

Ask the Brain something in app.nicia.ai, or from a connected agent once you’ve shared it with your team — “who owns billing?” comes back grounded in the actual documents, with a citation for every claim:

Billing is owned by the Payments squad; Priya Raman has been the DRI since the March reorg.

— handbook/teams/payments.md, notes/2026-03-11-reorg.md

If an answer looks wrong, the file it came from is one click away.

What if my markdown is messy?

That is the normal case and it is fine. Import never fails on structure it does not recognise — untyped files become plain documents, which are still fully searchable and citable. Structure is something you add later if you want it, not a precondition.

If you want to see what Nicia thinks your shape is, GET /v1/brains/{handle}/schema/candidates reports the field patterns it noticed across your files (person — 41 files — fields: name (98%), team (71%), and so on); POST /v1/brains/{handle}/schema/promote turns selected recurring keys into a governed additive-schema proposal. Nothing changes until Review accepts it, and skipping every suggestion leaves the Brain complete as it is.

Next

• Share it with your team — invite people, connect Claude Code and Codex.
• Keep it good — review, and letting agents contribute.