abhishek
8537b09f33
The panel has been complete except for the one part that answers. Its composer was deliberately disabled — it used to accept text, light up the send button, and swallow the submit, because no assistant endpoint existed. This connects it to the one that does. It is enabled only when a model is configured AND the page has an agent, checked at runtime via /assistant/status rather than assumed at build time. The placeholder says which of the two is missing: "Not connected yet" no model on this deployment "No assistant for this page yet" no agent for this route "Ask about this page" live Two different facts, two different sentences. A person on Inventory can move to Sales and get an answer today; a person whose deployment has no model can do nothing from the browser. Flattening both into "not connected" would be true and useless. The old rule is kept: never accept a message nothing will read. An answer shows its working — the tools it ran, their row counts, and a link to the page holding the same rows. Buddy states things with the confidence of a sentence, and the only honest way to present that is beside the evidence, so a person can disagree with it. Refused calls are shown too: an answer that quietly dropped one would look like Buddy chose not to look. A partial answer says so in amber, not as a grey hint. An answer cut off mid-sentence reads as a complete one otherwise, which is the failure the flag exists to prevent. The thread clears on navigation. An answer about Sales sitting above the Inventory page reads as being about what is on screen; losing the history is the smaller cost. Phase 2 ships one agent, covering Console and Sales. The rest arrive as backend config, not as changes here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
67 lines
2.2 KiB
TypeScript
67 lines
2.2 KiB
TypeScript
/**
|
|
* Nearle Buddy.
|
|
*
|
|
* Two calls: is this switched on, and here is a question. The tenant is not one
|
|
* of them — the server reads it from the session token, which is the whole
|
|
* point. A request body that carried a tenant would be a request body somebody
|
|
* could edit.
|
|
*/
|
|
|
|
import { api, WEB } from './client';
|
|
|
|
/** One tool the assistant ran, so an answer can show its working. */
|
|
export interface AssistantStep {
|
|
tool: string;
|
|
/** `ok` or `refused`. Refusals are shown, not hidden — an answer that quietly
|
|
dropped one would look like Buddy chose not to look. */
|
|
outcome: string;
|
|
rows?: number;
|
|
detail?: string;
|
|
scope?: string;
|
|
}
|
|
|
|
export interface AssistantAnswer {
|
|
reply: string;
|
|
used?: AssistantStep[];
|
|
model?: string;
|
|
/** Console routes showing the rows the answer came from. */
|
|
sources?: string[];
|
|
/**
|
|
* True when the loop hit its own limits, or the model's reply was cut off
|
|
* mid-sentence. The answer is still worth showing — a partial answer beats a
|
|
* spinner — but it must not be presented as the whole story.
|
|
*/
|
|
incomplete?: boolean;
|
|
}
|
|
|
|
/**
|
|
* Is the assistant switched on for this deployment?
|
|
*
|
|
* Asked once when the panel mounts, and the answer decides whether the composer
|
|
* is enabled. The panel has said "Not connected yet" since it was built; this is
|
|
* what finally answers that at runtime rather than at build time.
|
|
*
|
|
* Never throws. A console that cannot reach this endpoint should show a
|
|
* disabled field, not an error page — the panel is beside the work, not the
|
|
* work itself.
|
|
*/
|
|
export async function assistantAvailable(): Promise<boolean> {
|
|
try {
|
|
const status = await api.get<{ available?: boolean }>(`${WEB}/assistant/status`);
|
|
return status?.available === true;
|
|
} catch {
|
|
return false;
|
|
}
|
|
}
|
|
|
|
/**
|
|
* Ask a question.
|
|
*
|
|
* `agent` names which assistant answers — the console sends the one matching the
|
|
* page the panel sits beside. Phase 2 ships one, so an unknown name is refused
|
|
* rather than silently answered by the wrong agent.
|
|
*/
|
|
export async function askAssistant(agent: string, question: string): Promise<AssistantAnswer> {
|
|
return api.post<AssistantAnswer>(`${WEB}/assistant/ask`, { agent, question });
|
|
}
|