How do you import your existing memory into Nysa?

You can bring an existing GBrain brain, Obsidian vault, or folder of Markdown notes into Nysa through your AI agent. The agent packages and uploads the files, shows a preview of the people, companies and notes to be added, and waits for your confirmation before Nysa imports them.^[1]

That gives your team a way to keep the context it has already written. A folder of customer history or project decisions does not have to stay separate from the meetings and email that Nysa brings into your company brain.

What the import brings into your company brain

Import is for memory you already keep as a GBrain export or Markdown pages. That includes an Obsidian vault or a folder your agent uses for notes.

After you confirm, Nysa creates the people, companies and notes shown in the preview. Imported notes become facts with their source, like other notes in Nysa. They follow the same access scopes as the rest of the brain.

The dates matter, too. Nysa keeps the date at the top of a note or in a YYYY-MM-DD filename. If a note has no date, Nysa leaves it undated rather than assigning the day you imported it. An old decision should not look new just because you moved it.

Those imported notes sit alongside the context Nysa captures from ongoing work. The meeting-to-facts explainer describes how recorded conversations become facts with a quote, date and source. Import lets you bring earlier written context into that shared brain as well.

Your agent handles the files

The agent doing the import needs access to your files and a shell so it can find the folder and upload it. Nysa's import guide lists Claude Code, Codex, Cursor, OpenClaw and Hermes as options. A chat connection without access to the source folder is not enough for this workflow.

You also need the right Nysa access. Sign in through OAuth, the browser-based sign-in flow, or use a Read and write API key that includes your Personal scope or all scopes. Your role must be able to add knowledge: owner, admin or member.

Once connected, ask in ordinary language:

Import my Obsidian vault into Nysa. Show me the preview before confirming.

Or name the folder you want to use:

Bring the Markdown notes in this customer-history folder into Nysa. Stop at the preview so I can review it.

These are example requests, not special commands you need to memorize. Your agent uses Nysa's import tools over MCP, the connection that lets an agent use another service's tools. The MCP tools overview explains that connection in more detail.

The agent finds the brain on your computer, in a repository you name, or on your server, then packages and uploads it unchanged. You do not need to make a zip yourself. The upload link lasts 15 minutes, so have the source location ready before starting.

Review the preview before importing

The preview shows which people, companies and notes will be added. At this point, the agent has uploaded the files, but Nysa has not imported them into the brain yet.

Review the proposed contents against what you intended to bring over. Is this the customer-notes folder you chose, or a larger vault that also contains unrelated material? Are the people and companies relevant to your workspace? If you are uncertain about the source, pause before confirming.

In Nysa's documented workflow, asking to "try a small test" means uploading and showing the preview only. It does not mean approving the import. You still need to say yes before Nysa creates the records.

After confirmation, you can ask your agent, "What's the status of my import?" to follow progress. The documentation also states that repeating the confirmation is safe. That is a property of this import workflow, not a reason to assume every write tool behaves the same way.

An example with existing customer notes

Imagine a small team that has kept its customer notes in an Obsidian vault. This is a hypothetical example, not a customer story.

The founder has written down a customer's onboarding requirements and the reasons for a project decision. Another teammate uses a different agent and needs that history when preparing the next customer conversation.

The founder asks a file-capable agent to import the relevant vault into Nysa. Before confirming, they inspect the preview to check that it contains the intended customer notes. After the import completes, they ask the connected agent about a known decision and inspect its source.

The teammate can then use their own connected agent to ask about the allowed customer context. They do not inherit the founder's access simply because the notes were imported. Nysa's shared-access explainer covers the distinction between sharing a company brain and exposing everything in it.

What to know before moving a large folder

Supported import formats are GBrain exports and Markdown. Do not assume this feature imports every file type just because those files happen to be inside an Obsidian vault.

Your agent does not search Google Drive, Dropbox or the web to discover your brain. Give it the source location you intend to use. Import also needs write permission; a read-only API key cannot perform it.

Imported notes follow Nysa's scopes. Bringing a folder into the company brain does not make every note visible to every teammate or agent. Review sensitive material before uploading and check the relevant access afterward.

If you need to reverse the operation, Nysa lets you undo the whole import in one step from Settings in the web app. Keep that batch-level action distinct from correcting an individual fact later.

FAQ