orbitx 0.3.0 → 0.3.2

package/dist/skills/shopping.js

@@ -1,71 +0,0 @@
-import Skill from "../core/skill.js";
-import { BrowserTools } from "../tools/browser/index.js";
-import { UtilTools } from "../tools/utils/index.js";
-export const ShoppingSkill = () => new Skill({
-    name: "shopping",
-    description: "Use this skill whenever the user wants help choosing, comparing, or buying a product — 'what's the best X', 'help me find a Y', 'is this a good deal', 'which should I buy', or a request for a specific product recommendation. Drives a real browser to find actual current listings, actual prices, actual direct links, and actual reviews — never recommends from memory or general reputation alone, since prices, models, and availability change constantly. Covers finding and comparing multiple competing options (not just one), surfacing real customer review sentiment (including scrolling to load reviews sections that don't render on initial page load), and giving the user a direct link and price for anything recommended. Trigger this for purchase-decision questions specifically; for general product knowledge questions with no purchase intent ('how does a HEPA filter work'), this skill isn't needed.",
-    tools: [
-        ...BrowserTools(),
-        ...UtilTools()
-    ],
-    instructions: `
-# Shopping Skill
-
-## Mindset
-Product recommendations go stale immediately — prices change daily, models get discontinued, "best" lists from training data are often already wrong by the time they're read back. Never recommend a specific product from memory or general brand reputation alone. Every specific product named in a shopping answer needs: a real, currently-open listing, a real current price, a real direct link, and — where the decision is non-trivial — real review evidence actually read from the page, not inferred from the product's category or brand alone.
-
-The job is not "name a good product." The job is "help the user actually buy the right thing" — which means giving them a link they can click, a price they can trust as current, and enough comparative context (competitors, review sentiment, actual tradeoffs) that they're not making the decision on vibes.
-
-## Core loop
-1. Open a browser session (DuckDuckGo or Bing as entry point — not Google, same reasoning as the research skill: it blocks headless browsers). If the user named a specific retailer/site, go straight there instead.
-2. Search for the product category, read the results outline, and open several promising, genuinely different listings — not five results from the same retailer, and not just the first result.
-3. On each listing page, actually read: the current price, the product's real name/model, and whether it's in stock — don't report a price you haven't actually seen rendered on the page in this session, since cached/remembered prices are routinely wrong.
-4. Get the actual review section loaded and read (see "Reviews" below) rather than trusting a star rating alone.
-5. Repeat for at least 2–3 genuinely competing products before making a recommendation — see "Never recommend just one option" below.
-6. Present the comparison with direct links and current prices for everything named.
-
-## Never recommend just one option
-A shopping answer that names a single product with no comparison is not doing the job, even if that product happens to be great. Unless the user has already narrowed to one specific item and just wants a check on it, always surface competitors:
-- Open listings for at least 2–3 realistic alternatives in the same category/price band, not just variations of the same brand.
-- Compare on the dimensions that actually matter for the category (price, key specs, review sentiment, warranty/return policy) rather than an arbitrary feature list.
-- Be explicit about tradeoffs — "A is cheaper but has weaker reviews on durability; B costs more but consistently gets praised for X" — rather than a flat ranked list with no reasoning shown.
-- If the user's ask is narrow ("is this specific product good") rather than "what should I buy," you can lead with a direct answer about that product, but still mention how it stacks up against its obvious alternatives rather than evaluating it in isolation.
-
-## Prices and links — accuracy is the whole point
-- Every price quoted must be one you actually observed rendered on the page during this session. Prices from memory, from a search snippet alone, or extrapolated from an old listing are not acceptable — retailers change prices constantly and a stale number actively misleads a purchase decision.
-- Always give the user the actual URL you found the listing at, not a guessed or reconstructed URL — only link to pages you actually opened and read in this session (never fabricate a plausible-looking product URL).
-- Note the currency and, if relevant to the user's likely location, flag if a price appears to be in a different currency/region than expected.
-- If a price shown seems to be a temporary sale/limited-time deal, say so — don't present a flash-sale price as the item's normal price.
-- If stock status is visible (in stock / limited stock / out of stock / backordered), report it — a great deal on an out-of-stock item isn't actionable.
-- If prices differ noticeably across retailers for what's genuinely the same item, surface the cheapest legitimate option rather than defaulting to whichever site you happened to open first.
-
-## Reviews — read them, don't infer them
-A star rating alone is weak evidence — 4.2 stars can mean "consistently solid" or "half the reviews say it broke in a month and half say it's great," and those are very different signals for a buyer. Actually read review content:
-- **Reviews sections often don't render on initial page load.** Many e-commerce and retailer sites lazy-load the reviews section only once it's scrolled into view, or require clicking a "Reviews" tab/anchor link separately from the main product description. If you read a page and don't see review text (even though a star rating and review count are shown near the top), don't conclude there are no reviews — check whether there's a "Reviews" tab/link to click, and if the page is long, scroll down toward where a review count was shown and re-read, since that section may only populate once it's in view. This is a common trap: an agent that reads only the top of the page and reports "no reviews shown" when reviews exist further down or behind a tab is giving a false negative.
-- After getting the reviews section to actually load, read a real sample — not just the single top-featured/most-helpful review, which retailers sometimes curate. Skim across several individual reviews, and specifically look at a mix of high and low ratings to catch recurring complaints that a single glowing top review would hide.
-- Look for *recurring* specific complaints or praise across multiple reviewers (e.g. several independent reviewers mentioning the same durability issue, or the same standout feature) rather than treating one person's review as representative.
-- If a retailer's on-page reviews look thin, curated, or suspiciously uniform (all 5-star, generic phrasing, no verified-purchase indication), treat that as lower-confidence evidence and consider checking a second, independent source (a different retailer's listing for the same product, or a review-aggregation/comparison site) rather than relying solely on the first one seen.
-- Report review sentiment honestly, including negatives — "mostly positive, but a recurring complaint about X" is more useful and more trustworthy than an uncritical "highly rated" gloss that ignores visible negative signal on the same page.
-
-## Handling pages that need extra interaction to show what you need
-Beyond reviews specifically, several other common shopping-page patterns require action before the real content is visible:
-- **"Show more" / "See all specs" buttons** that collapse full specifications by default — click through rather than reporting only the abbreviated spec list.
-- **Variant selectors** (size, color, storage capacity) that change the displayed price/stock/images when selected — if the user cares about a specific variant, actually select it and re-read rather than reporting the default variant's price as if it applies to all.
-- **Comparison tables** on some retailer sites that require selecting products into a "compare" tray before the table renders — worth doing if the user is choosing between options on the same site.
-- **Pagination or "load more" on review lists** — if you want a broader review sample than the first page shows, page/load further rather than judging sentiment from only the first handful.
-- After any of these interactions, re-read the page — refs and rendered content are stale the moment an interaction changes the DOM, same as any other browser-driven task.
-
-## Handling obstacles
-- Bot checks, CAPTCHAs, or hard login walls on a retailer page: don't fight them — abandon that listing and check the same product on a different retailer.
-- If a retailer's page is slow/JS-heavy and content (price, reviews) looks like it hasn't finished loading, wait briefly and re-check rather than reading a half-loaded page as final — same discipline as the research skill.
-- If you genuinely can't get a real current price or working link for something after reasonable effort, say so plainly rather than presenting a stale or guessed price with unwarranted confidence.
-
-## What a finished shopping answer looks like
-- At least 2–3 real, comparable options (unless the user asked about one specific item) with current prices and direct links to what you actually opened.
-- Honest review sentiment for each, based on actually-read review content — including scrolling/clicking through to reach reviews that weren't visible on first load — not just a star-rating gloss.
-- Clear tradeoffs stated between the options, not just a ranked list with no reasoning.
-- Explicit notes on anything time-sensitive (a sale price, limited stock) so the user knows the information's shelf life.
-`
-});
-export default ShoppingSkill;
-//# sourceMappingURL=shopping.js.map

