@juspay/neurolink 12.4.3 → 12.5.0

package/dist/hitl/hitlManager.d.ts

@@ -97,4 +97,18 @@ export declare class HITLManager extends EventEmitter {
      * Get count of pending confirmations
      */
     getPendingCount(): number;
+    /**
+     * Whether a specific confirmation is still awaiting a response on this manager.
+     *
+     * A pending entry holds the `resolve`/`reject` of the suspended tool call, so it
+     * exists only in the memory of the manager that issued it. A manager constructed
+     * after the confirmation was issued — a session rebuilt from persisted state, for
+     * example — has an empty set, and `processUserResponse` for such an id logs a
+     * warning and returns without resolving anything.
+     *
+     * Callers that report an outcome back to a user should check this before treating
+     * a delivered `hitl:confirmation-response` as acted upon: the event being received
+     * says a listener existed, not that anything was waiting for it.
+     */
+    hasPendingConfirmation(confirmationId: string): boolean;
 }

package/dist/hitl/hitlManager.js

@@ -457,4 +457,20 @@ export class HITLManager extends EventEmitter {
     getPendingCount() {
         return this.pendingConfirmations.size;
     }
+    /**
+     * Whether a specific confirmation is still awaiting a response on this manager.
+     *
+     * A pending entry holds the `resolve`/`reject` of the suspended tool call, so it
+     * exists only in the memory of the manager that issued it. A manager constructed
+     * after the confirmation was issued — a session rebuilt from persisted state, for
+     * example — has an empty set, and `processUserResponse` for such an id logs a
+     * warning and returns without resolving anything.
+     *
+     * Callers that report an outcome back to a user should check this before treating
+     * a delivered `hitl:confirmation-response` as acted upon: the event being received
+     * says a listener existed, not that anything was waiting for it.
+     */
+    hasPendingConfirmation(confirmationId) {
+        return this.pendingConfirmations.has(confirmationId);
+    }
 }

package/dist/neurolink.d.ts

@@ -1311,6 +1311,43 @@ export declare class NeuroLink {
      * @see {@link NeuroLink.executeTool} for events related to tool execution
      */
     getEventEmitter(): TypedEventEmitter<NeuroLinkEvents>;
+    /**
+     * Whether a HITL confirmation is still awaiting a response on THIS instance.
+     *
+     * Emitting `hitl:confirmation-response` is not proof the decision landed. The
+     * forwarding listener for that event is installed once at construction, so
+     * `emitter.emit(...)` reports a listener was invoked even when nothing is
+     * waiting — the pending set lives one hop further in, on the HITL manager, and
+     * holds the `resolve`/`reject` of the suspended tool call. An instance built
+     * after the confirmation was issued (a session rebuilt from persisted state)
+     * therefore accepts the event and resolves nothing.
+     *
+     * Returns `false` in two different situations, which it deliberately does not
+     * distinguish: HITL was never configured on this instance, and the id is
+     * unknown or already settled. Both mean "emitting a response here achieves
+     * nothing", which is the question this answers. A caller that needs to tell a
+     * configuration mistake from an expired confirmation should check the HITL
+     * config separately rather than read that into this boolean.
+     *
+     * This is advisory, not atomic: it reports the state at the moment it is
+     * called. Nothing stops the confirmation timing out immediately afterwards, so
+     * emit on the answer without an `await` in between. Over the case it exists
+     * for — an instance rebuilt from persisted state, whose pending set is empty
+     * and can never repopulate for an id it never issued — absence cannot become
+     * presence, so the answer cannot go stale in the unsafe direction.
+     *
+     * @param confirmationId - The id from the `hitl:confirmation-request` event
+     * @returns `true` only if this instance is still holding that confirmation
+     *
+     * @example
+     * ```typescript
+     * if (!neurolink.hasPendingHITLConfirmation(confirmationId)) {
+     *   return refuse("This conversation has expired, so the action was not carried out.");
+     * }
+     * neurolink.getEventEmitter().emit("hitl:confirmation-response", { ... });
+     * ```
+     */
+    hasPendingHITLConfirmation(confirmationId: string): boolean;
     /**
      * Returns the instance-level tool-dedup configuration, or `undefined` when
      * toolDedup was not provided at construction time.

package/dist/neurolink.js

@@ -9132,6 +9132,45 @@ Current user's request: ${currentInput}`;
     getEventEmitter() {
         return this.emitter;
     }
+    /**
+     * Whether a HITL confirmation is still awaiting a response on THIS instance.
+     *
+     * Emitting `hitl:confirmation-response` is not proof the decision landed. The
+     * forwarding listener for that event is installed once at construction, so
+     * `emitter.emit(...)` reports a listener was invoked even when nothing is
+     * waiting — the pending set lives one hop further in, on the HITL manager, and
+     * holds the `resolve`/`reject` of the suspended tool call. An instance built
+     * after the confirmation was issued (a session rebuilt from persisted state)
+     * therefore accepts the event and resolves nothing.
+     *
+     * Returns `false` in two different situations, which it deliberately does not
+     * distinguish: HITL was never configured on this instance, and the id is
+     * unknown or already settled. Both mean "emitting a response here achieves
+     * nothing", which is the question this answers. A caller that needs to tell a
+     * configuration mistake from an expired confirmation should check the HITL
+     * config separately rather than read that into this boolean.
+     *
+     * This is advisory, not atomic: it reports the state at the moment it is
+     * called. Nothing stops the confirmation timing out immediately afterwards, so
+     * emit on the answer without an `await` in between. Over the case it exists
+     * for — an instance rebuilt from persisted state, whose pending set is empty
+     * and can never repopulate for an id it never issued — absence cannot become
+     * presence, so the answer cannot go stale in the unsafe direction.
+     *
+     * @param confirmationId - The id from the `hitl:confirmation-request` event
+     * @returns `true` only if this instance is still holding that confirmation
+     *
+     * @example
+     * ```typescript
+     * if (!neurolink.hasPendingHITLConfirmation(confirmationId)) {
+     *   return refuse("This conversation has expired, so the action was not carried out.");
+     * }
+     * neurolink.getEventEmitter().emit("hitl:confirmation-response", { ... });
+     * ```
+     */
+    hasPendingHITLConfirmation(confirmationId) {
+        return this.hitlManager?.hasPendingConfirmation(confirmationId) ?? false;
+    }
     /**
      * Returns the instance-level tool-dedup configuration, or `undefined` when
      * toolDedup was not provided at construction time.

package/dist/types/hitl.d.ts

@@ -228,6 +228,8 @@ export type HITLManager = {
     cleanup(): void;
     /** Get count of pending confirmations */
     getPendingCount(): number;
+    /** Whether a specific confirmation is still awaiting a response on this manager */
+    hasPendingConfirmation(confirmationId: string): boolean;
     /** EventEmitter methods for HITL events */
     on(event: string, listener: (...args: unknown[]) => void): HITLManager;
     emit(event: string, ...args: unknown[]): boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@juspay/neurolink",
-  "version": "12.4.3",
+  "version": "12.5.0",
   "packageManager": "pnpm@10.15.1",
   "description": "TypeScript AI SDK with 24+ LLM providers behind one consistent API. MCP-native (connect any MCP server), voice TTS/STT/realtime, RAG, agents, memory, context compaction. OpenAI · Anthropic · Gemini · Bedrock · Azure · Ollama · DeepSeek · NVIDIA NIM and more.",
   "author": {