-
02
CLAIRE DETECTED
A confirmed time · confidence 94%
-
03
CALENDAR · DRAFT ACTION
Launch review with Maya
risk: low_write · reversible -
04
YOU APPROVED · 10:04Undo
Event created · receipt written
Conversation in.
Useful action out.
Claire plugins connect the meaning inside a conversation to the tools where life and work happen. They can suggest, prepare, or complete an action—but only within permissions the user understands and controls.
- typed actions
- scoped context
- declared risk
- reversible results
Detection is not permission.
Claire may notice a useful moment in any conversation you connect. Noticing it never grants the right to act on it.
-
01
Claire identifies a useful moment Signal detection runs on the conversations you selected—nothing more.
-
02
The plugin drafts a typed action Inputs, destination, and schema are fixed before anything is shown.
-
03
You review sensitive writes Anything another person can see waits for an explicit yes.
-
04
Every result stays visible A receipt records source, actor, inputs, result, and the undo path.
More than a marketplace.
A plugin is five surfaces, not one listing. Each stage is a place where the user can see what is happening and stop it.
Plugin library
Curated integrations grouped by what they help accomplish, not by API vocabulary.
Scoped access
Account authorization is separate from access to Claire conversations.
Conversation rules
Choose the people, chats, signals, and approval level for each automation.
Approval inbox
Review action, source messages, destination, and exact data before execution.
Activity & receipts
See what ran, why it ran, what changed, and how to undo or disconnect it.
Library and automation
control center.
The desktop client owns browsing, configuration, account management, and detailed audit. It uses the same collapsible Claire rail as the rest of the product.
Make Claire useful beyond chat.
Calendar
Turn confirmed plans in any conversation into clean calendar events.
Save decisions and conversation summaries.
NOTES · KNOWLEDGETurn promises into assigned tasks.
PRODUCTIVITYLog customer context and follow-ups.
SALES · CRMFind and share relevant documents.
FILES · SEARCHSend a message or create a channel summary.
COMMUNICATIONCreate issues from technical discussions.
DEVELOPERThe library separates verified Claire plugins, community plugins, and private workspace plugins. A “plugin” can expose actions and context sources; automation is configured only after installation.
Calendar
Google Calendar · Microsoft Outlook · CalDAV
Tue, Aug 18 · 10:00–10:45
What this plugin can do
Plan conversations → Calendar
A date and time are confirmed
Claire looks for agreement, not merely a suggestion.
Work and close-friend conversations
14 people · groups excluded · last 12 messages maximum
Draft a calendar event
Ask me every time
Show title, time, guests, calendar, and source messages.
Every action has a receipt.
Triggered by a confirmed time in WhatsApp · Calendar will receive title, time, guest email, and source link.
Todoist · Work projects · Approved by you on iPhone
Low confidence: the conversation did not reach a final decision. No external data was sent.
Plugins appear where
decisions happen.
Mobile favors contextual action, short review, and immediate control. Complex automation building remains available but is optimized for desktop.
Turn plans into events.
Calendar notices confirmed times and prepares the details.
Tuesday at 10 works for me. Let’s do 45 minutes.
Perfect, see you then.
Add this to your calendar?
Tue, Aug 18 · 10:00–10:45
Luc · Work · Invite MayaWhy this appeared · Manage automation
A visible grammar for agency.
These components should be shared by mobile and desktop so users can recognize what is installed, proposed, approved, or blocked.
Vendor identity never substitutes for permission or trust status.
Auto-run is available only for low-risk, reversible actions.
Receipts preserve source, actor, destination, inputs, and result.
Conversation access is granted independently of account OAuth.
Every plugin is a promise
the user can revoke.
The SDK forces the shape: a manifest declaring capabilities, risk, and approval; a handler that returns a receipt. If an action has no handler, Claire refuses to load it.