claire / plugins Developer hub
Plugin product system · concept 01

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
ONE MESSAGE, ONE ACTION live trace
  1. 01
    WHATSAPP · MAYA KIM

    “Tuesday at 10 works for me. Let’s do 45 minutes.”

  2. 02
    CLAIRE DETECTED

    A confirmed time · confidence 94%

  3. 03
    CALENDAR · DRAFT ACTION

    Launch review with Maya

    Tue, Aug 18 · 10:00–10:45 · Luc / Work risk: low_write · reversible
  4. 04
    YOU APPROVED · 10:04

    Event created · receipt written

    Undo
Scope: this chat only No other conversation was read
THE SAFETY CONTRACT

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.

  1. 01
    Claire identifies a useful moment Signal detection runs on the conversations you selected—nothing more.
  2. 02
    The plugin drafts a typed action Inputs, destination, and schema are fixed before anything is shown.
  3. 03
    You review sensitive writes Anything another person can see waits for an explicit yes.
  4. 04
    Every result stays visible A receipt records source, actor, inputs, result, and the undo path.
PRODUCT MODEL

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.

01
DISCOVER

Plugin library

Curated integrations grouped by what they help accomplish, not by API vocabulary.

02
CONNECT

Scoped access

Account authorization is separate from access to Claire conversations.

03
CONFIGURE

Conversation rules

Choose the people, chats, signals, and approval level for each automation.

04
CONTROL

Approval inbox

Review action, source messages, destination, and exact data before execution.

05
AUDIT

Activity & receipts

See what ran, why it ran, what changed, and how to undo or disconnect it.

PLUGIN COMPONENTS

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.

PLUGIN IDENTITY
31
CalendarVERIFIED

Vendor identity never substitutes for permission or trust status.

RISK & APPROVAL
READ ONLYASK EVERY TIMEAUTO-RUN

Auto-run is available only for low-risk, reversible actions.

ACTION RECEIPT
Event createdApproved by you · 10:04

Receipts preserve source, actor, destination, inputs, and result.

CONTEXT SCOPE

Conversation access is granted independently of account OAuth.

BUILD ONE

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.