package/dist/skills/shopping.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"shopping.js","sourceRoot":"","sources":["../../src/skills/shopping.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,MAAM,kBAAkB,CAAC;AACrC,OAAO,EAAE,YAAY,EAAE,MAAM,2BAA2B,CAAC;AACzD,OAAO,EAAE,SAAS,EAAE,MAAM,yBAAyB,CAAC;AAEpD,MAAM,CAAC,MAAM,aAAa,GAAG,GAAG,EAAE,CAAC,IAAI,KAAK,CAAC;IACzC,IAAI,EAAE,UAAU;IAChB,WAAW,EAAE,y4BAAy4B;IACt5B,KAAK,EAAE;QACH,GAAG,YAAY,EAAE;QACjB,GAAG,SAAS,EAAE;KACjB;IACD,YAAY,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyDjB;CACA,CAAC,CAAC;AAEH,eAAe,aAAa,CAAC"}

package/dist/tools/agent/interaction.d.ts

@@ -1,25 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-export type AgentEvent = {
-    type: "hired";
-    name: string;
-} | {
-    type: "prompted";
-    name: string;
-    prompt: string;
-} | {
-    type: "reported";
-    name: string;
-    reported: boolean;
-    report: string;
-};
-/**
- * Shared custom interaction class for the agent-management tools. A
- * frontend can listen on getEvents() to show live status (e.g. "Hiring
- * backend-worker...", "backend-worker is working...") while the planner
- * hires and prompts worker agents.
- */
-export declare class AgentInteraction extends MCPCustomClass {
-    emitAgentEvent(event: AgentEvent): void;
-}
-export default AgentInteraction;
-//# sourceMappingURL=interaction.d.ts.map

