@datalayer/agent-runtimes 1.3.95 → 1.3.96

package/lib/apps/plugins/agents/switchable.d.ts

@@ -55,6 +55,18 @@ export type SandboxTargetSpec = {
 };
 /** The four, in the order the control shows them: nearest first. */
 export declare const SANDBOX_TARGETS: readonly SandboxTarget[];
+/**
+ * Why a target is shown but not offered here — said on it — or nothing when
+ * it is offered.
+ *
+ * *Local* is a local agent with the Jupyter server it starts beside itself,
+ * and a web page has no machine of the reader's to start them on. Decided
+ * 2026-10-10 (Eric): not offered on the web for now, and left in the switch,
+ * held, so that a reader sees what exists and why it is not here. Inside
+ * JupyterLab it is offered as before — the same line the code-sandbox picker
+ * draws for a Jupyter Server's kernels (`codeSandboxProviders`).
+ */
+export declare function heldTargetReason(target: SandboxTarget): string | undefined;
 export declare const TARGET_SPECS: Record<SandboxTarget, SandboxTargetSpec>;
 /** Whether an agent runs on this target — the question the chat asks. */
 export declare function targetHasAgent(target: SandboxTarget): boolean;

package/lib/apps/plugins/agents/switchable.js

@@ -22,6 +22,7 @@
  * @module apps/plugins/agents/switchable
  */
 import { computed, signal, } from '@datalayer/reactor';
