Notes

Notes are where you keep theory, cheat sheets, your answers to common questions and the code of your pet projects. During a meeting, Copilot finds fragments similar to the current question and uses them in its answer.

Which notes Copilot sees

Search covers every note with "Use in RAG" turned on. It's on for new notes.

You can limit a meeting's search to certain folders: the "Notes for Copilot" button (folder icon) when creating the meeting or later on its page, and "Note folders" in the "AI features" menu in the web version of a meeting. Copilot then searches only in the selected folders, still among notes with "Use in RAG". Without a selection, it searches all notes. This keeps apart materials that shouldn't mix, for example several versions of your resume with different cases: put them in folders and pick the right one for the meeting.

During a meeting, notes search is turned off with "Use notes" in the "AI features" menu (the lightning icon). Each quick action has the same flag in its settings.

The notes panel in the overlay (Ctrl/Cmd + N) shows all notes except test projects, including those excluded from RAG. It's a cheat sheet for you and doesn't affect what the assistant sees.

How fragments are found

• The query is built from the current question: your message or the latest line plus one or two lines before it. Text from screenshots is not part of the search. For a quick action, the query is the action's own text.
• Search works both by meaning and by words. Note titles and section headings strongly affect whether a fragment is found.
• An answer gets at most three fragments, and at most two from one note. If the search doesn't finish in time, the answer comes without notes.
• The fragments the model received are shown under "Sources" below the answer. The model may not have used them.
• To make the assistant look up something specific in your notes, ask directly: "find in my notes…". It will then run a separate search.

After you edit a note, it's found by words right away and by meaning a few seconds later, once indexing finishes. Deleting a note or excluding it from RAG takes effect immediately.

Notes with RAG show their indexing status. Until a note is in the index, it can't be found by meaning. "Waiting for subscription" means indexing resumes once your subscription is active again. "Not indexed" means the text couldn't be processed: shorten the note or split it into parts and click "Reindex". Temporary failures of the indexing service are retried automatically.

"What Copilot finds" shows which fragments would go into the hint for a question you type. That way you can check before a meeting whether the right note is found. The check covers all notes with RAG and ignores meeting folders.

Questions and answers

The "Questions and answers" format is chosen when you create a note and can't be changed later. Such a note consists of question and answer cards.

In a meeting, a card works like any other fragment: the assistant finds a similar question and bases its answer on the card, but doesn't paste the answer verbatim. A card is always passed as a whole. To have it found by differently worded questions, fill in "Other phrasings"; the "Generate" button suggests variants.

Importing a list

Paste a ready list with "Import Markdown" in the collection editor:

## What is an index?
Answer in Markdown.

## What is a transaction?
Answer in Markdown.

Each line starting with ## begins a new card, and everything up to the next such line becomes the answer, including lists, code and ### subheadings. Lines like Q: … and A: … work too. Imported cards are added to the existing ones and saved with the "Save" button. Other phrasings are not recognized during import.

Uploading files

• Upload files accepts .md, .mdx, .txt and .pdf. Each file becomes a separate note.
• Import file inside a note replaces its text with the file contents instead of appending.
• A scanned PDF without a text layer is recognized by AI. If a PDF mixes text pages and scanned pages, the scanned ones are not recognized.

Test project

With "Upload test project" you can upload the code of a pet project so Copilot can answer questions about it. The whole project is stored as one note: you can't edit it by hand, and you update it with the "Replace" button. An answer gets at most two fragments from one note, so ask about the project specifically, naming the module, file or function. .env files, node_modules, build output and .git are skipped automatically. If the project doesn't fit the limit, the important files are checked first: README and manifests, entry points and routes, with tests and generated files last.

Files that contain something that looks like keys or passwords are unchecked when you upload. If you upload such a file anyway, those values are replaced with [REDACTED], so they reach neither the note nor Copilot's answers.

Export

You can download all notes and contexts as one zip archive from the notes library: notes come as Markdown files by folder, contexts as JSON.

Tips

• One topic per note. An answer gets at most two fragments from any single note.
• Give notes and headings clear names: fragments are found by them.
• Break long text up with headings, since fragments are cut by section.
• Before a meeting, add company specifics and exclude from RAG anything unrelated to the role.