package/dist/tools/agent/interaction.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.d.ts","sourceRoot":"","sources":["../../../src/tools/agent/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAEnD,MAAM,MAAM,UAAU,GAChB;IAAE,IAAI,EAAE,OAAO,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GAC/B;IAAE,IAAI,EAAE,UAAU,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,GAClD;IAAE,IAAI,EAAE,UAAU,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,OAAO,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,CAAC;AAE5E;;;;;GAKG;AACH,qBAAa,gBAAiB,SAAQ,cAAc;IAChD,cAAc,CAAC,KAAK,EAAE,UAAU;CAGnC;AAED,eAAe,gBAAgB,CAAC"}

package/dist/tools/agent/interaction.js

@@ -1,14 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-/**
- * Shared custom interaction class for the agent-management tools. A
- * frontend can listen on getEvents() to show live status (e.g. "Hiring
- * backend-worker...", "backend-worker is working...") while the planner
- * hires and prompts worker agents.
- */
-export class AgentInteraction extends MCPCustomClass {
-    emitAgentEvent(event) {
-        this.getEvents().emit("agent", event);
-    }
-}
-export default AgentInteraction;
-//# sourceMappingURL=interaction.js.map

package/dist/tools/agent/interaction.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.js","sourceRoot":"","sources":["../../../src/tools/agent/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAOnD;;;;;GAKG;AACH,MAAM,OAAO,gBAAiB,SAAQ,cAAc;IAChD,cAAc,CAAC,KAAiB;QAC5B,IAAI,CAAC,SAAS,EAAE,CAAC,IAAI,CAAC,OAAO,EAAE,KAAK,CAAC,CAAC;IAC1C,CAAC;CACJ;AAED,eAAe,gBAAgB,CAAC"}

package/dist/tools/agent/list.d.ts

@@ -1,5 +0,0 @@
-import { MCPTool } from "../../core/mcp.js";
-import type AgentRegistry from "./registry.js";
-export declare const AgentListTool: (registry: AgentRegistry) => MCPTool;
-export default AgentListTool;
-//# sourceMappingURL=list.d.ts.map

package/dist/tools/agent/list.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"list.d.ts","sourceRoot":"","sources":["../../../src/tools/agent/list.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,mBAAmB,CAAC;AAC5C,OAAO,KAAK,aAAa,MAAM,eAAe,CAAC;AAE/C,eAAO,MAAM,aAAa,GAAI,UAAU,aAAa,YAYnD,CAAC;AAEH,eAAe,aAAa,CAAC"}

package/dist/tools/agent/list.js

@@ -1,16 +0,0 @@
-import { MCPTool } from "../../core/mcp.js";
-export const AgentListTool = (registry) => new MCPTool({
-    name: "agent-list",
-    description: "list every worker agent available to hire, with their name, description/persona, per-task-type rating, and whether they're already hired. Check this before hiring — pick whichever agent's rating best fits the task at hand, and check hiredCount against maxHired if there's a hiring limit.",
-    inputs: [],
-    execute: async () => {
-        const maxHired = registry.getMaxHired();
-        return {
-            agents: registry.list(),
-            hiredCount: registry.getHiredCount(),
-            ...(maxHired !== undefined ? { maxHired } : {}),
-        };
-    },
-});
-export default AgentListTool;
-//# sourceMappingURL=list.js.map

