Inbox copilot for webmail
Draft replies and triage without a server.
For: Teams building on top of webmail
A content script that suggests reply drafts inside a webmail UI. Anouk's cache means re-opening the same thread reuses the earlier draft, and the queue keeps a busy inbox from hammering the provider.
The problem
Inbox tools generate a draft every time a thread opens. Opening the same thread repeatedly means repeated spend, and a user churning through 40 messages can easily hit provider rate limits.
How Anouk handles it
- ▸The draft request is keyed by thread id, so re-opening a thread returns the cached draft.
- ▸The per-provider queue paces requests as the user moves quickly through the inbox.
- ▸The user supplies their own key, so there is no shared backend cost or data custody to manage.
src/inbox.js
import { AIService } from 'anouk';
async function draftReply(thread) {
return AIService.call(
'Draft a concise, friendly reply',
thread.latestMessage,
`reply_${thread.id}`
);
} Anouk features used
AIService.call()Response cache (thread-keyed)Rate-limit queueSettings panel
Build this in an afternoon
Scaffold with anouk init, drop in the call above, and point it at a provider.