Reply in thread without ever opening Gmail

Gmail's UI is fine. The friction isn't the UI — it's the journey: realize you should reply, switch apps, search the thread, scroll to the bottom, click Reply, write, click Send, switch back.

Cut the trip out.

You: Reply to Sarah's invoice email — say I'll process it by Friday and thank her for the patience.

Kin searches your Gmail for the most recent email from Sarah matching the description, drafts a reply that preserves the In-Reply-To and References headers (so Gmail threads it correctly on her side), quotes the draft back to you, sends on confirmation.

What "correct threading" means

A reply that's not in-thread shows up as a new email in the recipient's inbox. It breaks the conversation, looks unprofessional, and often gets missed. Kin's reply path explicitly fetches the original message's Message-ID header and includes it in the new message — so it lands as a reply.

The whole conversation, on demand

You: Show me my full conversation with Maya about the apartment.

Kin calls list_email_threads with a query like from:maya OR to:maya apartment, picks the matching thread, then get_email_thread to fetch all messages with bodies in chronological order. You see the entire conversation in chat, summarized.

Thread-level actions

• Reply to the whole thread: "Reply to that thread saying I'll get back to them tomorrow."
• Archive an entire thread: modify_thread_labels removes INBOX from all messages at once.
• Trash a thread: "Trash this whole conversation" — one call removes every message.
• Apply labels: "Label the whole thread as 'Negotiations'."

Single-message commands still work for granular control. Thread-level commands save round-trips when you mean "the whole back-and-forth."