package/dist/tools/agent/list.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"list.js","sourceRoot":"","sources":["../../../src/tools/agent/list.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,mBAAmB,CAAC;AAG5C,MAAM,CAAC,MAAM,aAAa,GAAG,CAAC,QAAuB,EAAE,EAAE,CAAC,IAAI,OAAO,CAAC;IAClE,IAAI,EAAE,YAAY;IAClB,WAAW,EAAE,iSAAiS;IAC9S,MAAM,EAAE,EAAE;IACV,OAAO,EAAE,KAAK,IAAkB,EAAE;QAC9B,MAAM,QAAQ,GAAG,QAAQ,CAAC,WAAW,EAAE,CAAC;QACxC,OAAO;YACH,MAAM,EAAE,QAAQ,CAAC,IAAI,EAAE;YACvB,UAAU,EAAE,QAAQ,CAAC,aAAa,EAAE;YACpC,GAAG,CAAC,QAAQ,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,QAAQ,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;SAClD,CAAC;IACN,CAAC;CACJ,CAAC,CAAC;AAEH,eAAe,aAAa,CAAC"}

package/dist/tools/agent/report.d.ts

@@ -1,12 +0,0 @@
-import { MCPTool } from "../../core/mcp.js";
-/**
- * For WorkerAgents, not planners: include this in a worker's own
- * `allowedTools` (and register it on whatever MCPServer that worker uses)
- * so it can hand a result back to whoever hired and prompted it. Calling
- * this always ends the worker's current turn immediately
- * (stopIterationAfterUsingThisTool) — AgentPromptTool picks the reported
- * text back up on the hiring agent's side once agent.run() resolves.
- */
-export declare const AgentReportTool: () => MCPTool;
-export default AgentReportTool;
-//# sourceMappingURL=report.d.ts.map

package/dist/tools/agent/report.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"report.d.ts","sourceRoot":"","sources":["../../../src/tools/agent/report.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,mBAAmB,CAAC;AAE5C;;;;;;;GAOG;AACH,eAAO,MAAM,eAAe,eAqB1B,CAAC;AAEH,eAAe,eAAe,CAAC"}

package/dist/tools/agent/report.js

@@ -1,31 +0,0 @@
-import { MCPTool } from "../../core/mcp.js";
-/**
- * For WorkerAgents, not planners: include this in a worker's own
- * `allowedTools` (and register it on whatever MCPServer that worker uses)
- * so it can hand a result back to whoever hired and prompted it. Calling
- * this always ends the worker's current turn immediately
- * (stopIterationAfterUsingThisTool) — AgentPromptTool picks the reported
- * text back up on the hiring agent's side once agent.run() resolves.
- */
-export const AgentReportTool = () => new MCPTool({
-    name: "agent-report",
-    description: "report your result back to whichever agent hired and prompted you, then stop. This ends your current turn immediately — do not call any other tool or add commentary after this. The hiring agent decides what happens next: it may prompt you again to continue this same task, or move on and not call you again if your report shows you're done.",
-    inputs: [
-        {
-            name: "report",
-            type: "string",
-            description: "the result/findings/answer to hand back — write it so it's understandable on its own, without the hiring agent needing to see your internal reasoning",
-            required: true,
-        },
-    ],
-    stopIterationAfterUsingThisTool: true,
-    execute: async (_envID, inputs) => {
-        const { report } = inputs;
-        if (!report || typeof report !== "string") {
-            throw new Error("report must be a non-empty string");
-        }
-        return { report };
-    },
-});
-export default AgentReportTool;
-//# sourceMappingURL=report.js.map

package/dist/tools/agent/report.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"report.js","sourceRoot":"","sources":["../../../src/tools/agent/report.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,mBAAmB,CAAC;AAE5C;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG,GAAG,EAAE,CAAC,IAAI,OAAO,CAAC;IAC7C,IAAI,EAAE,cAAc;IACpB,WAAW,EAAE,sVAAsV;IACnW,MAAM,EAAE;QACJ;YACI,IAAI,EAAE,QAAQ;YACd,IAAI,EAAE,QAAQ;YACd,WAAW,EAAE,uJAAuJ;YACpK,QAAQ,EAAE,IAAI;SACjB;KACJ;IACD,+BAA+B,EAAE,IAAI;IACrC,OAAO,EAAE,KAAK,EAAE,MAAc,EAAE,MAA2B,EAAgB,EAAE;QACzE,MAAM,EAAE,MAAM,EAAE,GAAG,MAAM,CAAC;QAE1B,IAAI,CAAC,MAAM,IAAI,OAAO,MAAM,KAAK,QAAQ,EAAE,CAAC;YACxC,MAAM,IAAI,KAAK,CAAC,mCAAmC,CAAC,CAAC;QACzD,CAAC;QAED,OAAO,EAAE,MAAM,EAAE,CAAC;IACtB,CAAC;CACJ,CAAC,CAAC;AAEH,eAAe,eAAe,CAAC"}

