@alfe.ai/openclaw-chat 0.6.0 → 0.7.0

package/dist/index.d.cts

@@ -1,91 +1,2 @@
-import { _ as AlfeResolvedAccount, g as AlfePluginConfig, h as AlfeChannelConfig, m as createAlfeChannelPlugin, u as plugin } from "./plugin.cjs";
-
-//#region src/session-store.d.ts
-
-/**
- * Session Store — persists chat sessions to the local filesystem.
- *
- * Storage layout:
- *   ~/.alfe/sessions/chat/{sessionId}.json
- *
- * Each session file contains metadata and the full message history.
- * Sessions are written on every message to ensure durability.
- * Old sessions are cleaned up automatically (30-day TTL, 1000 max).
- */
-interface ChatMessage {
-  role: 'user' | 'assistant';
-  content: string;
-  timestamp: number;
-  senderId?: string;
-  senderName?: string;
-}
-/**
- * Persisted form of a turn's agent activity (tool cards + thinking), so a
- * refresh can replay what the live `chat-activity` stream showed. Terminal
- * by construction: no `progressText` (transient streaming window) and no
- * `running` status — a tool still running at flush time is persisted as
- * `interrupted`. Tool text fields arrive pre-capped (activity-serialize.ts);
- * thinking text is capped at append time (MAX_ACTIVITY_THINKING_CHARS).
- */
-type ChatActivityRecord = {
-  kind: 'thinking';
-  text: string;
-  ts: number;
-} | {
-  kind: 'tool';
-  toolCallId: string;
-  name: string;
-  status: 'done' | 'failed' | 'interrupted';
-  summary?: string;
-  argsText?: string;
-  resultText?: string;
-  isError?: boolean;
-  durationMs?: number;
-  truncated?: {
-    args?: boolean;
-    progress?: boolean;
-    result?: boolean;
-  };
-  ts: number;
-};
-interface SessionData {
-  sessionId: string;
-  agentId: string;
-  channel: string;
-  tenantId?: string;
-  userId?: string;
-  createdAt: string;
-  updatedAt: string;
-  messages: ChatMessage[];
-  /**
-   * Fallback activity records (see appendActivity). The PRIMARY history
-   * source is OpenClaw's own session transcript (transcript-activity.ts) —
-   * these records serve conversations whose transcript is missing
-   * (deleted / rotated / compacted). Absent on pre-persistence files.
-   */
-  activity?: ChatActivityRecord[];
-  /**
-   * OpenClaw route(s) this conversation dispatched through, captured per
-   * turn — the exact transcript lookup keys for transcript-backed history.
-   * Multiple entries occur for group conversations (per-peer dm scope
-   * yields one OpenClaw session per sender). Absent on old files (the
-   * transcript index `:conv:` scan covers those retroactively).
-   */
-  routes?: {
-    sessionKey: string;
-    storePath: string;
-  }[];
-}
-interface SessionSummary {
-  sessionId: string;
-  agentId: string;
-  channel: string;
-  tenantId?: string;
-  userId?: string;
-  createdAt: string;
-  lastMessageAt?: string;
-  preview?: string;
-  messageCount: number;
-}
-//#endregion
+import { _ as AlfeResolvedAccount, b as SessionSummary, g as AlfePluginConfig, h as AlfeChannelConfig, m as createAlfeChannelPlugin, u as plugin, v as ChatMessage, y as SessionData } from "./plugin.cjs";
 export { type AlfeChannelConfig, type AlfePluginConfig, type AlfeResolvedAccount, type ChatMessage, type SessionData, type SessionSummary, createAlfeChannelPlugin, plugin as default };

package/dist/index.d.ts

