@vincemakes/kiso-ask-ext 0.44.0 → 0.45.1

package/README.md

@@ -19,6 +19,12 @@ The same artifact can be installed as a user-level extension (copy
 `dist/kiso-ask.mjs` into `~/.kiso/extensions/`), in which case the
 installing code supplies its own bridge.
 
+A host supplies the bridge the same way: `createAskExtension(ui)`, where
+`ui.ask(spec, signal, ctx)` answers the questions. `ctx` is
+`{ sessionId, callId }` from the tool context, so a host that serves many
+sessions from one runtime knows which session is asking and which call
+the answer belongs to.
+
 ## Durability
 
 No new mechanisms. The call is durable as its `tool_call_end`, the answers

package/dist/kiso-ask.mjs

@@ -98,9 +98,11 @@ function resultContent(result) {
 }
 
 /**
- * The factory. `ui` is the panel bridge: `{ ask(spec, signal) → Promise<
- * {answers:[…]} | {declined:[…]} > }`. The CLI builds it over the
- * editor's panel slot; a test can pass any object with that one method.
+ * The factory. `ui` is the panel bridge: `{ ask(spec, signal, ctx) →
+ * Promise< {answers:[…]} | {declined:[…]} > }`, where `ctx` is
+ * `{ sessionId, callId }` from the tool context. The CLI builds it over the
+ * editor's panel slot and ignores `ctx`; a test can pass any object with
+ * that one method.
  */
 export default async function createAskExtension(ui) {
 	// TTY gating by construction: no bridge, no tool. The extension still
@@ -144,7 +146,10 @@ export default async function createAskExtension(ui) {
 					// The schema already refused an empty list; this guard is
 					// for direct tool use (a test, a bridge under repair).
 					if (questions.length === 0) return { content: "ask_user: no questions", isError: true };
-					const result = await ui.ask({ questions }, ctx?.signal);
+					// The third argument tells a host WHICH session and call is asking: one
+					// runtime may serve many sessions, and a bridge built per runtime cannot
+					// know otherwise. Both are the tool context's own values, passed through.
+					const result = await ui.ask({ questions }, ctx?.signal, { sessionId: ctx?.sessionId, callId: ctx?.callId });
 					return { content: resultContent(result), isError: false };
 				},
 			},

package/index.d.ts

@@ -10,9 +10,20 @@
 import type { KisoExtension } from "@vincemakes/kiso-core";
 import type { AskResult, AskSpec } from "@vincemakes/kiso-tui-cells";
 
-/** The panel bridge the CLI implements over its editor's panel slot. */
+/** Which session and which tool call is asking — the tool context's own
+ *  values, passed through. Optional because the context declares them
+ *  optional: a direct call of the tool with a bare context gets
+ *  `undefined`, never a made-up id. */
+export interface AskCallContext {
+	readonly sessionId?: string;
+	readonly callId?: string;
+}
+
+/** The panel bridge. The CLI implements it over its editor's panel slot
+ *  and ignores `ctx`; a host serving many sessions from one runtime reads
+ *  `ctx` to route the question to the right session. */
 export interface AskUI {
-	ask(spec: AskSpec, signal?: { readonly aborted: boolean }): Promise<AskResult>;
+	ask(spec: AskSpec, signal?: { readonly aborted: boolean }, ctx?: AskCallContext): Promise<AskResult>;
 }
 
 declare const createAskExtension: (ui?: AskUI) => Promise<KisoExtension>;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vincemakes/kiso-ask-ext",
-	"version": "0.44.0",
+	"version": "0.45.1",
 	"description": "kiso official ask extension \u2014 ask_user option panels: the model asks the human, the answers are durable facts",
 	"type": "module",
 	"license": "MIT",
@@ -23,7 +23,7 @@
 		"test": "vitest run"
 	},
 	"devDependencies": {
-		"@vincemakes/kiso-core": "0.44.0",
+		"@vincemakes/kiso-core": "0.45.1",
 		"@types/node": "^26.1.2",
 		"typescript": "^5.7.2",
 		"vitest": "^3.0.0"