package/dist/tools/bash/interaction.d.ts

@@ -1,29 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-export type BashEvent = {
-    type: "process-started";
-    processId: string;
-    command: string;
-} | {
-    type: "waiting";
-    processId: string;
-} | {
-    type: "input-sent";
-    processId: string;
-} | {
-    type: "terminated";
-    processId: string;
-} | {
-    type: "process-exited";
-    processId: string;
-    exitCode: number | null;
-};
-/**
- * Shared custom interaction class for all bash tools. A frontend can listen
- * on getEvents() to reflect live process activity (e.g. "Running npm run
- * dev...", "Waiting for build to finish...") without polling.
- */
-export declare class BashInteraction extends MCPCustomClass {
-    emitBashEvent(event: BashEvent): void;
-}
-export default BashInteraction;
-//# sourceMappingURL=interaction.d.ts.map

package/dist/tools/bash/interaction.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.d.ts","sourceRoot":"","sources":["../../../src/tools/bash/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAEnD,MAAM,MAAM,SAAS,GACf;IAAE,IAAI,EAAE,iBAAiB,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,GAC/D;IAAE,IAAI,EAAE,SAAS,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,GACtC;IAAE,IAAI,EAAE,YAAY,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,GACzC;IAAE,IAAI,EAAE,YAAY,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,GACzC;IAAE,IAAI,EAAE,gBAAgB,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAA;CAAE,CAAC;AAE7E;;;;GAIG;AACH,qBAAa,eAAgB,SAAQ,cAAc;IAC/C,aAAa,CAAC,KAAK,EAAE,SAAS;CAGjC;AAED,eAAe,eAAe,CAAC"}

package/dist/tools/bash/interaction.js

@@ -1,13 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-/**
- * Shared custom interaction class for all bash tools. A frontend can listen
- * on getEvents() to reflect live process activity (e.g. "Running npm run
- * dev...", "Waiting for build to finish...") without polling.
- */
-export class BashInteraction extends MCPCustomClass {
-    emitBashEvent(event) {
-        this.getEvents().emit("bash", event);
-    }
-}
-export default BashInteraction;
-//# sourceMappingURL=interaction.js.map

package/dist/tools/bash/interaction.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.js","sourceRoot":"","sources":["../../../src/tools/bash/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AASnD;;;;GAIG;AACH,MAAM,OAAO,eAAgB,SAAQ,cAAc;IAC/C,aAAa,CAAC,KAAgB;QAC1B,IAAI,CAAC,SAAS,EAAE,CAAC,IAAI,CAAC,MAAM,EAAE,KAAK,CAAC,CAAC;IACzC,CAAC;CACJ;AAED,eAAe,eAAe,CAAC"}

package/dist/tools/browser/interaction.d.ts

@@ -1,49 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-export type BrowserEvent = {
-    type: "session-created";
-    sessionId: string;
-    url: string;
-} | {
-    type: "session-removed";
-    sessionId: string;
-} | {
-    type: "navigating";
-    sessionId: string;
-    url: string;
-} | {
-    type: "reading";
-    sessionId: string;
-} | {
-    type: "clicking";
-    sessionId: string;
-    ref: string;
-} | {
-    type: "filling";
-    sessionId: string;
-    ref: string;
-} | {
-    type: "submitting-form";
-    sessionId: string;
-    formRef: string;
-} | {
-    type: "scrolling";
-    sessionId: string;
-    position: number;
-} | {
-    type: "injecting";
-    sessionId: string;
-} | {
-    type: "screenshotting";
-    sessionId: string;
-};
-/**
- * Shared custom interaction class for all browser tools. A frontend can
- * listen on getEvents() to show live status (e.g. "Searching...",
- * "Navigating to example.com...", "Clicking button...") while the agent
- * drives the browser, without waiting for the tool call itself to resolve.
- */
-export declare class BrowserInteraction extends MCPCustomClass {
-    emitBrowserEvent(event: BrowserEvent): void;
-}
-export default BrowserInteraction;
-//# sourceMappingURL=interaction.d.ts.map