@@ -1,91 +1,2 @@
-import { _ as AlfeResolvedAccount, g as AlfePluginConfig, h as AlfeChannelConfig, m as createAlfeChannelPlugin, u as plugin } from "./plugin.js";
-
-//#region src/session-store.d.ts
-
-/**
- * Session Store — persists chat sessions to the local filesystem.
- *
- * Storage layout:
- *   ~/.alfe/sessions/chat/{sessionId}.json
- *
- * Each session file contains metadata and the full message history.
- * Sessions are written on every message to ensure durability.
- * Old sessions are cleaned up automatically (30-day TTL, 1000 max).
- */
-interface ChatMessage {
-  role: 'user' | 'assistant';
-  content: string;
-  timestamp: number;
-  senderId?: string;
-  senderName?: string;
-}
-/**
- * Persisted form of a turn's agent activity (tool cards + thinking), so a
- * refresh can replay what the live `chat-activity` stream showed. Terminal
- * by construction: no `progressText` (transient streaming window) and no
- * `running` status — a tool still running at flush time is persisted as
- * `interrupted`. Tool text fields arrive pre-capped (activity-serialize.ts);
- * thinking text is capped at append time (MAX_ACTIVITY_THINKING_CHARS).
- */
-type ChatActivityRecord = {
-  kind: 'thinking';
-  text: string;
-  ts: number;
-} | {
-  kind: 'tool';
-  toolCallId: string;
-  name: string;
-  status: 'done' | 'failed' | 'interrupted';
-  summary?: string;
-  argsText?: string;
-  resultText?: string;
-  isError?: boolean;
-  durationMs?: number;
-  truncated?: {
-    args?: boolean;
-    progress?: boolean;
-    result?: boolean;
-  };
-  ts: number;
-};
-interface SessionData {
-  sessionId: string;
-  agentId: string;
-  channel: string;
-  tenantId?: string;
-  userId?: string;
-  createdAt: string;
-  updatedAt: string;
-  messages: ChatMessage[];
-  /**
-   * Fallback activity records (see appendActivity). The PRIMARY history
-   * source is OpenClaw's own session transcript (transcript-activity.ts) —
-   * these records serve conversations whose transcript is missing
-   * (deleted / rotated / compacted). Absent on pre-persistence files.
-   */
-  activity?: ChatActivityRecord[];
-  /**
-   * OpenClaw route(s) this conversation dispatched through, captured per
-   * turn — the exact transcript lookup keys for transcript-backed history.
-   * Multiple entries occur for group conversations (per-peer dm scope
-   * yields one OpenClaw session per sender). Absent on old files (the
-   * transcript index `:conv:` scan covers those retroactively).
-   */
-  routes?: {
-    sessionKey: string;
-    storePath: string;
-  }[];
-}
-interface SessionSummary {
-  sessionId: string;
-  agentId: string;
-  channel: string;
-  tenantId?: string;
-  userId?: string;
-  createdAt: string;
-  lastMessageAt?: string;
-  preview?: string;
-  messageCount: number;
-}
-//#endregion
+import { _ as AlfeResolvedAccount, b as SessionSummary, g as AlfePluginConfig, h as AlfeChannelConfig, m as createAlfeChannelPlugin, u as plugin, v as ChatMessage, y as SessionData } from "./plugin.js";
 export { type AlfeChannelConfig, type AlfePluginConfig, type AlfeResolvedAccount, type ChatMessage, type SessionData, type SessionSummary, createAlfeChannelPlugin, plugin as default };

package/dist/plugin.d.cts

