@morphllm/morphsdk 0.2.134 → 0.2.135

package/dist/tools/warp_grep/openai.js

@@ -5,20 +5,20 @@ import {
   execute,
   openai_default,
   warpGrepTool
-} from "../../chunk-PTGAOOSH.js";
-import "../../chunk-37SPZ55Z.js";
+} from "../../chunk-KNE5TLKB.js";
+import "../../chunk-L3XJHXFB.js";
 import {
   formatResult
-} from "../../chunk-B6LTRVNE.js";
+} from "../../chunk-Y5UTWBLJ.js";
 import "../../chunk-NF2QWJDY.js";
 import "../../chunk-63VHBANJ.js";
-import "../../chunk-WBMMR34M.js";
+import "../../chunk-PXUIQKXO.js";
 import "../../chunk-GVGJIXV2.js";
 import "../../chunk-YLT4PSXT.js";
 import "../../chunk-DKODF3YG.js";
 import "../../chunk-QRXG5CAZ.js";
 import "../../chunk-VCKJ22DX.js";
-import "../../chunk-5ALXAPOK.js";
+import "../../chunk-B6CX5J56.js";
 import "../../chunk-PZ5AY32C.js";
 export {
   createGitHubReadFileTool,

package/dist/tools/warp_grep/vercel.cjs

@@ -969,7 +969,7 @@ var import_openai = __toESM(require("openai"), 1);
 // package.json
 var package_default = {
   name: "@morphllm/morphsdk",
-  version: "0.2.134",
+  version: "0.2.135",
   description: "TypeScript SDK and CLI for Morph Fast Apply integration",
   type: "module",
   main: "./dist/index.cjs",
@@ -2042,8 +2042,8 @@ function formatResult(result) {
 }
 
 // tools/warp_grep/prompts.ts
-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.';
-var GITHUB_WARP_GREP_SEARCH_DESCRIPTION = 'IMPORTANT: If you need to explore the codebase of a public GitHub repository (not your local workspace), use warpgrep_github_search instead of warpgrep_codebase_search. ONLY use this tool when the task requires understanding code in an external repo, and invoke warpgrep_github_search with a natural-language query describing the target functionality, bug, or architectural concern. DO NOT use this tool when the task requires understanding code in your local workspace. Use warpgrep_codebase_search instead.Useful when you suspect a library or framework is being used in a way that is not documented, or if you suspect an update or a bug in the library or framework.WarpGrep searches GitHub repos the same way it searches local codebases: fast and accurate. Keep queries action-oriented (e.g., "Find where how the new use workflow directive works"), and after reviewing the results, you may verify important findings with other tools or direct file reads. WarpGrep 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 involves exploring code in an external public repo, ALWAYS use warpgrep_github_search. You must provide either a github_url or owner_repo parameter (at least one is required).';
+var WARP_GREP_DESCRIPTION = 'Very fast code search exploration subagent (not a grep tool) that runs parallel grep and file read calls over multiple turns to locate relevant files and line ranges. The search term should be a targeted natural-language query describing what you are trying to find or accomplish, e.g. "Find where authentication requests are handled in the Express routes" or "How do callers of processOrder handle the error case?". Fill in extra context you can infer to make the query specific. Do not pass bare keywords or symbol names \u2014 use grep directly for exact symbol lookups. Use this tool first when exploring unfamiliar code. The results may be partial \u2014 follow up with classical search tools or direct file reads if needed.';
+var GITHUB_WARP_GREP_SEARCH_DESCRIPTION = "Code search exploration subagent for public GitHub repositories (not your local workspace \u2014 use warpgrep_codebase_search for that). Runs parallel grep and file read calls to locate relevant files and line ranges in external github repositories without cloning the repository. Pass a targeted natural-language query, not bare keywords. Useful for understanding how a library works or investigating upstream bugs. You must provide either github_url or owner_repo (at least one required). ";
 var GITHUB_SEARCH_DESCRIPTION = GITHUB_WARP_GREP_SEARCH_DESCRIPTION;
 var GITHUB_READ_FILE_DESCRIPTION = "Read a single file (or a line range) from a public GitHub repository. ONLY USE THIS WHEN YOU ALREADY KNOW THE EXACT FILE PATH YOU WANT TO READ, for example after finding it via warpgrep_github_search results. Takes owner/repo shorthand and the file path within the repo. Optionally specify startLine and endLine (1-based) to read a specific range. Returns the file content with line numbers.";