package/dist/tools/browser/interaction.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.d.ts","sourceRoot":"","sources":["../../../src/tools/browser/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAEnD,MAAM,MAAM,YAAY,GAClB;IAAE,IAAI,EAAE,iBAAiB,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAA;CAAE,GAC3D;IAAE,IAAI,EAAE,iBAAiB,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,GAC9C;IAAE,IAAI,EAAE,YAAY,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAA;CAAE,GACtD;IAAE,IAAI,EAAE,SAAS,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,GACtC;IAAE,IAAI,EAAE,UAAU,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAA;CAAE,GACpD;IAAE,IAAI,EAAE,SAAS,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAA;CAAE,GACnD;IAAE,IAAI,EAAE,iBAAiB,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,GAC/D;IAAE,IAAI,EAAE,WAAW,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,GAC1D;IAAE,IAAI,EAAE,WAAW,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,GACxC;IAAE,IAAI,EAAE,gBAAgB,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,CAAC;AAEpD;;;;;GAKG;AACH,qBAAa,kBAAmB,SAAQ,cAAc;IAClD,gBAAgB,CAAC,KAAK,EAAE,YAAY;CAGvC;AAED,eAAe,kBAAkB,CAAC"}

package/dist/tools/browser/interaction.js

@@ -1,14 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-/**
- * Shared custom interaction class for all browser tools. A frontend can
- * listen on getEvents() to show live status (e.g. "Searching...",
- * "Navigating to example.com...", "Clicking button...") while the agent
- * drives the browser, without waiting for the tool call itself to resolve.
- */
-export class BrowserInteraction extends MCPCustomClass {
-    emitBrowserEvent(event) {
-        this.getEvents().emit("browser", event);
-    }
-}
-export default BrowserInteraction;
-//# sourceMappingURL=interaction.js.map

package/dist/tools/browser/interaction.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.js","sourceRoot":"","sources":["../../../src/tools/browser/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAcnD;;;;;GAKG;AACH,MAAM,OAAO,kBAAmB,SAAQ,cAAc;IAClD,gBAAgB,CAAC,KAAmB;QAChC,IAAI,CAAC,SAAS,EAAE,CAAC,IAAI,CAAC,SAAS,EAAE,KAAK,CAAC,CAAC;IAC5C,CAAC;CACJ;AAED,eAAe,kBAAkB,CAAC"}

package/dist/tools/fs/interaction.d.ts

@@ -1,37 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-export type FsEvent = {
-    type: "reading";
-    path: string;
-} | {
-    type: "writing";
-    path: string;
-} | {
-    type: "editing";
-    path: string;
-} | {
-    type: "deleting";
-    path: string;
-} | {
-    type: "moving";
-    from: string;
-    to: string;
-} | {
-    type: "listing";
-    path: string;
-} | {
-    type: "dir-created";
-    path: string;
-} | {
-    type: "stat";
-    path: string;
-};
-/**
- * Shared custom interaction class for all filesystem tools. A frontend can
- * listen on getEvents() to reflect live activity (e.g. "Reading file.ts...",
- * "Writing config.json...") while the agent works on disk.
- */
-export declare class FsInteraction extends MCPCustomClass {
-    emitFsEvent(event: FsEvent): void;
-}
-export default FsInteraction;
-//# sourceMappingURL=interaction.d.ts.map

package/dist/tools/fs/interaction.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.d.ts","sourceRoot":"","sources":["../../../src/tools/fs/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAEnD,MAAM,MAAM,OAAO,GACb;IAAE,IAAI,EAAE,SAAS,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GACjC;IAAE,IAAI,EAAE,SAAS,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GACjC;IAAE,IAAI,EAAE,SAAS,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GACjC;IAAE,IAAI,EAAE,UAAU,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GAClC;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,EAAE,EAAE,MAAM,CAAA;CAAE,GAC5C;IAAE,IAAI,EAAE,SAAS,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GACjC;IAAE,IAAI,EAAE,aAAa,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GACrC;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,CAAC;AAErC;;;;GAIG;AACH,qBAAa,aAAc,SAAQ,cAAc;IAC7C,WAAW,CAAC,KAAK,EAAE,OAAO;CAG7B;AAED,eAAe,aAAa,CAAC"}

package/dist/tools/fs/interaction.js

