notes

Notes

The Notes feature gives you a personal, structured markdown workspace that is fully accessible to Ariadne's AI agents. Notes are organised in folders, support rich markdown formatting, and can be searched semantically — meaning the agent can find relevant notes even when the wording doesn't match exactly.

Accessing Notes

Click Home → Notes in the top navigation.

Creating a Note

1. Click the New Note button (or the + icon next to a folder)
2. Give the note a title
3. Write your content using Markdown — headings, bullet lists, code blocks, tables, and more are all supported
4. Notes are saved automatically as you type

Organising Notes with Folders

Notes live inside folders, which you can create and nest as needed.

• Click New Folder to create a top-level folder
• Drag notes between folders to reorganise them
• Folders can be collapsed in the sidebar to reduce visual clutter
• Deleting a folder recursively deletes all notes and sub-folders inside it

Importing Files

You can drag and drop files from your desktop directly into the Notes sidebar to create notes from external files. Supported file types are converted to markdown on import.

Moving Notes Between Scopes

If you belong to an organisation, you can move notes between your personal space and the organisation's shared notes:

• All users can move personal notes into an organisation (contributing to shared knowledge)
• Organisation owners and managers can move notes out of an organisation back to their personal space

This makes it easy to draft a note privately and then publish it to your team, or for administrators to reorganise shared content.

Searching Notes

Use the search bar at the top of the Notes page to find notes by title or content.

Semantic Search

Because Ariadne indexes note content as vector embeddings, the agent can find notes using meaning rather than exact text. For example, if you ask the agent "do I have any notes about my project deadlines?", it can retrieve the relevant note even if the word "deadline" doesn't appear verbatim.

Agent Access to Notes

Any agent with access to the Notes tool collection can:

• Search your notes to find relevant context automatically
• Read a specific note when asked
• Create new notes on your behalf
• Update existing notes to keep them current

This makes notes a powerful way to give agents persistent, structured context — for example, storing your preferences, project specifications, or reference material.

Editing a Note While the Agent Edits It

The Notes editor is live. If Ariadne changes a note you have open, the change appears without a refresh, and the editor tells you who made it. Your unsaved text is never silently replaced: if an edit lands while you are typing, you are warned that someone else also edited the note rather than having your work overwritten.

For the fuller canvas experience — numbered revisions, an author against each change, and a visible history — open the document from a conversation's side panel or a project's Canvas tab. Those save through the canvas engine, which tracks every revision; the Notes page's own auto-save does not. See Chat & Conversations.

Project documents live in the note tree too, under a Projects folder, so anything a project writes is searchable alongside the rest of your notes.

Markdown Tips

Notes support standard Markdown:

# Heading 1
## Heading 2

**Bold text**, *italic text*

- Bullet point
- Another point

1. Numbered list

`inline code`

\```python
# Code block
print("Hello, Ariadne")
\```

| Column 1 | Column 2 |
|----------|----------|
| Value    | Value    |

Publishing Notes as Public Documentation

Any note, or any folder of notes, can be published as a read-only public page. Visitors do not sign in and cannot edit anything — they see the rendered Markdown and nothing else.

Publishing something

1. In Notes, right-click a note or a folder in the sidebar and choose Publish to web… (for the note you have open, the globe button in the toolbar does the same thing).
2. Set the public title and an optional description — these appear at the top of the page and are used as the page's description for search engines and link previews.
3. For a folder, decide whether to include subfolders. With this on, notes you add to the folder later are published automatically.
4. Optionally choose a share name, which becomes the address: https://your-ariadne/docs/getting-started. Leave it blank and you get a long random link instead.
5. Click Publish. The share link and the API address appear in the same dialog.

Choosing exactly what is public

After publishing a folder, the dialog lists every document the link currently exposes with a tick box beside each one. Untick anything that should stay private. Unticking a folder hides everything inside it.

Two rules are worth knowing:

• Scope is live, not a snapshot. Move a note out of a published folder and it stops being public immediately. Move one in and it becomes public immediately.
• Editing a published note publishes the edit. There is no separate "publish this version" step.

How you can tell a note is public

Public notes are marked with a globe wherever notes are listed — in the sidebar tree, in the recent grid and in search results — so you never have to open a note to find out whether it is exposed.

The note you have open also shows a Public pill next to its title. Click it to open the publishing settings for that note, or to find the folder that is publishing it.

The globe button in the sidebar header turns green while anything at all is published, and its tooltip says how many notes that currently covers.

Seeing what is public

Notes → the globe button in the sidebar header (or /notes/published) lists everything you have published: the share link, how many documents it exposes, how many times it has been read, and whether it is currently live. This is the page to check if you are ever unsure what is exposed.

Taking something down

In the publish dialog:

• Turn off "Link is live" to take the page down while keeping the address. Turning it back on restores the same link.
• Unpublish removes the grant entirely. The link stops working and will not come back.

Organisation notes

Notes owned by an organisation can only be published by an organisation owner or manager. Being a member is enough to read them, but not to put them on the internet.

The public API

Every publication is also a small read-only JSON API, with CORS open to any origin so a browser on any site can call it:

The index gives each document an id, a title, a path (its folder within the collection) and a short summary. That is enough to build a documentation site, pull the notes into a static site generator, or embed a help page in another application.

curl https://your-ariadne/api/public/v1/docs/getting-started
curl https://your-ariadne/api/public/v1/docs/getting-started/documents/42/raw

There is no authentication on these endpoints, by design — anything reachable through them is content you explicitly published.

Use Cases

• Meeting notes – capture action items and let the agent remind you of them later
• Project documentation – keep specs, decisions, and architecture notes that agents can reference
• Personal knowledge base – store facts, preferences, and reference material
• Scratch pad – rough notes the agent can help organise or expand
• Public documentation – publish a folder of notes as a documentation site with a share link