Files
PaperClipAI/packages/shared
Bender (Paperclip agent)andClaude Fable 5 ee1361037c Propose connector telemetry events behind proposal markers
Adds three proposed product telemetry events for connectors (tool
connections), following doc/TELEMETRY_WORKFLOW.md. The runtime client
swallows unregistered first-party event names, so nothing is emitted
until the telemetry schema adopts them.

- connector.connection_created: which catalog connectors installations
  create connections for (gallery/api/example/composio_sync flows).
- connector.connection_updated: lifecycle transitions (status/enabled)
  after creation; silent when a committed write changed neither field.
- connector.invocation_completed: terminal invocation outcomes
  (succeeded/failed/denied/cancelled/timed_out/rate_limited) with
  origin (setup_test vs agent/user/system/plugin) and duration.

Connector identity is the reviewed catalog slug (config.sourceTemplateKey
validated against shared app-definitions); everything else reports the
literal "custom" so no user- or provider-controlled string leaves the
process. Only connection_purpose=tool rows emit. Emission is best-effort
and never awaited or allowed to throw on lifecycle paths.

Proposal: https://github.com/paperclipai/paperclip/issues/13578

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-09-23 18:13:01 +00:00
..
2026-03-12 13:09:22 -05:00