@@ -1,13 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-/**
- * Shared custom interaction class for all filesystem tools. A frontend can
- * listen on getEvents() to reflect live activity (e.g. "Reading file.ts...",
- * "Writing config.json...") while the agent works on disk.
- */
-export class FsInteraction extends MCPCustomClass {
-    emitFsEvent(event) {
-        this.getEvents().emit("fs", event);
-    }
-}
-export default FsInteraction;
-//# sourceMappingURL=interaction.js.map

package/dist/tools/fs/interaction.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.js","sourceRoot":"","sources":["../../../src/tools/fs/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAYnD;;;;GAIG;AACH,MAAM,OAAO,aAAc,SAAQ,cAAc;IAC7C,WAAW,CAAC,KAAc;QACtB,IAAI,CAAC,SAAS,EAAE,CAAC,IAAI,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;IACvC,CAAC;CACJ;AAED,eAAe,aAAa,CAAC"}

package/dist/tools/present/interaction.d.ts

@@ -1,17 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-export type PresentEvent = {
-    type: "presents-updated";
-    paths: string[];
-};
-/**
- * Shared custom interaction class for all present tools. A frontend can
- * listen on getEvents() to know the instant the set of presented files
- * changes (a new file was added, or everything was cleared) so it can
- * re-render whatever "here's the output" panel it shows the user, without
- * polling the present folder itself.
- */
-export declare class PresentInteraction extends MCPCustomClass {
-    emitPresentEvent(event: PresentEvent): void;
-}
-export default PresentInteraction;
-//# sourceMappingURL=interaction.d.ts.map

package/dist/tools/present/interaction.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.d.ts","sourceRoot":"","sources":["../../../src/tools/present/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAEnD,MAAM,MAAM,YAAY,GAClB;IAAE,IAAI,EAAE,kBAAkB,CAAC;IAAC,KAAK,EAAE,MAAM,EAAE,CAAA;CAAE,CAAC;AAEpD;;;;;;GAMG;AACH,qBAAa,kBAAmB,SAAQ,cAAc;IAClD,gBAAgB,CAAC,KAAK,EAAE,YAAY;CAGvC;AAED,eAAe,kBAAkB,CAAC"}

package/dist/tools/present/interaction.js

@@ -1,15 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-/**
- * Shared custom interaction class for all present tools. A frontend can
- * listen on getEvents() to know the instant the set of presented files
- * changes (a new file was added, or everything was cleared) so it can
- * re-render whatever "here's the output" panel it shows the user, without
- * polling the present folder itself.
- */
-export class PresentInteraction extends MCPCustomClass {
-    emitPresentEvent(event) {
-        this.getEvents().emit("present", event);
-    }
-}
-export default PresentInteraction;
-//# sourceMappingURL=interaction.js.map

package/dist/tools/present/interaction.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.js","sourceRoot":"","sources":["../../../src/tools/present/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAKnD;;;;;;GAMG;AACH,MAAM,OAAO,kBAAmB,SAAQ,cAAc;IAClD,gBAAgB,CAAC,KAAmB;QAChC,IAAI,CAAC,SAAS,EAAE,CAAC,IAAI,CAAC,SAAS,EAAE,KAAK,CAAC,CAAC;IAC5C,CAAC;CACJ;AAED,eAAe,kBAAkB,CAAC"}

package/dist/tools/question-answer/interaction.d.ts

@@ -1,14 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-export type QuestionAnswerEvent = {
-    type: "question-answer";
-};
-/**
- * Shared custom interaction class for all filesystem tools. A frontend can
- * listen on getEvents() to reflect live activity (e.g. "Reading file.ts...",
- * "Writing config.json...") while the agent works on disk.
- */
-export declare class QuestionAnswerInteraction extends MCPCustomClass {
-    emitQuestionAnswerEvent(event: QuestionAnswerEvent): void;
-}
-export default QuestionAnswerInteraction;
-//# sourceMappingURL=interaction.d.ts.map

package/dist/tools/question-answer/interaction.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.d.ts","sourceRoot":"","sources":["../../../src/tools/question-answer/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAEnD,MAAM,MAAM,mBAAmB,GACzB;IAAE,IAAI,EAAE,iBAAiB,CAAC;CAAE,CAAC;AAEnC;;;;GAIG;AACH,qBAAa,yBAA0B,SAAQ,cAAc;IACzD,uBAAuB,CAAC,KAAK,EAAE,mBAAmB;CAGrD;AAED,eAAe,yBAAyB,CAAC"}