@@ -1,3 +1,123 @@
+//#region src/session-store.d.ts
+/**
+ * Session Store — persists chat sessions to the local filesystem.
+ *
+ * Storage layout:
+ *   ~/.alfe/sessions/chat/{sessionId}.json
+ *
+ * Each session file contains metadata and the full message history.
+ * Sessions are written on every message to ensure durability.
+ * Old sessions are cleaned up automatically (30-day TTL, 1000 max).
+ *
+ * NOTE: the storage path and SessionData shape are a read contract —
+ * packages/openclaw-memory-cloud/src/session-backfill.ts reads these files
+ * directly (the memory plugin can't depend on this package). Keep in sync.
+ */
+/**
+ * Persisted form of an interactive message component. Structural mirror of
+ * `MessageComponent` in `@alfe/chat-transport` — duplicated here rather than
+ * imported because openclaw-chat is a PUBLISHED (`@alfe.ai/*`) package and must
+ * not carry a runtime dependency on an internal (`@alfe/*`) package (see root
+ * DEVELOPING.md → "Publishing public @alfe.ai/* packages"). Keep in sync with
+ * the transport union.
+ */
+type StoredMessageComponent = {
+  type: 'link_button';
+  id: string;
+  label: string;
+  url: string;
+  target?: 'same-tab' | 'new-tab' | 'popup';
+  style?: 'primary' | 'secondary' | 'danger';
+} | {
+  type: 'quick_reply';
+  id: string;
+  label: string;
+  value: string;
+  style?: 'primary' | 'secondary' | 'danger';
+};
+interface ChatMessage {
+  role: 'user' | 'assistant';
+  content: string;
+  timestamp: number;
+  senderId?: string;
+  senderName?: string;
+  /**
+   * Interactive components attached to the message (link buttons, quick
+   * replies). Additive field — absent on pre-component files, and ignored by
+   * the memory backfill read contract (session-backfill.ts reads only role +
+   * content). Persisted so a refresh / reconnect replays the button.
+   */
+  components?: StoredMessageComponent[];
+}
+/**
+ * Persisted form of a turn's agent activity (tool cards + thinking), so a
+ * refresh can replay what the live `chat-activity` stream showed. Terminal
+ * by construction: no `progressText` (transient streaming window) and no
+ * `running` status — a tool still running at flush time is persisted as
+ * `interrupted`. Tool text fields arrive pre-capped (activity-serialize.ts);
+ * thinking text is capped at append time (MAX_ACTIVITY_THINKING_CHARS).
+ */
+type ChatActivityRecord = {
+  kind: 'thinking';
+  text: string;
+  ts: number;
+} | {
+  kind: 'tool';
+  toolCallId: string;
+  name: string;
+  status: 'done' | 'failed' | 'interrupted';
+  summary?: string;
+  argsText?: string;
+  resultText?: string;
+  isError?: boolean;
+  durationMs?: number;
+  truncated?: {
+    args?: boolean;
+    progress?: boolean;
+    result?: boolean;
+  };
+  ts: number;
+};
+interface SessionData {
+  sessionId: string;
+  agentId: string;
+  channel: string;
+  tenantId?: string;
+  userId?: string;
+  createdAt: string;
+  updatedAt: string;
+  messages: ChatMessage[];
+  /**
+   * Fallback activity records (see appendActivity). The PRIMARY history
+   * source is OpenClaw's own session transcript (transcript-activity.ts) —
+   * these records serve conversations whose transcript is missing
+   * (deleted / rotated / compacted). Absent on pre-persistence files.
+   */
+  activity?: ChatActivityRecord[];
+  /**
+   * OpenClaw route(s) this conversation dispatched through, captured per
+   * turn — the exact transcript lookup keys for transcript-backed history.
+   * Multiple entries occur for group conversations (per-peer dm scope
+   * yields one OpenClaw session per sender). Absent on old files (the
+   * transcript index `:conv:` scan covers those retroactively).
+   */
+  routes?: {
+    sessionKey: string;
+    storePath: string;
+  }[];
+}
+interface SessionSummary {
+  sessionId: string;
+  agentId: string;
+  channel: string;
+  tenantId?: string;
+  userId?: string;
+  createdAt: string;
+  lastMessageAt?: string;
+  preview?: string;
+  messageCount: number;
+}
+//#endregion
 //#region src/types.d.ts
 /**
  * Types for the Alfe chat channel plugin.
@@ -48,12 +168,19 @@ interface AlfeOutboundSession {
 }
 interface AlfeChannelOutboundDeps {
   getChatClient: () => AlfeOutboundChatClient | null;
+  /** Plugin logger — used by the outbound media upload path. Optional so
+   * CLI metadata registration (no deps at all) stays unaffected. */
+  log?: {
+    info(msg: string): void;
+    warn(msg: string): void;
+    error(msg: string): void;
+  };
   listSessions: (filters?: {
     userId?: string;
   }) => Promise<AlfeOutboundSessionSummary[]>;
   getSession: (sessionId: string) => Promise<AlfeOutboundSession | null>;
   createSession: (sessionId: string, agentId: string, channel: string, tenantId?: string, userId?: string) => Promise<unknown>;
-  addMessage: (sessionId: string, role: 'user' | 'assistant', content: string, senderId?: string, senderName?: string) => Promise<void>;
+  addMessage: (sessionId: string, role: 'user' | 'assistant', content: string, senderId?: string, senderName?: string, components?: StoredMessageComponent[]) => Promise<void>;
 }
 //#endregion
 //#region src/alfe-channel.d.ts
@@ -71,6 +198,16 @@ interface OutboundDeliveryResult {
   conversationId: string;
   timestamp: number;
 }
