Save meeting notes to Drive without opening Drive

After a meeting, you have a small window — maybe two minutes — before the next thing eats the memory of what was decided. The notes either get captured then or they don't get captured at all.

Make it one sentence.

You: Save this as "Sprint Review 2026-05-11.md" in my Notes folder.

Decisions: – Ship the Drive integration to early access this week – Push billing redesign to next sprint – Sarah owns the H1 hiring update

Next steps: – Maya to draft launch comms by Wed – Alex to scope the API rate-limit changes

Kin calls save_to_drive. The file appears in your Drive, in the folder you named. Link comes back in chat. Done.

Why a folder name works

When you say "my Notes folder," Kin doesn't guess — it lists your Drive folders, finds one called "Notes" (or anything close to it via fuzzy match), and uses that ID. If you have two folders both called Notes, it asks which one.

Beyond notes

The same primitive — save text to a Drive file — powers a lot of small frictions:

• Daily summary: "Save today's recap to my Journal folder."
• Brainstorm dump: "Save this list of ideas as 'Q2 Marketing Brainstorm' in Marketing."
• Quick reference: "Save this SQL query I keep forgetting to my Snippets folder."

Create folders too

You: Create a folder called "Client - Acme" inside my Projects folder.

Kin calls create_drive_folder with the right parent ID. The new folder is ready, and you can pipe more saves into it.

And copy, move, rename, share

The full Drive write surface is available:

• Copy a template doc: "Copy the Proposal Template to a file called 'Proposal - Acme' in the Client - Acme folder."
• Move a file: "Move all the contracts in my Inbox folder to Legal."
• Rename a file: "Rename 'Untitled doc' to 'Brand Guidelines v3'."
• Share a file: "Share the budget sheet with sarah@acme.com as a commenter."
• Trash a file: "Trash that old draft."

Each write quotes its action back before executing. You always know what's about to happen.