Skip to content

Save to a base from a conversation#

A conversation often ends with something worth keeping: a decision, an answer that took a while to get, a summary. Save to a base keeps it as a note in a knowledge base — Markdown with its title, date, where it came from and which model wrote it — so later searches find it and cite it.

Nothing is saved without you: you choose the base, read what will be kept, and save it.

Before you begin#

  • A knowledge base to save into (Build a knowledge base; one without source drives, filled only with notes, works too).
  • Permission to add to it: knowledge-bases:write-content.

Save a message#

In the app's chat (Assistant) or the console's Playground:

  1. On the message, open its actions and choose Save to a base.
  2. Choose the knowledge base, and what to save:
    • This message — as it is. A message of yours is saved with the source chat; an answer, with the source model and the model's name.
    • A summary of the conversation, written by the model — choose Write the summary; read it, change it if you like, and save that (source model).
  3. Check the title (from the conversation, editable) and choose Save to the base.

The note is named after its date and title (notes/saved/2026-10-12-release-plan.md) and is found by searches a few seconds later.

$ astra metis note handbook --title "Release plan" --source model --conversation "Planning" \
    --text "We ship Metis notes on Friday; Ana owns the announcement."
To handbook: “Release plan” (source: model)

We ship Metis notes on Friday; Ana owns the announcement.

Save this note? [y/N] y
saved as notes/saved/2026-10-12-release-plan.md in handbook (found by searches after its next pass)

The text may come from --text, --file <path> or standard input. Without a terminal to ask on, astra saves only with --yes — the way a script or an assistant says the person already confirmed.

$ curl -fsS -X POST "$ASTRALYX_API/metis/knowledge-bases/handbook/notes" \
    -H "Authorization: Bearer $ASTRALYX_TOKEN" -H 'content-type: application/json' \
    -d '{"title": "Release plan", "text": "We ship Metis notes on Friday; Ana owns the announcement.", "source": "model", "conversation": "Planning", "model": "qwen3-8b"}'
{"path":"saved/2026-10-12-release-plan.md","document":"notes/saved/2026-10-12-release-plan.md","source":"metis-handbook","title":"Release plan"}

What a note looks like#

notes/saved/2026-10-12-release-plan.md
---
title: "Release plan"
date: "2026-10-12T14:03:00Z"
source: "model"
conversation: "Planning"
model: "qwen3-8b"
---

# Release plan

We ship Metis notes on Friday; Ana owns the announcement.
Field Values
title Up to 200 characters
date When it was said (default: when it was saved)
source chat (a person's words), model (a model's answer or summary), upload, api
conversation, model When known
text Markdown, up to 256 KB — upload longer text as a file

Keep a file you attach#

When you attach a document to a chat message (a PDF, a Markdown or text file, a Word document), turn on Keep in a base and choose the base: the model reads it for this conversation, and the same file is added to the base so later searches find it. Photos are not kept: a base reads text.

Where it is kept#

The conversation itself stays where it was: the app keeps its chats on your phone, the Playground in your browser. Only what you save is sent, to the base's machine, where it is written in the base's own notes (Where added files live).