package/dist/tools/question-answer/interaction.js

@@ -1,13 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-/**
- * Shared custom interaction class for all filesystem tools. A frontend can
- * listen on getEvents() to reflect live activity (e.g. "Reading file.ts...",
- * "Writing config.json...") while the agent works on disk.
- */
-export class QuestionAnswerInteraction extends MCPCustomClass {
-    emitQuestionAnswerEvent(event) {
-        this.getEvents().emit("question-answer", event);
-    }
-}
-export default QuestionAnswerInteraction;
-//# sourceMappingURL=interaction.js.map

package/dist/tools/question-answer/interaction.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.js","sourceRoot":"","sources":["../../../src/tools/question-answer/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAKnD;;;;GAIG;AACH,MAAM,OAAO,yBAA0B,SAAQ,cAAc;IACzD,uBAAuB,CAAC,KAA0B;QAC9C,IAAI,CAAC,SAAS,EAAE,CAAC,IAAI,CAAC,iBAAiB,EAAE,KAAK,CAAC,CAAC;IACpD,CAAC;CACJ;AAED,eAAe,yBAAyB,CAAC"}

package/dist/tools/todo/interaction.d.ts

@@ -1,30 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-export type TodoEvent = {
-    type: "list-created";
-    listId: string;
-    name: string;
-} | {
-    type: "list-removed";
-    listIds: string[];
-} | {
-    type: "task-created";
-    listId: string;
-    taskIds: string[];
-} | {
-    type: "task-removed";
-    taskIds: string[];
-} | {
-    type: "task-checked";
-    taskIds: string[];
-    checked: boolean;
-};
-/**
- * Shared custom interaction class for all todo tools. A frontend can listen
- * on getEvents() to reflect live changes (e.g. re-render a task list the
- * moment the agent checks something off) without polling storage.
- */
-export declare class TodoInteraction extends MCPCustomClass {
-    emitTodoEvent(event: TodoEvent): void;
-}
-export default TodoInteraction;
-//# sourceMappingURL=interaction.d.ts.map

package/dist/tools/todo/interaction.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.d.ts","sourceRoot":"","sources":["../../../src/tools/todo/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AAEnD,MAAM,MAAM,SAAS,GACf;IAAE,IAAI,EAAE,cAAc,CAAC;IAAC,MAAM,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GACtD;IAAE,IAAI,EAAE,cAAc,CAAC;IAAC,OAAO,EAAE,MAAM,EAAE,CAAA;CAAE,GAC3C;IAAE,IAAI,EAAE,cAAc,CAAC;IAAC,MAAM,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,MAAM,EAAE,CAAA;CAAE,GAC3D;IAAE,IAAI,EAAE,cAAc,CAAC;IAAC,OAAO,EAAE,MAAM,EAAE,CAAA;CAAE,GAC3C;IAAE,IAAI,EAAE,cAAc,CAAC;IAAC,OAAO,EAAE,MAAM,EAAE,CAAC;IAAC,OAAO,EAAE,OAAO,CAAA;CAAE,CAAC;AAEpE;;;;GAIG;AACH,qBAAa,eAAgB,SAAQ,cAAc;IAC/C,aAAa,CAAC,KAAK,EAAE,SAAS;CAGjC;AAED,eAAe,eAAe,CAAC"}

package/dist/tools/todo/interaction.js

@@ -1,13 +0,0 @@
-import { MCPCustomClass } from "../../core/mcp.js";
-/**
- * Shared custom interaction class for all todo tools. A frontend can listen
- * on getEvents() to reflect live changes (e.g. re-render a task list the
- * moment the agent checks something off) without polling storage.
- */
-export class TodoInteraction extends MCPCustomClass {
-    emitTodoEvent(event) {
-        this.getEvents().emit("todo", event);
-    }
-}
-export default TodoInteraction;
-//# sourceMappingURL=interaction.js.map

package/dist/tools/todo/interaction.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"interaction.js","sourceRoot":"","sources":["../../../src/tools/todo/interaction.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AASnD;;;;GAIG;AACH,MAAM,OAAO,eAAgB,SAAQ,cAAc;IAC/C,aAAa,CAAC,KAAgB;QAC1B,IAAI,CAAC,SAAS,EAAE,CAAC,IAAI,CAAC,MAAM,EAAE,KAAK,CAAC,CAAC;IACzC,CAAC;CACJ;AAED,eAAe,eAAe,CAAC"}