Notebooks

A notebook is where your writing lives. Notes, drafts, research, project material, meeting records — anything you would keep.

Underneath, a notebook is a Git repository and every note is a Markdown file. That is not an implementation detail you are expected to ignore; it is the point.

• Every save is a commit, so nothing is silently overwritten and you can see what changed and when.
• Notes are plain .md files, readable by any editor.
• You can clone a notebook to your laptop and work in VS Code or Obsidian.
• Branches let you draft a reorganisation without touching the main version.
• If Kyra vanished tomorrow, you would still have your notes and their full history.

Notebooks are not memory

Both hold things you told Kyra. They are for different jobs.

	Notebook	Memory
Holds	Content you wrote	Facts about you and your decisions
Shape	Files, any length	Single sentences
You edit it	Directly, in an editor	By telling Kyra to forget or correct something
Kyra uses it	When you ask, or when searching	Automatically, whenever relevant
Example	“Launch retrospective”, 900 words	“Prefers short written summaries”

Say “save that as a note” to force a note; say “remember that” to force a memory. Left alone, Kyra picks — and it picks correctly most of the time.

Cloud and local

Type	Stored	Good for
Cloud	With Kyra, synced across your signed-in devices	Everything: sync, sharing, publishing, branches, Git access, and Kyra reaching it
Local: browser	Only in the browser you created it in	Private scratch work on one machine

Cloud is the default and the one the rest of the product is built around. A local notebook is genuinely local — Kyra cannot see it, other devices cannot see it, and clearing your browser data deletes it.

Note

Creating cloud notebooks and some collaboration features depend on your plan. When something is gated, Kyra opens the billing page rather than failing quietly.

Creating one

Portal → Notebooks → New notebook. Give it a name, a URL slug, and optionally a description.

By voice: “Make me a notebook for the house renovation.”

How many

Fewer than you think. A notebook is a boundary for access and publishing, not for tidiness — Kyra searches across all of them, and tags and links handle organisation.

Make a new notebook when the answer to “who can see this?” or “is this published?” differs. Otherwise use folders.

A reasonable set:

• Personal — everything of your own
• Work — if it needs different sharing
• One per published thing
• One per collaboration, shared with the people involved

Getting around

Open a notebook and you get a file tree on the left, tabs across the top, and the editor in the middle.

• New note / New folder to add things
• Drag in the tree to move them
• Right-click for rename, move, delete
• Search, or Cmd/Ctrl+K, across titles and content

A notebook lives at kyra-hi.com/<owner>/<notebook>, and an open note adds a path parameter — so any note has a URL you can paste to a colleague who has access.

Where notes go when you capture by voice

Voice capture writes into your configured destination, which by default is a cloud notebook. Kyra confirms which notebook it used, and you can send it elsewhere:

“Save this in the work notebook.” “Add that to the launch note.”

Adding to an existing note appends rather than replacing it. Kyra can also make targeted edits to part of a note without rewriting the rest.

Tip

If you are still in your first days with Kyra it will occasionally offer to save things as notes. That offer fades once you have got the hang of it — repeated prompting is a nag, not a feature. Asking always works.

Next

• Writing notes — the editor and everything Markdown supports.
• Finding things — search, links, and the knowledge graph.
• History and branches
• Sharing and publishing
• Using your notebook from your own machine