Skip to content
KyraKyra H.I. Docs

Kyra H.I.

Kyra is a personal agent you talk to. Not a search box with a microphone on it — something closer to a capable colleague who happens to be reachable by voice, keeps your notes in order, remembers what you decided, and can act on your computer when you ask.

The bet behind it is simple. Typing is a bottleneck, not a feature. Most of the thinking you do away from a keyboard is lost by the time you reach one.

   Say it                    Kyra sorts it out                   You get it back
   ──────                    ─────────────────                   ───────────────
   "Remember we settled  →   files it as a durable memory   →    recalled next time
    on the flat rate."                                            it's relevant


   "Save that as a note" →   commits Markdown to a           →   editable, versioned,
                             Git-backed notebook                 yours to export


   "Draft the reply,     →   writes it, waits                →   you approve, then
    don't send it"                                                it sends


   "What's running       →   reads the coding sessions       →   answered by voice,
    on my machine?"          on your own computer                without opening a laptop

Three ways in

Section titled “Three ways in”

You do not have to adopt all of Kyra at once. Most people start with one of these and add the others when they need them.

Start here if you want to…Go to
TalkCapture thoughts, ask questions, get things drafted, hands-freeGetting started
WriteA notebook that survives Kyra — Markdown, Git history, publishableNotebooks
BuildKyra driving your editor and the coding agents on your machineComputer control

What it actually does

Section titled “What it actually does”

Captures without ceremony. You say a thing; it lands. Filing, tagging, and linking are Kyra’s job, not yours. Notes →

Remembers across conversations. Durable memories for decisions and preferences, searchable transcripts for everything else — and a page where you can read and delete any of it. Memory →

Does long work in the background. Anything that would leave you listening to silence becomes a task. Kyra says it is starting, gets on with it, and tells you when there is something to look at. Background work →

Asks before it acts. Sending, publishing, inviting, deleting, spawning work on your machine — all of it stops and checks first, and how often it checks is a setting you own, not one Kyra can talk you out of. Confirmations →

Works on your computer, not just your phone. A small local process lets Kyra open files in your editor, type at your cursor, and steer the Claude Code or Codex sessions you already have running. Computer control →

Stays yours. Notes are Markdown files in a Git repository you can clone, and every version is a commit. Kyra ceasing to exist would not take your notes with it. Git access →

The two surfaces

Section titled “The two surfaces”

Kyra is one product with two faces, and knowing which one to reach for saves a lot of frustration.

The mobile app is for talking. Capture, questions, quick results, approvals, checking what is running. It is the surface designed for when your hands are busy.

The web portal is for looking. Editing notes properly, reviewing transcripts, managing what Kyra remembers, sharing and publishing, organisations, billing, and every setting. It is the surface designed for a big screen and a keyboard.

They share everything. A note captured by voice in the car is open in the portal editor by the time you sit down.

Where to go next

Section titled “Where to go next”