@morphllm/morphsdk 0.2.84 → 0.2.86

package/dist/tools/warp_grep/openai.d.ts

@@ -1,9 +1,10 @@
 import { ChatCompletionTool } from 'openai/resources/chat/completions';
 export { formatResult } from './client.js';
 export { getSystemPrompt } from './agent/prompt.js';
-import { d as WarpGrepToolConfig, b as WarpGrepResult } from '../../types-Cv4LpqVl.js';
-import './providers/types.js';
+import { d as WarpGrepToolConfig, b as WarpGrepResult } from '../../types-BMowL9iZ.js';
+import './agent/types.js';
 import '../utils/resilience.js';
+import './providers/types.js';
 
 /**
  * OpenAI SDK adapter for morph-warp-grep tool

package/dist/tools/warp_grep/openai.js

@@ -3,12 +3,12 @@ import {
   execute,
   openai_default,
   warpGrepTool
-} from "../../chunk-LX2WNS3L.js";
+} from "../../chunk-IXNX4HMC.js";
 import "../../chunk-KW7OEGZK.js";
 import {
   formatResult
-} from "../../chunk-D4EQYM6O.js";
-import "../../chunk-LF2X6YNP.js";
+} from "../../chunk-37SJ3IOY.js";
+import "../../chunk-HJOMBO2A.js";
 import "../../chunk-PUGSTXLO.js";
 import "../../chunk-KRDIR7GG.js";
 import "../../chunk-APP75CBN.js";

package/dist/tools/warp_grep/providers/remote.d.ts

@@ -1,5 +1,5 @@
 import { WarpGrepProvider, GrepResult, ReadResult, ListDirectoryEntry } from './types.js';
-import { R as RemoteCommands } from '../../../types-Cv4LpqVl.js';
+import { R as RemoteCommands } from '../../../types-BMowL9iZ.js';
 import '../../utils/resilience.js';
 
 /**

package/dist/tools/warp_grep/vercel.cjs

@@ -34,7 +34,8 @@ __export(vercel_exports, {
   default: () => vercel_default,
   execute: () => execute,
   formatResult: () => formatResult,
-  getSystemPrompt: () => getSystemPrompt
+  getSystemPrompt: () => getSystemPrompt,
+  warpGrepJsonSchema: () => warpGrepJsonSchema
 });
 module.exports = __toCommonJS(vercel_exports);
 var import_ai = require("ai");
@@ -1795,11 +1796,22 @@ function formatResult(result) {
 var WARP_GREP_DESCRIPTION = 'IMPORTANT: If you need to explore the codebase to gather context, and the task does not involve a single file or function which is provided by name, you should ALWAYS use the warpgrep codebase search tool first instead of running search commands. When the task requires exploration beyond a single known file, invoke warpgrep first with a natural-language query describing the target functionality, bug, or architectural concern. Warp Grep is a fast and accurate tool that can search for all relevant context in a codebase. Keep queries action-oriented (e.g., "Find where billing invoices are generated and emailed"), and after reviewing the summarized results, you may verify important findings with other search tools or direct file reads to ensure completeness. Warp Grep can be used for query types like: find function responsible for <small feature>; find code that does <description>; find code path for <big feature>; Where does <minimal error message> come from?; or any query of that type. When a task requires exploration beyond a single known file, ALWAYS default to warpgrep codebase search before other search mechanisms.';
 
 // tools/warp_grep/vercel.ts
+var warpGrepJsonSchema = {
+  type: "object",
+  properties: {
+    query: {
+      type: "string",
+      description: "Free-form repository question"
+    }
+  },
+  required: ["query"],
+  additionalProperties: false
+};
 async function execute(input, config) {
   return executeToolCall(input, config);
 }
 function createWarpGrepTool(config) {
-  const schema = import_zod.z.object({
+  const schema = config.inputSchema ?? import_zod.z.object({
     query: import_zod.z.string().describe("Free-form repository question")
   });
   return (0, import_ai.tool)({
@@ -1824,6 +1836,7 @@ var vercel_default = createWarpGrepTool;
   createWarpGrepTool,
   execute,
   formatResult,
-  getSystemPrompt
+  getSystemPrompt,
+  warpGrepJsonSchema
 });
 //# sourceMappingURL=vercel.cjs.map