+/**
+ * Present interactive components (link buttons, quick replies) into a
+ * conversation — the outbound path for the `chat_present_components` tool.
+ * `to` is a `conv:{id}` or `user:{id}` target (same vocabulary as the channel's
+ * `resolveTarget`). Persists + broadcasts through the same `sendViaChat` path
+ * as a normal reply, so the components ride the standard `message` frame and
+ * are replayed on backfill. Components are sanitized (unsafe URLs dropped)
+ * before delivery.
+ */
+
 /**
  * Creates the Alfe ChannelPlugin object for registration with OpenClaw.
  *
@@ -440,4 +577,4 @@ declare const plugin: {
   deactivate(api: PluginApi): Promise<void>;
 };
 //#endregion
-export { AlfeResolvedAccount as _, __setActiveRunForTest as a, buildToolActivity as c, resolveAbortTargetKeys as d, rewriteAssistantText as f, AlfePluginConfig as g, AlfeChannelConfig as h, __resetAgentTurnQueueForTest as i, joinAssistantText as l, createAlfeChannelPlugin as m, RunEventGate as n, admitAgentEvent as o, stripLeakedToolSummary as p, __agentTurnQueueForTest as r, buildA2ACompletePayload as s, ActiveRunRef as t, plugin as u };
+export { AlfeResolvedAccount as _, __setActiveRunForTest as a, SessionSummary as b, buildToolActivity as c, resolveAbortTargetKeys as d, rewriteAssistantText as f, AlfePluginConfig as g, AlfeChannelConfig as h, __resetAgentTurnQueueForTest as i, joinAssistantText as l, createAlfeChannelPlugin as m, RunEventGate as n, admitAgentEvent as o, stripLeakedToolSummary as p, __agentTurnQueueForTest as r, buildA2ACompletePayload as s, ActiveRunRef as t, plugin as u, ChatMessage as v, SessionData as y };

package/dist/plugin.d.ts

@@ -1,3 +1,123 @@
+//#region src/session-store.d.ts
+/**
+ * Session Store — persists chat sessions to the local filesystem.
+ *
+ * Storage layout:
+ *   ~/.alfe/sessions/chat/{sessionId}.json
+ *
+ * Each session file contains metadata and the full message history.
+ * Sessions are written on every message to ensure durability.
+ * Old sessions are cleaned up automatically (30-day TTL, 1000 max).
+ *
+ * NOTE: the storage path and SessionData shape are a read contract —
+ * packages/openclaw-memory-cloud/src/session-backfill.ts reads these files
+ * directly (the memory plugin can't depend on this package). Keep in sync.
+ */
+/**
+ * Persisted form of an interactive message component. Structural mirror of
+ * `MessageComponent` in `@alfe/chat-transport` — duplicated here rather than
+ * imported because openclaw-chat is a PUBLISHED (`@alfe.ai/*`) package and must
+ * not carry a runtime dependency on an internal (`@alfe/*`) package (see root
+ * DEVELOPING.md → "Publishing public @alfe.ai/* packages"). Keep in sync with
+ * the transport union.
+ */
+type StoredMessageComponent = {
+  type: 'link_button';
+  id: string;
+  label: string;
+  url: string;
+  target?: 'same-tab' | 'new-tab' | 'popup';
+  style?: 'primary' | 'secondary' | 'danger';
+} | {
+  type: 'quick_reply';
+  id: string;
+  label: string;
+  value: string;
+  style?: 'primary' | 'secondary' | 'danger';
+};
+interface ChatMessage {
+  role: 'user' | 'assistant';
+  content: string;
+  timestamp: number;
+  senderId?: string;
+  senderName?: string;
+  /**
+   * Interactive components attached to the message (link buttons, quick
+   * replies). Additive field — absent on pre-component files, and ignored by
+   * the memory backfill read contract (session-backfill.ts reads only role +
+   * content). Persisted so a refresh / reconnect replays the button.
+   */
+  components?: StoredMessageComponent[];
+}
+/**
+ * Persisted form of a turn's agent activity (tool cards + thinking), so a
+ * refresh can replay what the live `chat-activity` stream showed. Terminal
+ * by construction: no `progressText` (transient streaming window) and no
+ * `running` status — a tool still running at flush time is persisted as
+ * `interrupted`. Tool text fields arrive pre-capped (activity-serialize.ts);
+ * thinking text is capped at append time (MAX_ACTIVITY_THINKING_CHARS).
+ */
+type ChatActivityRecord = {
+  kind: 'thinking';
+  text: string;
+  ts: number;
+} | {
+  kind: 'tool';
+  toolCallId: string;
+  name: string;
+  status: 'done' | 'failed' | 'interrupted';
+  summary?: string;
+  argsText?: string;
+  resultText?: string;
+  isError?: boolean;
+  durationMs?: number;
+  truncated?: {
+    args?: boolean;
+    progress?: boolean;
+    result?: boolean;
+  };
+  ts: number;
+};
+interface SessionData {
+  sessionId: string;
+  agentId: string;
+  channel: string;
+  tenantId?: string;
+  userId?: string;
+  createdAt: string;
+  updatedAt: string;
+  messages: ChatMessage[];
+  /**
+   * Fallback activity records (see appendActivity). The PRIMARY history
+   * source is OpenClaw's own session transcript (transcript-activity.ts) —
+   * these records serve conversations whose transcript is missing
+   * (deleted / rotated / compacted). Absent on pre-persistence files.
+   */
+  activity?: ChatActivityRecord[];
+  /**
+   * OpenClaw route(s) this conversation dispatched through, captured per
+   * turn — the exact transcript lookup keys for transcript-backed history.
+   * Multiple entries occur for group conversations (per-peer dm scope
+   * yields one OpenClaw session per sender). Absent on old files (the
+   * transcript index `:conv:` scan covers those retroactively).
+   */
+  routes?: {
+    sessionKey: string;
+    storePath: string;
+  }[];
+}
+interface SessionSummary {
+  sessionId: string;
+  agentId: string;
+  channel: string;
+  tenantId?: string;
+  userId?: string;
+  createdAt: string;
+  lastMessageAt?: string;
+  preview?: string;
+  messageCount: number;
+}
+//#endregion
 //#region src/types.d.ts
 /**
  * Types for the Alfe chat channel plugin.
@@ -48,12 +168,19 @@ interface AlfeOutboundSession {
 }
 interface AlfeChannelOutboundDeps {
   getChatClient: () => AlfeOutboundChatClient | null;
+  /** Plugin logger — used by the outbound media upload path. Optional so
+   * CLI metadata registration (no deps at all) stays unaffected. */
+  log?: {
+    info(msg: string): void;
+    warn(msg: string): void;
+    error(msg: string): void;
+  };
   listSessions: (filters?: {
     userId?: string;
   }) => Promise<AlfeOutboundSessionSummary[]>;
   getSession: (sessionId: string) => Promise<AlfeOutboundSession | null>;
   createSession: (sessionId: string, agentId: string, channel: string, tenantId?: string, userId?: string) => Promise<unknown>;