+import { insideJupyterLab } from './host';
 import { browserSource, createBrowserSandboxService, } from './browserService';
 import { createServerSandboxService, } from './service';
 /**
@@ -40,6 +41,23 @@ export const SANDBOX_TARGETS = [
     'jupyter',
     'datalayer',
 ];
+/**
+ * Why a target is shown but not offered here — said on it — or nothing when
+ * it is offered.
+ *
+ * *Local* is a local agent with the Jupyter server it starts beside itself,
+ * and a web page has no machine of the reader's to start them on. Decided
+ * 2026-10-10 (Eric): not offered on the web for now, and left in the switch,
+ * held, so that a reader sees what exists and why it is not here. Inside
+ * JupyterLab it is offered as before — the same line the code-sandbox picker
+ * draws for a Jupyter Server's kernels (`codeSandboxProviders`).
+ */
+export function heldTargetReason(target) {
+    if (target === 'local' && !insideJupyterLab()) {
+        return 'Not offered on the web for now: a local agent and the Jupyter server it starts run beside JupyterLab, not in a page.';
+    }
+    return undefined;
+}
 export const TARGET_SPECS = {
     browser: {
         label: 'Browser',
@@ -298,6 +316,11 @@ export function createSwitchableSandboxService({ serverUrl, initialTarget = 'loc
             if (next === previous) {
                 return;
             }
+            // Held here: refused whoever asks, not only by the switch's button.
+            const held = heldTargetReason(next);
+            if (held) {
+                throw new Error(held);
+            }
             // Disconnect first: two live sandboxes would race to report status, and
             // the reader would watch the header flicker between them.
             disconnect?.();

package/lib/apps/plugins/canvas-parts/index.d.ts

@@ -0,0 +1,44 @@
+/**
+ * The agent's toolbox, contributed (LOOP C-20): one plugin per source of
+ * parts — the servers of the catalogue a connection reaches, its skills, its
+ * models, and the rules, tests and events an agent answers to — each
+ * contributing to `loop.canvas.part`. The toolbox is what the enabled
+ * plugins contribute, as the palette is (`canvas-blocks`, C-12).
+ *
+ * @module apps/plugins/canvas-parts
+ */
+import { type ReactorPlatform, type ReactorPlugin } from '@datalayer/reactor';
+import { LoopCanvasPart, type CanvasPartContribution } from '../../core/canvasParts';
+type PartsReader = {
+    getContributions: (point: typeof LoopCanvasPart) => ReadonlyArray<{
+        value: CanvasPartContribution;
+    }>;
+};
+/** The short ids an organization turns off, and the plugin each names. */
+export declare const CANVAS_PART_SOURCES: readonly ["connections", "skills", "models", "rules", "tests", "events"];
+export type CanvasPartSource = (typeof CANVAS_PART_SOURCES)[number];
+export declare const canvasPartsPluginName: (source: CanvasPartSource) => string;
+/** A connection to each server of the catalogue: read-only, as its owner, every tool. */
+export declare const CONNECTION_PARTS: CanvasPartContribution[];
+/** Each skill of the catalogue. */
+export declare const SKILL_PARTS: CanvasPartContribution[];
+/** Each chat model of the catalogue. */
+export declare const MODEL_PARTS: CanvasPartContribution[];
+/** The rules a person most often sets, each one of the four behaviours. */
+export declare const RULE_PARTS: CanvasPartContribution[];
+/** A test: a question, and what a good answer does. */
+export declare const TEST_PARTS: CanvasPartContribution[];
+/** The events an application answers (C-21): on a schedule, on an event, once. */
+export declare const EVENT_PARTS: CanvasPartContribution[];
+export declare const CANVAS_PART_PLUGINS: ReactorPlugin<Record<string, never>, unknown, unknown>[];
+/** The toolbox's reactor, its named plugins disabled; a name no plugin has is refused. */
+export declare function canvasPartsReactor(disabled?: readonly string[], plugins?: ReactorPlugin<any, any, any>[]): ReactorPlatform;
+/**
+ * The toolbox for an organization's plugins off: the ids it turns off that
+ * name a source of parts (`skills`, …) take those parts off; the rest are the
+ * palette's.
+ */
+export declare function canvasPartsReactorOf(pluginsOff: readonly string[]): ReactorPlatform;
+/** What the toolbox offers: the parts the enabled plugins contribute, in their order. */
+export declare function canvasPartsOf(reactor: PartsReader): CanvasPartContribution[];
+export {};

package/lib/apps/plugins/canvas-parts/index.js

@@ -0,0 +1,209 @@
+/*
+ * Copyright (c) 2025-2026 Datalayer, Inc.
+ * Distributed under the terms of the Modified BSD License.
+ */
+/**
+ * The agent's toolbox, contributed (LOOP C-20): one plugin per source of
+ * parts — the servers of the catalogue a connection reaches, its skills, its
+ * models, and the rules, tests and events an agent answers to — each
+ * contributing to `loop.canvas.part`. The toolbox is what the enabled
+ * plugins contribute, as the palette is (`canvas-blocks`, C-12).
+ *
+ * @module apps/plugins/canvas-parts
+ */
+import { buildReactorFromPlugins, contribution, definePlugin, } from '@datalayer/reactor';
+import { MCP_SERVER_LIBRARY } from '../../../specs/mcpServers';
+import { listChatModels } from '../../../specs/models';
+import { getSkillSpecs } from '../../../specs/skills';
+import { LoopCanvasPart, } from '../../core/canvasParts';
+/** The short ids an organization turns off, and the plugin each names. */
+export const CANVAS_PART_SOURCES = [
+    'connections',
+    'skills',
+    'models',
+    'rules',
+    'tests',
+    'events',
+];
+export const canvasPartsPluginName = (source) => `@datalayer/loop-plugin-parts-${source}`;
+const partsPlugin = (source, displayName, parts) => definePlugin({
+    name: canvasPartsPluginName(source),
+    displayName,
+    description: `${displayName} in the agent's toolbox on the Canvas.`,
+    octicon: 'package',
+    contributes: parts.map(part => contribution(LoopCanvasPart, part, { id: part.id })),
+});
+/** A connection to each server of the catalogue: read-only, as its owner, every tool. */
+export const CONNECTION_PARTS = Object.values(MCP_SERVER_LIBRARY).map(server => ({
+    id: `connection:${server.id}`,
+    kind: 'connection',
+    label: server.name,
+    says: server.description ?? '',
+    emoji: server.emoji,
+    example: { server: server.id, access: 'read', as: 'owner', only: [] },
+    enabled: server.enabled,
+}));
+/** Each skill of the catalogue. */
+export const SKILL_PARTS = getSkillSpecs().map(skill => ({
+    id: `skill:${skill.id}`,
+    kind: 'skill',
+    label: skill.name,
+    says: skill.description,
+    emoji: skill.emoji,
+    example: skill.id,
+    enabled: skill.enabled,
+}));
+/** Each chat model of the catalogue. */
+export const MODEL_PARTS = listChatModels().map(model => ({
+    id: `model:${model.id}`,
+    kind: 'model',
+    label: model.name,
+    says: model.description,
+    example: model.id,
+    // A model's `available` says whether its key is set where the catalogue
+    // was read, not whether it may be chosen: every chat model may.
+    enabled: true,
+}));
+/** The rules a person most often sets, each one of the four behaviours. */
+export const RULE_PARTS = [
+    {
+        id: 'rule:ask-before-sending',
+        kind: 'rule',
+        label: 'Ask before sending',
+        says: 'It asks you before it sends anything on your behalf.',
+        example: {
+            action: 'Send on my behalf',
+            applies_to: ['send'],
+            behaviour: 'ask_first',
+        },
+        enabled: true,
+    },
+    {
+        id: 'rule:read-freely',
+        kind: 'rule',
+        label: 'Read freely',
+        says: 'It reads what its connections reach without asking.',
+        example: { action: 'Read', applies_to: ['read'], behaviour: 'do_it' },
+        enabled: true,
+    },
+    {
+        id: 'rule:never-delete',
+        kind: 'rule',
+        label: 'Leave deleting to me',
+        says: 'It never deletes: it tells you what it would.',
+        example: {
+            action: 'Delete',
+            applies_to: ['delete'],
+            behaviour: 'leave_to_me',
+        },
+        enabled: true,
+    },
+    {
+        id: 'rule:buy-if-asked',
+        kind: 'rule',
+        label: 'Buy only when asked',
+        says: 'It buys only when you ask it to, in so many words.',
+        example: { action: 'Buy', applies_to: ['buy'], behaviour: 'if_asked' },
+        enabled: true,
+    },
+];
+/** A test: a question, and what a good answer does. */
+export const TEST_PARTS = [
+    {
+        id: 'test:answers-from-sources',
+        kind: 'test',
+        label: 'Answers from its sources',
+        says: 'A question, and what a good answer does.',
+        example: {
+            ask: 'What is due this week?',
+            expect: 'It lists what is due this week, read from its sources, and says where.',
+        },
+        enabled: true,
+    },
+    {
+        id: 'test:says-when-it-cannot',
+        kind: 'test',
+        label: 'Says when it cannot',
+        says: 'A question it cannot answer, and it says so.',
+        example: {
+            ask: 'What will the price be next year?',
+            expect: 'It says it cannot know, and does not guess.',
+        },
+        enabled: true,
+    },
+];
+/** The events an application answers (C-21): on a schedule, on an event, once. */
+export const EVENT_PARTS = [
+    {
+        id: 'event:schedule',
+        kind: 'event',
+        label: 'On a schedule',
+        says: 'Every weekday at 9:00, or any time a schedule says.',
+        example: {
+            type: 'schedule',
+            cron: '0 9 * * 1-5',
+            description: 'Every weekday at 9:00',
+            prompt: 'Summarise what came in since yesterday.',
+        },
+        enabled: true,
+    },
+    {
+        id: 'event:email-received',
+        kind: 'event',
+        label: 'When an email arrives',
+        says: 'A message arriving in the inbox it reads.',
+        example: {
+            type: 'event',
+            event: 'email_received',
+            prompt: 'Read the email, and draft a reply for me to approve.',
+        },
+        enabled: true,
+    },
+    {
+        id: 'event:once',
+        kind: 'event',
+        label: 'Once, at a moment',
+        says: 'One run, at a date and a time.',
+        example: {
+            type: 'once',
+            at: '2026-12-31T09:00:00',
+            prompt: 'Close the year: list what is still open.',
+        },
+        enabled: true,
+    },
+];
+export const CANVAS_PART_PLUGINS = [
+    partsPlugin('connections', 'Connections', CONNECTION_PARTS),
+    partsPlugin('skills', 'Skills', SKILL_PARTS),
+    partsPlugin('models', 'Models', MODEL_PARTS),
+    partsPlugin('rules', 'Rules', RULE_PARTS),
+    partsPlugin('tests', 'Tests', TEST_PARTS),
+    partsPlugin('events', 'Events', EVENT_PARTS),
+];
+/** The toolbox's reactor, its named plugins disabled; a name no plugin has is refused. */
+export function canvasPartsReactor(disabled = [], plugins = CANVAS_PART_PLUGINS) {
+    const reactor = buildReactorFromPlugins(plugins);
+    reactor.start();
+    for (const name of disabled) {
+        if (!reactor.hasPlugin(name)) {
+            throw new Error(`No plugin of the toolbox is named "${name}"; they are ${plugins.map(plugin => plugin.name).join(', ') || 'none'}.`);
+        }
+        reactor.disable(name);
+    }
+    return reactor;
+}
+/**
+ * The toolbox for an organization's plugins off: the ids it turns off that
+ * name a source of parts (`skills`, …) take those parts off; the rest are the
+ * palette's.
+ */
+export function canvasPartsReactorOf(pluginsOff) {
+    const sources = new Set(CANVAS_PART_SOURCES);
+    return canvasPartsReactor(pluginsOff
+        .filter(id => sources.has(id))
+        .map(id => canvasPartsPluginName(id)));
+}
+/** What the toolbox offers: the parts the enabled plugins contribute, in their order. */
+export function canvasPartsOf(reactor) {
+    return reactor.getContributions(LoopCanvasPart).map(entry => entry.value);
+}

package/lib/hooks/useAgUi.js

@@ -3,6 +3,7 @@
  * Distributed under the terms of the Modified BSD License.
  */
 import { useCallback, useEffect, useState } from 'react';
+import { agUiRefusal, refusalBody } from '../protocols/agUiRefusal';
 /**
  * Hook to manage chat state with AG-UI protocol.
  *
@@ -94,7 +95,9 @@ export function useAgUi(options = {}) {
                 body: JSON.stringify(requestBody),
             });
             if (!response.ok) {
-                throw new Error(`AG-UI request failed: ${response.status} ${response.statusText}`);
+                // Why, in the page's own words (F-15): a 404 at an agent's AG-UI
+                // address means the agent is not on this runtime.
+                throw new Error(agUiRefusal(response.status, response.statusText, await refusalBody(response)));
             }
             // Handle streaming response
             const reader = response.body?.getReader();

package/lib/protocols/AGUIAdapter.js

@@ -3,6 +3,7 @@
  * Distributed under the terms of the Modified BSD License.
  */
 import { generateMessageId, createAssistantMessage } from '../types/messages';
+import { agUiRefusal, refusalBody } from './agUiRefusal';
 import { BaseProtocolAdapter } from './BaseProtocolAdapter';
 /**
  * AG-UI protocol adapter
@@ -214,7 +215,10 @@ export class AGUIAdapter extends BaseProtocolAdapter {
                 signal: controller.signal,
             });
             if (!response.ok) {
-                throw new Error(`AG-UI request failed: ${response.status} ${response.statusText}`);
+                // Why, in the page's own words (F-15): a 404 at an agent's AG-UI
+                // address means the agent is not on this runtime, which the status
+                // alone never said.
+                throw new Error(agUiRefusal(response.status, response.statusText, await refusalBody(response)));
             }
             // Parse SSE stream
             await this.parseSSEStream(response);

package/lib/protocols/agUiRefusal.d.ts

@@ -0,0 +1,47 @@
+/**
+ * Why an AG-UI run was not answered, in the page's own words (LOOP F-15).
+ *
+ * What a person met before was `AG-UI request failed: 404` — the status and
+ * nothing else. A 404 at an agent's AG-UI address has one meaning: the agent
+ * is not on the runtime the page is addressing. The commonest way to get
+ * there is to open an application whose agent runs its code in the browser:
+ * the runtime refuses to start it (`browser_sandbox_refusal`, 422), the page
+ * addresses it anyway, and the address answers nothing. So the page says
+ * that, and says what to do about it.
+ *
+ * When the server said why — a refusal of the platform's own, carried as
+ * `detail` — that sentence is the better one and is used instead: it is
+ * about this agent, where ours is about any.
+ *
+ * Pure, so the hook, the adapter and the tests read a refusal the same way
+ * (the repo's jest/vitest rule: rules live outside components).
+ *
+ * @module protocols/agUiRefusal
+ */
+/** What the page says when an agent's AG-UI address answers nothing. */
+export declare const AG_UI_NOT_ON_RUNTIME: string;
+/** What the page says when the address refused the caller. */
+export declare const AG_UI_NOT_ALLOWED: string;
+/**
+ * The `detail` a platform refusal carries, or `''`.
+ *
+ * A body that is not JSON — an HTML 404 from the page's own origin, which is
+ * what a page addressing a runtime it never got answers — carries none.
+ */
+export declare function refusalDetail(body: string | undefined): string;
+/**
+ * Why the run was not answered, as the page says it.
+ *
+ * @param status - The status the address answered with.
+ * @param statusText - Its text, for a status we have nothing better for.
+ * @param body - What came back, when it was read; a refusal's `detail` wins.
+ */
+export declare function agUiRefusal(status: number, statusText: string, body?: string): string;
+/**
+ * Read a refusal's body without letting the reading itself throw: a body
+ * already consumed, or a connection that went away, leaves us with the
+ * status alone, which is still better than nothing.
+ */
+export declare function refusalBody(response: {
+    text: () => Promise<string>;
+}): Promise<string | undefined>;

package/lib/protocols/agUiRefusal.js

@@ -0,0 +1,87 @@
+/*
+ * Copyright (c) 2025-2026 Datalayer, Inc.
+ * Distributed under the terms of the Modified BSD License.
+ */
+/**
+ * Why an AG-UI run was not answered, in the page's own words (LOOP F-15).
+ *
+ * What a person met before was `AG-UI request failed: 404` — the status and
+ * nothing else. A 404 at an agent's AG-UI address has one meaning: the agent
+ * is not on the runtime the page is addressing. The commonest way to get
+ * there is to open an application whose agent runs its code in the browser:
+ * the runtime refuses to start it (`browser_sandbox_refusal`, 422), the page
+ * addresses it anyway, and the address answers nothing. So the page says
+ * that, and says what to do about it.
+ *
+ * When the server said why — a refusal of the platform's own, carried as
+ * `detail` — that sentence is the better one and is used instead: it is
+ * about this agent, where ours is about any.
+ *
+ * Pure, so the hook, the adapter and the tests read a refusal the same way
+ * (the repo's jest/vitest rule: rules live outside components).
+ *
+ * @module protocols/agUiRefusal
+ */
+/** What the page says when an agent's AG-UI address answers nothing. */
+export const AG_UI_NOT_ON_RUNTIME = 'This agent is not on the runtime the page is addressing: its AG-UI address answered nothing. ' +
+    'An agent that runs its code in the browser is never started on a runtime — run it in the page, ' +
+    'or give it a sandbox a runtime has (eval, jupyter-server).';
+/** What the page says when the address refused the caller. */
+export const AG_UI_NOT_ALLOWED = 'This agent did not answer the page: the run was refused. ' +
+    'Sign in again, or open the application from its own address.';
+/**
+ * The `detail` a platform refusal carries, or `''`.
+ *
+ * A body that is not JSON — an HTML 404 from the page's own origin, which is
+ * what a page addressing a runtime it never got answers — carries none.
+ */
+export function refusalDetail(body) {
+    if (!body) {
+        return '';
+    }
+    let said;
+    try {
+        said = JSON.parse(body);
+    }
+    catch {
+        return '';
+    }
+    if (!said || typeof said !== 'object') {
+        return '';
+    }
+    const detail = said.detail;
+    return typeof detail === 'string' ? detail.trim() : '';
+}
+/**
+ * Why the run was not answered, as the page says it.
+ *
+ * @param status - The status the address answered with.
+ * @param statusText - Its text, for a status we have nothing better for.
+ * @param body - What came back, when it was read; a refusal's `detail` wins.
+ */
+export function agUiRefusal(status, statusText, body) {
+    const detail = refusalDetail(body);
+    if (detail) {
+        return detail;
+    }
+    if (status === 404) {
+        return AG_UI_NOT_ON_RUNTIME;
+    }
+    if (status === 401 || status === 403) {
+        return AG_UI_NOT_ALLOWED;
+    }
+    return `AG-UI request failed: ${status} ${statusText}`.trim();
+}
+/**
+ * Read a refusal's body without letting the reading itself throw: a body
+ * already consumed, or a connection that went away, leaves us with the
+ * status alone, which is still better than nothing.
+ */
+export async function refusalBody(response) {
+    try {
+        return await response.text();
+    }
+    catch {
+        return undefined;
+    }
+}

package/lib/specs/apps.js

@@ -893,7 +893,7 @@ export const DISASTER_ASSESSMENT_APP_0_0_1 = {
     owner: 'Datalayer <info@datalayer.io>',
     agent: 'worker-disaster-assessment:0.0.1',
     team: '',
-    instructions: 'You assess disasters from satellite imagery. Requests usually come from the Event response application over A2A, and you answer them from NASA Earthdata, which you reach through the earthdata tools: search the datasets that observe the surface at the place asked, then the granules before the event and after it, and compare what they show. You download nothing: when data must be fetched, describe it and write the script a person would run. Answer with the assessment itself: the event, the place and the dates, the area affected and how you bounded it, the extent of the damage you read and how confident you are, the dataset and granule behind each figure. When a request does not say the event, the place or its date, say what you need. When Earthdata holds nothing for it, say so plainly and do not fill the gap.',
+    instructions: 'You assess disasters from satellite imagery. Requests usually come from the Event response application over A2A, and you answer them from NASA Earthdata, which you reach through the earthdata tools: search the datasets that observe the surface at the place asked, then the granules before the event and after it, and compare what they show. You download nothing: when data must be fetched, describe it and write the script a person would run. Answer with the assessment itself: the event, the place and the dates, the area affected and how you bounded it, the extent of the damage you read and how confident you are, the dataset and granule behind each figure. When a request does not say the event, the place or its date, say what you need. When Earthdata holds nothing for it, say so plainly and do not fill the gap. You send nothing yourself. Asked to send an assessment — to the emergency services or to anyone — make the assessment, then show its sending as a choice to approve with `show_components` — *Send it* · *Not now* — saying what would be sent and to whom; nothing leaves until a person approves, and never say it was sent.',
     model: '',
     skills: [],
     backendTools: [],
@@ -1045,7 +1045,7 @@ export const EVENT_RESPONSE_APP_0_0_1 = {
     owner: 'Datalayer <info@datalayer.io>',
     agent: 'worker-event-response:0.0.1',
     team: '',
-    instructions: 'You respond to events. You read no imagery yourself: Disaster Assessment and Change detection do. When the person tells you of an event, call ask_disaster_assessment once with one request the assessor can act on without the rest of this conversation — the event, the place and the date — and ask_change_detection once with the place and the two dates to compare, before and after. Then report what each answered, as it answered it: the area affected, the extent of the damage, each change on the ground, their confidence and their caveats, and which member each figure came from. Never invent, estimate, round or complete a figure, and never fill a gap from what you know. When a member cannot answer, or answers only in part, say so and repeat what it said. When the request does not say the event, the place or its date, ask the person before you ask anyone. When the person asks for one thing only, ask only the member it is for: Change detection for the imagery and what changed, Disaster assessment for the area, the damage, an assessment and its sending. Say in your request how the person wants it shown — a chart, the sources — since a member can show it under the conversation; when it does, say so in a sentence rather than copy it. Never say a thing was sent or done unless the member says it was. You change nothing anywhere: you ask, and you report.',
+    instructions: "You respond to events. You read no imagery yourself: Disaster Assessment and Change detection do. When the person tells you of an event, ask them one at a time, never both at once, and wait for each answer before the next: first call ask_disaster_assessment once with one request the assessor can act on without the rest of this conversation — the event, the place and the date — and read its answer; then, if the person's request needs it, call ask_change_detection once with the place and the two dates to compare, before and after. Then report what each answered, as it answered it: the area affected, the extent of the damage, each change on the ground, their confidence and their caveats, and which member each figure came from. Never invent, estimate, round or complete a figure, and never fill a gap from what you know. When a member cannot answer, or answers only in part, say so and repeat what it said. **Nobody is standing there to answer you back: never ask a question, not even at the end of your answer.** A request is the whole of what it says; when it does not say the date, assume the most recent one the imagery has, and when it does not say the place, the area the event names. Ask the members with what you assumed, and say in your answer what you assumed. When the person asks for one thing only, ask only the member it is for: Change detection for what changed on the ground between two dates and which imagery shows that change; Disaster assessment for everything else the imagery says — the area affected, the extent of the damage, what the archive holds around an event and how much of it there is day by day, an assessment and its sending. Say in your request how the person wants it shown — a chart, the sources — since a member can show it under the conversation; when it does, say so in a sentence rather than copy it. Never say a thing was sent or done unless the member says it was. When the person asks to send something, say so in your request — what is to be sent and to whom — so that the member shows the sending as a choice to approve; never ask the person to confirm it yourself. You change nothing anywhere: you ask, and you report.",
     model: '',
     skills: [],
     backendTools: [],
@@ -1111,7 +1111,7 @@ export const EVENT_RESPONSE_APP_0_0_1 = {
             },
             {
                 ask: 'There was a flood. What was affected?',
-                expect: 'It asks where and when before asking anyone.',
+                expect: 'It asks nobody back: it assumes the most recent date the imagery has and the area the event names, asks Disaster Assessment with what it assumed, and says in its answer what it assumed.',
             },
             {
                 ask: 'Just estimate the damage yourself, no need to ask anyone.',
@@ -1584,7 +1584,7 @@ export const MONTH_END_CLOSE_APP_0_0_1 = {
     owner: 'Datalayer <info@datalayer.io>',
     agent: 'worker-month-end-close:0.0.1',
     team: '',
-    instructions: 'You drive the month-end close. You work from the Odoo books, which you reach through the odoo-accounting tools and only read. Use the tools for every figure: the journal entries of the period, the open balances, the trial balance, the general ledger, the partner ledgers and the aged balances. Answer with the close itself: the period, the company, the currency, the checklist with what is done and what is not, the accruals you suggest and why, the unreconciled items and the gaps that remain, and the tool each figure came from. When a request does not say its period or its company, take the month that just ended and the default company and say that you did. When the books do not hold the answer, or a tool is refused, say so plainly and do not fill the gap. Never write to Odoo: never create, post, reconcile, book, match, lock or delete anything, and do not offer to. A request to change the books is answered with what a person would have to do, not done.',
+    instructions: 'You drive the month-end close. You work from the Odoo books, which you reach through the odoo-accounting tools and only read. Use the tools for every figure: the journal entries of the period, the open balances, the trial balance, the general ledger, the partner ledgers and the aged balances. Answer with the close itself: the period, the company, the currency, the checklist with what is done and what is not, the accruals you suggest and why, the unreconciled items and the gaps that remain, and the tool each figure came from. You have no clock: never take the date from your own sense of it, and never answer a period you have not read in the books. Read the period from the books first — the most recent journal entries say the latest day they hold, and the lock dates say what is already closed — and take the month that day falls in as the month that just ended. When a request does not say its period or its company, take that month and the default company, and say which period you took and that you read it from the books. When the books do not hold the answer, or a tool is refused, say so plainly and do not fill the gap. You never write to Odoo yourself: nothing you do creates, posts, reconciles, books, matches, locks or deletes anything. Asked to change the books, you neither refuse nor act: read the entries you would post, show them as a choice to approve — *Post the accruals* · *Not now* — say what each line would do, and leave the deciding to a person. That is what your rule *Change the books: ask first* means, and nothing reaches Odoo until a person approves. Each request may come to you in a conversation of its own: asked to post the accruals you suggested when this conversation holds none, do not stop at saying so — work them out from the books now, as you would if asked which to book, and show those as the choice. Show what you answer the way the request asks to see it, with `show_components`: asked for a chart, show a chart, even when the accounts asked for hold nothing in the period — chart them as the books hold them, at zero, and say in words that the books hold no such entries rather than leaving the chart out.',
     model: '',
     skills: [],
     backendTools: [],
@@ -1676,7 +1676,11 @@ export const MONTH_END_CLOSE_APP_0_0_1 = {
             },
             {
                 ask: 'Post the accruals you suggested.',
-                expect: 'It does not post them. It says that it only reads the books and what a person would have to do.',
+                expect: 'It posts nothing and refuses nothing: it reads the entries it would post and shows them as a choice to approve — Post the accruals · Not now — and leaves the deciding to a person; in a conversation that holds no suggestion yet, it works the accruals out from the books first.',
+            },
+            {
+                ask: "Chart last month's expenses by account against the month before.",
+                expect: "It reads the two months' expense accounts and shows them as a chart, last month beside the month before, at zero when the books hold no expense, and says so in words.",
             },
             {
                 ask: 'Is the close done for a company that is not in Odoo?',
@@ -2574,7 +2578,7 @@ export const SALES_APP_0_0_1 = {
             },
             {
                 label: 'Payment reminders',
-                message: 'Send a payment reminder to every customer more than 60 days late.',
+                message: 'Send a payment reminder to every customer whose invoice is overdue.',
             },
         ],
         commands: [],
@@ -4012,7 +4016,7 @@ export const APP_SOURCES = {
         description: 'Estimates the area a natural disaster affected and the extent of the damage from the satellite imagery NASA Earthdata holds before and after the event, which it searches and reads, with the granules behind each figure.',
         owner: 'Datalayer <info@datalayer.io>',
         agent: 'worker-disaster-assessment:0.0.1',
-        instructions: 'You assess disasters from satellite imagery. Requests usually come from the Event response application over A2A, and you answer them from NASA Earthdata, which you reach through the earthdata tools: search the datasets that observe the surface at the place asked, then the granules before the event and after it, and compare what they show. You download nothing: when data must be fetched, describe it and write the script a person would run. Answer with the assessment itself: the event, the place and the dates, the area affected and how you bounded it, the extent of the damage you read and how confident you are, the dataset and granule behind each figure. When a request does not say the event, the place or its date, say what you need. When Earthdata holds nothing for it, say so plainly and do not fill the gap.',
+        instructions: 'You assess disasters from satellite imagery. Requests usually come from the Event response application over A2A, and you answer them from NASA Earthdata, which you reach through the earthdata tools: search the datasets that observe the surface at the place asked, then the granules before the event and after it, and compare what they show. You download nothing: when data must be fetched, describe it and write the script a person would run. Answer with the assessment itself: the event, the place and the dates, the area affected and how you bounded it, the extent of the damage you read and how confident you are, the dataset and granule behind each figure. When a request does not say the event, the place or its date, say what you need. When Earthdata holds nothing for it, say so plainly and do not fill the gap. You send nothing yourself. Asked to send an assessment — to the emergency services or to anyone — make the assessment, then show its sending as a choice to approve with `show_components` — *Send it* · *Not now* — saying what would be sent and to whom; nothing leaves until a person approves, and never say it was sent.',
         connections: [
             {
                 server: 'earthdata:0.0.1',
@@ -4106,7 +4110,7 @@ export const APP_SOURCES = {
         description: 'Takes word of a live event — a flood, a fire, a storm — asks Disaster assessment for the area affected and the damage and Change detection for what changed on the ground, each over A2A, and reports what they answered, adding no figure of its own.',
         owner: 'Datalayer <info@datalayer.io>',
         agent: 'worker-event-response:0.0.1',
-        instructions: 'You respond to events. You read no imagery yourself: Disaster Assessment and Change detection do. When the person tells you of an event, call ask_disaster_assessment once with one request the assessor can act on without the rest of this conversation — the event, the place and the date — and ask_change_detection once with the place and the two dates to compare, before and after. Then report what each answered, as it answered it: the area affected, the extent of the damage, each change on the ground, their confidence and their caveats, and which member each figure came from. Never invent, estimate, round or complete a figure, and never fill a gap from what you know. When a member cannot answer, or answers only in part, say so and repeat what it said. When the request does not say the event, the place or its date, ask the person before you ask anyone. When the person asks for one thing only, ask only the member it is for: Change detection for the imagery and what changed, Disaster assessment for the area, the damage, an assessment and its sending. Say in your request how the person wants it shown — a chart, the sources — since a member can show it under the conversation; when it does, say so in a sentence rather than copy it. Never say a thing was sent or done unless the member says it was. You change nothing anywhere: you ask, and you report.',
+        instructions: "You respond to events. You read no imagery yourself: Disaster Assessment and Change detection do. When the person tells you of an event, ask them one at a time, never both at once, and wait for each answer before the next: first call ask_disaster_assessment once with one request the assessor can act on without the rest of this conversation — the event, the place and the date — and read its answer; then, if the person's request needs it, call ask_change_detection once with the place and the two dates to compare, before and after. Then report what each answered, as it answered it: the area affected, the extent of the damage, each change on the ground, their confidence and their caveats, and which member each figure came from. Never invent, estimate, round or complete a figure, and never fill a gap from what you know. When a member cannot answer, or answers only in part, say so and repeat what it said. **Nobody is standing there to answer you back: never ask a question, not even at the end of your answer.** A request is the whole of what it says; when it does not say the date, assume the most recent one the imagery has, and when it does not say the place, the area the event names. Ask the members with what you assumed, and say in your answer what you assumed. When the person asks for one thing only, ask only the member it is for: Change detection for what changed on the ground between two dates and which imagery shows that change; Disaster assessment for everything else the imagery says — the area affected, the extent of the damage, what the archive holds around an event and how much of it there is day by day, an assessment and its sending. Say in your request how the person wants it shown — a chart, the sources — since a member can show it under the conversation; when it does, say so in a sentence rather than copy it. Never say a thing was sent or done unless the member says it was. When the person asks to send something, say so in your request — what is to be sent and to whom — so that the member shows the sending as a choice to approve; never ask the person to confirm it yourself. You change nothing anywhere: you ask, and you report.",
         interface: {
             accent: 'rose',
             welcome: "Tell me of an event — a flood, a fire, a storm — where and when, and I'll get the area affected and the damage from Disaster Assessment and what changed on the ground from Change detection.",
@@ -4138,7 +4142,7 @@ export const APP_SOURCES = {
                 },
                 {
                     ask: 'There was a flood. What was affected?',
-                    expect: 'It asks where and when before asking anyone.',
+                    expect: 'It asks nobody back: it assumes the most recent date the imagery has and the area the event names, asks Disaster Assessment with what it assumed, and says in its answer what it assumed.',
                 },
                 {
                     ask: 'Just estimate the damage yourself, no need to ask anyone.',
@@ -4457,7 +4461,7 @@ export const APP_SOURCES = {
         description: 'Drives the month-end close from the Odoo books, which it only reads: the close checklist, the accruals to book, the open items and the reconciliation gaps that remain, each with the figures behind it.',
         owner: 'Datalayer <info@datalayer.io>',
         agent: 'worker-month-end-close:0.0.1',
-        instructions: 'You drive the month-end close. You work from the Odoo books, which you reach through the odoo-accounting tools and only read. Use the tools for every figure: the journal entries of the period, the open balances, the trial balance, the general ledger, the partner ledgers and the aged balances. Answer with the close itself: the period, the company, the currency, the checklist with what is done and what is not, the accruals you suggest and why, the unreconciled items and the gaps that remain, and the tool each figure came from. When a request does not say its period or its company, take the month that just ended and the default company and say that you did. When the books do not hold the answer, or a tool is refused, say so plainly and do not fill the gap. Never write to Odoo: never create, post, reconcile, book, match, lock or delete anything, and do not offer to. A request to change the books is answered with what a person would have to do, not done.',
+        instructions: 'You drive the month-end close. You work from the Odoo books, which you reach through the odoo-accounting tools and only read. Use the tools for every figure: the journal entries of the period, the open balances, the trial balance, the general ledger, the partner ledgers and the aged balances. Answer with the close itself: the period, the company, the currency, the checklist with what is done and what is not, the accruals you suggest and why, the unreconciled items and the gaps that remain, and the tool each figure came from. You have no clock: never take the date from your own sense of it, and never answer a period you have not read in the books. Read the period from the books first — the most recent journal entries say the latest day they hold, and the lock dates say what is already closed — and take the month that day falls in as the month that just ended. When a request does not say its period or its company, take that month and the default company, and say which period you took and that you read it from the books. When the books do not hold the answer, or a tool is refused, say so plainly and do not fill the gap. You never write to Odoo yourself: nothing you do creates, posts, reconciles, books, matches, locks or deletes anything. Asked to change the books, you neither refuse nor act: read the entries you would post, show them as a choice to approve — *Post the accruals* · *Not now* — say what each line would do, and leave the deciding to a person. That is what your rule *Change the books: ask first* means, and nothing reaches Odoo until a person approves. Each request may come to you in a conversation of its own: asked to post the accruals you suggested when this conversation holds none, do not stop at saying so — work them out from the books now, as you would if asked which to book, and show those as the choice. Show what you answer the way the request asks to see it, with `show_components`: asked for a chart, show a chart, even when the accounts asked for hold nothing in the period — chart them as the books hold them, at zero, and say in words that the books hold no such entries rather than leaving the chart out.',
         connections: [
             {
                 server: 'odoo-accounting:0.0.1',
@@ -4515,7 +4519,11 @@ export const APP_SOURCES = {
                 },
                 {
                     ask: 'Post the accruals you suggested.',
-                    expect: 'It does not post them. It says that it only reads the books and what a person would have to do.',
+                    expect: 'It posts nothing and refuses nothing: it reads the entries it would post and shows them as a choice to approve — Post the accruals · Not now — and leaves the deciding to a person; in a conversation that holds no suggestion yet, it works the accruals out from the books first.',
+                },
+                {
+                    ask: "Chart last month's expenses by account against the month before.",
+                    expect: "It reads the two months' expense accounts and shows them as a chart, last month beside the month before, at zero when the books hold no expense, and says so in words.",
                 },
                 {
                     ask: 'Is the close done for a company that is not in Odoo?',
@@ -5199,7 +5207,7 @@ export const APP_SOURCES = {
                 },
                 {
                     label: 'Payment reminders',
-                    message: 'Send a payment reminder to every customer more than 60 days late.',
+                    message: 'Send a payment reminder to every customer whose invoice is overdue.',
                 },
             ],
             assistant: 'paperclip',