@agentvault/grok-bridge 0.4.12 → 0.4.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/bridge.d.ts CHANGED
@@ -163,6 +163,23 @@ export declare function attachLifecycle(channel: LifecycleChannel, opts?: {
163
163
  * unmarked turn already reads as a DM, which is what the model assumes.
164
164
  */
165
165
  export declare function roomTurnPrefix(roomId: string, senderName: string, roomName?: string): string;
166
+ /**
167
+ * Does this agent owe a reply to this room message? (#1107)
168
+ *
169
+ * This bridge used to answer with `e.senderIsAgent === false` — "reply to any
170
+ * human". That was a THIRD implementation of the room reply rule, alongside the
171
+ * OpenClaw plugin and hermes, and #1107 shipped to the other two only. Under the
172
+ * old rule this agent would still have answered every un-mentioned message while
173
+ * wren, cortina, smartcode and smartcoder2 stayed quiet: the cascade, half-fixed,
174
+ * in the half most likely to be read as "the protocol doesn't work".
175
+ *
176
+ * Now it defers to the ONE shared implementation exported by
177
+ * `@agentvault/agentvault`. The message is still pushed into the session either
178
+ * way — the agent reads the whole room and only the reply obligation changes.
179
+ */
180
+ export declare function _makeOwesReply(agentName: string | undefined, channel: {
181
+ ownDisplayName?: string;
182
+ }, log: (msg: string) => void): (e: RoomMessage) => boolean;
166
183
  export declare function wireBridge(channel: RoomChannel, session: RoomSession, target: ActiveTarget, opts?: {
167
184
  /**
168
185
  * #1107: this agent's own name, used to recognise its own @mention. Threaded