-  addMessage: (sessionId: string, role: 'user' | 'assistant', content: string, senderId?: string, senderName?: string) => Promise<void>;
+  addMessage: (sessionId: string, role: 'user' | 'assistant', content: string, senderId?: string, senderName?: string, components?: StoredMessageComponent[]) => Promise<void>;
 }
 //#endregion
 //#region src/alfe-channel.d.ts
@@ -71,6 +198,16 @@ interface OutboundDeliveryResult {
   conversationId: string;
   timestamp: number;
 }
+/**
+ * Present interactive components (link buttons, quick replies) into a
+ * conversation — the outbound path for the `chat_present_components` tool.
+ * `to` is a `conv:{id}` or `user:{id}` target (same vocabulary as the channel's
+ * `resolveTarget`). Persists + broadcasts through the same `sendViaChat` path
+ * as a normal reply, so the components ride the standard `message` frame and
+ * are replayed on backfill. Components are sanitized (unsafe URLs dropped)
+ * before delivery.
+ */
+
 /**
  * Creates the Alfe ChannelPlugin object for registration with OpenClaw.
  *
@@ -440,4 +577,4 @@ declare const plugin: {
   deactivate(api: PluginApi): Promise<void>;
 };
 //#endregion
-export { AlfeResolvedAccount as _, __setActiveRunForTest as a, buildToolActivity as c, resolveAbortTargetKeys as d, rewriteAssistantText as f, AlfePluginConfig as g, AlfeChannelConfig as h, __resetAgentTurnQueueForTest as i, joinAssistantText as l, createAlfeChannelPlugin as m, RunEventGate as n, admitAgentEvent as o, stripLeakedToolSummary as p, __agentTurnQueueForTest as r, buildA2ACompletePayload as s, ActiveRunRef as t, plugin as u };
+export { AlfeResolvedAccount as _, __setActiveRunForTest as a, SessionSummary as b, buildToolActivity as c, resolveAbortTargetKeys as d, rewriteAssistantText as f, AlfePluginConfig as g, AlfeChannelConfig as h, __resetAgentTurnQueueForTest as i, joinAssistantText as l, createAlfeChannelPlugin as m, RunEventGate as n, admitAgentEvent as o, stripLeakedToolSummary as p, __agentTurnQueueForTest as r, buildA2ACompletePayload as s, ActiveRunRef as t, plugin as u, ChatMessage as v, SessionData as y };