What to say
Kyra understands ordinary language; you do not need commands. This page exists because seeing what is possible is harder than saying it — most people use a third of what is there because nothing told them the rest existed.
Capture
Section titled “Capture”“Remember that I prefer British spelling.” “Remember we chose the flat rate over per-seat.” “Save a note: the launch blockers are pricing, onboarding copy, and the iOS build.” “Save this in the work notebook.” “Add that to the launch note.” “Note this down — I’ll explain in a second.”
Recall
Section titled “Recall”“What did we decide about pricing?” “Find my notes on the Rotterdam trip.” “What did I say last Tuesday about the migration?” “Have I written anything about this before?” “What do you remember about me?” “Read me the top of the launch note.”
Notes and notebooks
Section titled “Notes and notebooks”“Make me a notebook for the house renovation.” “Add a section about the pricing decision to the launch note.” “In the retro note, change the owner of the second action to Sam.” “Draw me a flowchart of the release process.” “Tidy up the research notebook.” — asks first, it is a big change “Open that note.”
Getting something written
Section titled “Getting something written”“Draft a short message to the team about the launch blockers. Don’t send it.” “Write up the argument for the flat rate.” “Turn that into an agenda.” “Make it shorter and less formal.” “Design this with me.”
Longer work
Section titled “Longer work”“Look into what changed in EU AI rules this year and write it up.” “Research the options and give me a recommendation.” “What are you working on?” “What needs approval?” “Cancel that.” “What went wrong?”
Steering the conversation
Section titled “Steering the conversation”“Short version.” “Go deeper.” “Skip ahead.” “Draft it.” “Save that.” “Stop — I meant the other one.”
Your device
Section titled “Your device”“What’s my next meeting?” “Move the design review to Thursday at two.” “Remind me to call Mark after lunch.” “Call Sarah.” “Copy that to my clipboard.” “Put on the album we talked about.”
Your machine
Section titled “Your machine”Needs computer control.
“What’s running on my machine?” “What needs me?” “Tell the auth one to keep v1 for now.” “Have the migration one use bcrypt instead, no need to stop.” “Hand the token-refresh session to me.” “Start a session to write the migration tests, branch off main.” “How much has that session cost?” “Open the billing router.” “Search the workspace for where we handle refunds.”
Account
Section titled “Account”“What plan am I on?” “How many credits do I have left?” “When do my credits reset?” “Switch to Dutch.” “Open my billing page.”
Feedback
Section titled “Feedback”“File a bug: the queue screen doesn’t refresh after a task finishes.” “Feature request: let me pin a notebook.”
Kyra captures it in your words, with the device context attached, and routes it to the people who can act on it. This is the actual channel — use it.
Phrasings that work better
Section titled “Phrasings that work better”Say what you want, not how to get it. “Move the design review to Thursday” beats “open my calendar, find the design review…”. Kyra picks the mechanism.
Say “don’t send it” when you mean it. Kyra would ask anyway, but saying it up front means the draft arrives with no interruption in the middle.
Name the notebook if it matters. “Save this in work” removes a question.
Refer to things loosely. “The auth one”, “that article about attention”. Kyra resolves by meaning and asks when genuinely ambiguous.
Correct in place. “No, per-seat” mid-sentence works. You do not need to start over.