cartethyia 2.7.8 → 2.8.0

package/src/providers/integrations/freebuff/assets/official-tools.json

@@ -0,0 +1,1070 @@
+[
+ {
+  "type": "function",
+  "function": {
+   "name": "read_files",
+   "description": "Example:\n<read_files_params_example>\n{\n  \"paths\": [\n    \"path/to/file1.ts\",\n    \"path/to/file2.ts\"\n  ]\n}\n</read_files_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Read files from disk. List several paths to read several files in one call. Large files are cut off after 2,000 lines, with a note telling you the file's total line count. Don't read a large file whole: use code_search to locate the part you need (matches come with line numbers), then read a window around it with { path, offset, limit }. Avoid tiny repeated slices; when in doubt, take a window of a few hundred lines.",
+    "type": "object",
+    "properties": {
+     "paths": {
+      "description": "List of files to read. Each entry is either a file path, or an object { path, offset, limit } to read a specific line range of that file.",
+      "type": "array",
+      "items": {
+       "anyOf": [
+        {
+         "description": "File path to read. Prefer paths relative to the **project root**; absolute paths inside the project are accepted, but paths outside the project will not work.",
+         "type": "string",
+         "minLength": 1
+        },
+        {
+         "type": "object",
+         "properties": {
+          "path": {
+           "type": "string",
+           "minLength": 1
+          },
+          "offset": {
+           "description": "Line number to start reading from (1-indexed).",
+           "type": "integer",
+           "minimum": 1,
+           "maximum": 9007199254740991
+          },
+          "limit": {
+           "description": "Maximum number of lines to read (defaults to 2,000).",
+           "type": "integer",
+           "exclusiveMinimum": 0,
+           "maximum": 9007199254740991
+          }
+         },
+         "required": [
+          "path"
+         ],
+         "additionalProperties": false
+        }
+       ]
+      }
+     }
+    },
+    "required": [
+     "paths"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "str_replace",
+   "description": "Use this tool to make edits within existing files.\n\nImportant:\nIf you are making multiple edits in a row to a file, use only one str_replace call with multiple replacements instead of multiple str_replace tool calls.\n\nExample:\n<str_replace_params_example>\n{\n  \"path\": \"path/to/file\",\n  \"replacements\": [\n    {\n      \"oldString\": \"This is the old string\",\n      \"newString\": \"This is the new string\"\n    },\n    {\n      \"oldString\": \"\\n\\t\\t// @codebuff delete this log line please\\n\\t\\tconsole.log(\\\"Hello, world!\\\");\\n\",\n      \"newString\": \"\\n\"\n    },\n    {\n      \"oldString\": \"\\nfoo:\",\n      \"newString\": \"\\nbar:\",\n      \"allowMultiple\": true\n    }\n  ]\n}\n</str_replace_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Replace strings in a file with new strings.",
+    "type": "object",
+    "properties": {
+     "path": {
+      "description": "The path to the file to edit.",
+      "type": "string",
+      "minLength": 1
+     },
+     "replacements": {
+      "description": "Array of replacements to make.",
+      "minItems": 1,
+      "type": "array",
+      "items": {
+       "description": "Pair of oldString and newString values.",
+       "type": "object",
+       "properties": {
+        "oldString": {
+         "description": "The string to replace. This must be an *exact match* of the string you want to replace, including whitespace and punctuation.",
+         "type": "string",
+         "minLength": 1
+        },
+        "newString": {
+         "description": "The string to replace the corresponding oldString with. Can be empty to delete.",
+         "type": "string"
+        },
+        "allowMultiple": {
+         "description": "Whether to allow multiple replacements of oldString.",
+         "default": false,
+         "type": "boolean"
+        }
+       },
+       "required": [
+        "oldString",
+        "newString"
+       ],
+       "additionalProperties": false
+      }
+     }
+    },
+    "required": [
+     "path",
+     "replacements"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "write_file",
+   "description": "Create or replace a file with the given content.\n\nFormat the `content` parameter with the entire content of the file.\n\n#### Additional Info\n\nDo not use this tool to delete or rename a file. Instead run a terminal command for that.\n\nExamples:\n\nExample 1 - Simple file creation:\n<write_file_params_example>\n{\n  \"path\": \"new-file.ts\",\n  \"instructions\": \"Prints Hello, world\",\n  \"content\": \"console.log(\\\"Hello, world!\\\");\"\n}\n</write_file_params_example>\n\nExample 2 - Overwriting a file:\n<write_file_params_example>\n{\n  \"path\": \"foo.ts\",\n  \"instructions\": \"Update foo function\",\n  \"content\": \"function foo() {\\n  doSomethingNew();\\n}\\n  \\nfunction bar() {\\n  doSomethingOld();\\n}\\n\"\n}\n</write_file_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Create or overwrite a file with the given content.",
+    "type": "object",
+    "properties": {
+     "path": {
+      "description": "Path to the file relative to the **project root**",
+      "type": "string",
+      "minLength": 1
+     },
+     "instructions": {
+      "description": "What the change is intended to do in only one sentence.",
+      "type": "string"
+     },
+     "content": {
+      "description": "Complete file content to write to the file.",
+      "type": "string"
+     }
+    },
+    "required": [
+     "path",
+     "instructions",
+     "content"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "run_terminal_command",
+   "description": "Stick to these use cases:\n1. Typechecking the project or running build (e.g., \"npm run build\"). Reading the output can help you edit code to fix build errors. If possible, use an option that performs checks but doesn't emit files, e.g. `tsc --noEmit`.\n2. Running tests (e.g., \"npm test\"). Reading the output can help you edit code to fix failing tests. Or, you could write new unit tests and then run them.\n3. Moving, renaming, or deleting files and directories. These actions can be vital for refactoring requests. Use `mv` or `rm` (commands run in bash on every OS, including Windows — do not use `move`/`del`).\n\nMost likely, you should ask for permission for any other type of command you want to run. If asking for permission, show the user the command you want to run using ``` tags and *do not* use the tool call format, e.g.:\n```bash\ngit branch -D foo\n```\n\nDO NOT do any of the following:\n1. Run commands that can modify files outside of the project directory, install packages globally, install virtual environments, or have significant side effects outside of the project directory, unless you have explicit permission from the user. Treat anything outside of the project directory as read-only.\n2. Run `git push` because it can break production (!) if the user was not expecting it. Don't run `git commit`, `git rebase`, or related commands unless you get explicit permission. If a user asks to commit changes, you can do so, but you should not invoke any further git commands beyond the git commit command.\n3. Run scripts without asking. Especially don't run scripts that could run against the production environment or have permanent effects without explicit permission from the user.\n4. Be careful with any command that has big or irreversible effects. Anything that touches a production environment, servers, the database, or other systems that could be affected by a command should be run with explicit permission from the user.\n5. Use the run_terminal_command tool to create or edit files. Do not use `cat` or `echo` to create or edit files. You should instead use other tools for creating or editing files.\n6. Use the wrong package manager for the project. For example, if the project uses `pnpm` or `bun` or `yarn`, you should not use `npm`. Similarly not everyone uses `pip` for python, etc.\n\nDo:\n- If there's an opportunity to use \"-y\" or \"--yes\" flags, use them. Any command that prompts for confirmation will hang if you don't use the flags.\n\nNotes:\n- If the user references a specific file, it could be either from their cwd or from the project root. You **must** determine which they are referring to (either infer or ask). Then, you must specify the path relative to the project root (or use the cwd parameter)\n- Commands can succeed without giving any output, e.g. if no type errors were found.\n\n\n### Using git to commit changes\n\nWhen the user requests a new git commit, please follow these steps closely:\n\n1. **Run two run_terminal_command tool calls:**\n   - Run `git diff` to review both staged and unstaged modifications.\n   - Run `git log` to check recent commit messages, ensuring consistency with this repository's style.\n\n2. **Select relevant files to include in the commit:**\n   Use the git context established at the start of this conversation to decide which files are pertinent to the changes. Stage any new untracked files that are relevant, but avoid committing previously modified files (from the beginning of the conversation) unless they directly relate to this commit.\n\n3. **Analyze the staged changes and compose a commit message:**\n   Enclose your analysis in <commit_analysis> tags. Within these tags, you should:\n   - Note which files have been altered or added.\n   - Categorize the nature of the changes (e.g., new feature, fix, refactor, documentation, etc.).\n   - Consider the purpose or motivation behind the alterations.\n   - Refrain from using tools to inspect code beyond what is presented in the git context.\n   - Evaluate the overall impact on the project.\n   - Check for sensitive details that should not be committed.\n   - Draft a concise, one- to two-sentence commit message focusing on the “why” rather than the “what.”\n   - Use precise, straightforward language that accurately represents the changes.\n   - Ensure the message provides clarity—avoid generic or vague terms like “Update” or “Fix” without context.\n   - Revisit your draft to confirm it truly reflects the changes and their intention.\n\n4. **Create the commit, ending with this specific footer:**\n   ```\n   Generated with Codebuff 🤖\n   Co-Authored-By: Codebuff <noreply@codebuff.com>\n   ```\n   Commands run in bash on every OS (Git Bash on Windows), so always use HEREDOC syntax to format the message:\n   ```\n   git commit -m \"$(cat <<'EOF'\n   Your commit message here.\n\n   🤖 Generated with Codebuff\n   Co-Authored-By: Codebuff <noreply@codebuff.com>\n   EOF\n   )\"\n   ```\n\n**Important details**\n\n- When feasible, use a single `git commit -am` command to add and commit together, but do not accidentally stage unrelated files.\n- Never alter the git config.\n- Do not push to the remote repository.\n- Avoid using interactive flags (e.g., `-i`) that require unsupported interactive input.\n- Do not create an empty commit if there are no changes.\n- Make sure your commit message is concise yet descriptive, focusing on the intention behind the changes rather than merely describing them.\n\n\nExample:\n<run_terminal_command_params_example>\n{\n  \"command\": \"echo \\\"hello world\\\"\"\n}\n</run_terminal_command_params_example>\n\n<run_terminal_command_params_example>\n{\n  \"command\": \"git commit -m \\\"Your commit message here.\\n\\n🤖 Generated with Codebuff\\nCo-Authored-By: Codebuff <noreply@codebuff.com>\\\"\"\n}\n</run_terminal_command_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Execute a CLI command from the **project root** (different from the user's cwd).",
+    "type": "object",
+    "properties": {
+     "command": {
+      "description": "CLI command. Always executed with bash (Git Bash on Windows), so use POSIX syntax on every OS: `mv`/`rm`, `/dev/null`, heredocs. Never use cmd.exe syntax like `del`, `move`, or `> nul` — on Windows `> nul` creates a literal file named \"nul\" that is very hard to delete.",
+      "type": "string",
+      "minLength": 1
+     },
+     "process_type": {
+      "description": "Either SYNC (waits, returns output) or BACKGROUND (runs in background). Default SYNC",
+      "default": "SYNC",
+      "type": "string",
+      "enum": [
+       "SYNC",
+       "BACKGROUND"
+      ]
+     },
+     "cwd": {
+      "description": "The working directory to run the command in. Default is the project root.",
+      "type": "string"
+     },
+     "timeout_seconds": {
+      "description": "How long to wait, in seconds. Default 30, which is right for almost everything — omit this field unless the command genuinely runs longer. Budget for the command you are actually running (a typecheck or test run is tens of seconds, not minutes); an over-long value does not make a command safer, it just means you wait that long when something hangs. Values above 600 (10 minutes) are clamped. Set to -1 to wait indefinitely, for genuinely open-ended commands only. Does not apply for BACKGROUND commands — use those for long-running processes instead.",
+      "default": 30,
+      "type": "number"
+     }
+    },
+    "required": [
+     "command"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "code_search",
+   "description": "Purpose: Search through code files to find files with specific text patterns, function names, variable names, and more.\n\nMatches are returned with their line numbers, so in a large file you can search first and then read a window around a match with read_files { path, offset, limit } instead of reading the whole file.\n\nUse cases:\n1. Finding all references to a function, class, or variable name across the codebase\n2. Searching for specific code patterns or implementations\n3. Looking up where certain strings or text appear\n4. Finding files that contain specific imports or dependencies\n5. Locating configuration settings or environment variables\n\nThe pattern supports regular expressions and will search recursively through all files in the project by default. Some tips:\n- Be as constraining in the pattern as possible to limit the number of files returned, e.g. if searching for the definition of a function, use \"(function foo|const foo)\" or \"def foo\" instead of merely \"foo\".\n- Use Rust-style regex, not grep-style, PCRE, RE2 or JavaScript regex - you must always escape special characters like { and }\n- Be as constraining as possible to limit results, e.g. use \"(function foo|const foo)\" or \"def foo\" instead of merely \"foo\"\n- Add context to your search with surrounding terms (e.g., \"function handleAuth\" rather than just \"handleAuth\")\n- Use word boundaries (\\b) to match whole words only\n- Use the cwd parameter to narrow your search to specific directories\n- For case-sensitive searches like constants (e.g., ERROR vs error), omit the \"-i\" flag\n- Searches file content and filenames\n- Automatically ignores binary files, hidden files, and files in .gitignore\n\n\nAdvanced ripgrep flags (use the flags parameter):\n\n- Case sensitivity: \"-i\" for case-insensitive search\n- File type filtering: \"-t ts -t js\" (TypeScript and JavaScript), \"-t py\" (Python), etc.\n- Exclude file types: \"--type-not py\" to exclude Python files\n- Context lines: \"-A 3\" (3 lines after), \"-B 2\" (2 lines before), \"-C 2\" (2 lines before and after)\n- Line numbers: \"-n\" to show line numbers\n- Count matches: \"-c\" to count matches per file\n- Only filenames: \"-l\" to show only filenames with matches\n- Invert match: \"-v\" to show lines that don't match\n- Word boundaries: \"-w\" to match whole words only\n- Fixed strings: \"-F\" to treat pattern as literal string (not regex)\n\nNote: Do not use the end_turn tool after this tool! You will want to see the output of this tool before ending your turn.\n\nRESULT LIMITING:\n\n- The maxResults parameter limits the number of results shown per file (default: 15)\n- There is also a global limit of 250 total results across all files\n- These limits allow you to see results across multiple files without being overwhelmed by matches in a single file\n- If a file has more matches than maxResults, you'll see a truncation notice indicating how many results were found\n- If the global limit is reached, remaining files will be skipped\n\nExamples:\n<code_search_params_example>\n{\n  \"pattern\": \"foo\"\n}\n</code_search_params_example>\n<code_search_params_example>\n{\n  \"pattern\": \"foo\\\\.bar = 1\\\\.0\"\n}\n</code_search_params_example>\n<code_search_params_example>\n{\n  \"pattern\": \"import.*foo\",\n  \"cwd\": \"src\"\n}\n</code_search_params_example>\n<code_search_params_example>\n{\n  \"pattern\": \"function.*authenticate\",\n  \"flags\": \"-i -t ts -t js\"\n}\n</code_search_params_example>\n<code_search_params_example>\n{\n  \"pattern\": \"TODO\",\n  \"flags\": \"-n --type-not py\"\n}\n</code_search_params_example>\n<code_search_params_example>\n{\n  \"pattern\": \"getUserData\",\n  \"maxResults\": 10\n}\n</code_search_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Search for string patterns in the project's files. This tool uses ripgrep (rg), a fast line-oriented search tool.",
+    "type": "object",
+    "properties": {
+     "pattern": {
+      "description": "The pattern to search for.",
+      "type": "string",
+      "minLength": 1
+     },
+     "flags": {
+      "description": "Optional ripgrep flags to customize the search (e.g., \"-i\" for case-insensitive, \"-g *.ts -g *.js\" for TypeScript and JavaScript files only, \"-g !*.test.ts\" to exclude Typescript test files,  \"-A 3\" for 3 lines after match, \"-B 2\" for 2 lines before match).",
+      "type": "string"
+     },
+     "cwd": {
+      "description": "Optional working directory to search within, relative to the project root. Defaults to searching the entire project.",
+      "type": "string"
+     },
+     "maxResults": {
+      "description": "Maximum number of results to return per file. Defaults to 15. There is also a global limit of 250 results across all files.",
+      "default": 15,
+      "type": "integer",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991
+     }
+    },
+    "required": [
+     "pattern"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "glob",
+   "description": "Example:\n<glob_params_example>\n{\n  \"pattern\": \"**/*.test.ts\"\n}\n</glob_params_example>\n\nPurpose: Search for files matching a glob pattern to discover files by name patterns rather than content.\nUse cases:\n- Find all files with a specific extension (e.g., \"*.js\", \"*.test.ts\")\n- Locate files in specific directories (e.g., \"src/**/*.ts\")\n- Find files with specific naming patterns (e.g., \"**/test_*.go\", \"**/*-config.json\")\n- Discover test files, configuration files, or other files with predictable naming\n\nGlob patterns support:\n- * matches any characters except /\n- ** matches any characters including /\n- ? matches a single character\n- [abc] matches one of the characters in brackets\n- {a,b} matches one of the comma-separated patterns\n\nThis tool is fast and works well for discovering files by name patterns.",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Search for files matching a glob pattern. Returns matching file paths sorted by modification time.",
+    "type": "object",
+    "properties": {
+     "pattern": {
+      "description": "Glob pattern to match files against (e.g., *.js, src/glob/*.ts, glob/test/glob/*.go).",
+      "type": "string",
+      "minLength": 1
+     },
+     "cwd": {
+      "description": "Optional working directory to search within, relative to project root. If not provided, searches from project root.",
+      "type": "string"
+     },
+     "max_results": {
+      "description": "Maximum number of matching paths to return.",
+      "type": "integer",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991
+     }
+    },
+    "required": [
+     "pattern"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "list_directory",
+   "description": "Lists all files and directories in the specified path. Useful for exploring directory structure and finding files.\n\nExample:\n<list_directory_params_example>\n{\n  \"path\": \"src/components\"\n}\n</list_directory_params_example>\n\n<list_directory_params_example>\n{\n  \"path\": \".\"\n}\n</list_directory_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "List files and directories in the specified path. Returns separate arrays of file names and directory names.",
+    "type": "object",
+    "properties": {
+     "path": {
+      "description": "Directory path to list, relative to the project root.",
+      "type": "string"
+     }
+    },
+    "required": [
+     "path"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "write_todos",
+   "description": "Use this tool to track your objectives through an ordered step-by-step plan. Call this tool after you have gathered context on the user's request to plan out the implementation steps for the user's request.\n\nAfter completing each todo step, call this tool again to update the list and mark that task as completed. Note that each time you call this tool, rewrite ALL todos with their current status.\n\nUse this tool frequently as you work through tasks to update the list of todos with their current status. Doing this is extremely useful because it helps you stay on track and complete all the requirements of the user's request. It also helps inform the user of your plans and the current progress, which they want to know at all times.\n\nExample:\n<write_todos_params_example>\n{\n  \"todos\": [\n    {\n      \"task\": \"Create new implementation in foo.ts\",\n      \"completed\": true\n    },\n    {\n      \"task\": \"Update bar.ts to use the new implementation\",\n      \"completed\": false\n    },\n    {\n      \"task\": \"Write tests for the new implementation\",\n      \"completed\": false\n    },\n    {\n      \"task\": \"Run the tests to verify the new implementation\",\n      \"completed\": false\n    }\n  ]\n}\n</write_todos_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Write a todo list to track tasks for multi-step implementations. Use this frequently to maintain an updated step-by-step plan.",
+    "type": "object",
+    "properties": {
+     "todos": {
+      "description": "List of todos with their completion status. Add ALL of the applicable tasks to the list, so you don't forget to do anything. Try to order the todos the same way you will complete them. Do not mark todos as completed if you have not completed them yet!",
+      "type": "array",
+      "items": {
+       "type": "object",
+       "properties": {
+        "task": {
+         "description": "Description of the task",
+         "type": "string"
+        },
+        "completed": {
+         "description": "Whether the task is completed",
+         "type": "boolean"
+        }
+       },
+       "required": [
+        "task",
+        "completed"
+       ],
+       "additionalProperties": false
+      }
+     }
+    },
+    "required": [
+     "todos"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "run_file_change_hooks",
+   "description": "Purpose: Trigger client-configured file change hooks for the specified files. This tool allows the backend to request the client to run its configured file change hooks (like tests, linting, type checking) after file changes have been applied.\n\nUse cases:\n- After making code changes, trigger the relevant tests and checks\n- Ensure code quality by running configured linters and type checkers\n- Validate that changes don't break the build\n\nThe client will run only the hooks whose filePattern matches the provided files.\n\nExample:\n<run_file_change_hooks_params_example>\n{\n  \"files\": [\n    \"src/components/Button.tsx\",\n    \"src/utils/helpers.ts\"\n  ]\n}\n</run_file_change_hooks_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "type": "object",
+    "properties": {
+     "files": {
+      "description": "List of file paths that were changed and should trigger file change hooks",
+      "type": "array",
+      "items": {
+       "type": "string"
+      }
+     }
+    },
+    "required": [
+     "files"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "end_turn",
+   "description": "Only use this tool to hand control back to the user.\n\n- When to use: after you have completed a meaningful chunk of work and you are either (a) fully done, or (b) explicitly waiting for the user's next message.\n- Do NOT use: as a stop token mid-work, to pause between tool calls, to wait for tool results, or to \"check in\" unnecessarily.\n- Before calling: finish all pending steps, resolve tool results, and include any outputs the user needs to review.\n- Effect: Signals the UI to wait for the user's reply; any pending tool results will be ignored.\n\n*INCORRECT USAGE*:\n<some_tool_that_produces_results_params_example>\n{\n  \"query\": \"some example search term\"\n}\n</some_tool_that_produces_results_params_example>\n\n<end_turn_params_example>\n{}\n</end_turn_params_example>\n\n*CORRECT USAGE*:\nAll done! Would you like some more help with xyz?\n\n<end_turn_params_example>\n{}\n</end_turn_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "End your turn, regardless of any new tool results that might be coming. This will allow the user to type another prompt.",
+    "type": "object",
+    "properties": {},
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "web_search",
+   "description": "Purpose: Search the web for current, up-to-date information on any topic. This tool uses Serper's Google Search API to find relevant content from across the internet.\n\nUse cases:\n- Finding current information about technologies, libraries, or frameworks\n- Researching best practices and solutions\n- Getting up-to-date news or documentation\n- Finding examples and tutorials\n- Checking current status of services or APIs\n\nThe tool will return JSON search results with titles, URLs, content snippets, and other available SERP fields such as answer boxes or related questions.\n\nExample:\n<web_search_params_example>\n{\n  \"query\": \"Next.js 15 new features\",\n  \"depth\": \"standard\"\n}\n</web_search_params_example>\n\n<web_search_params_example>\n{\n  \"query\": \"React Server Components tutorial\",\n  \"depth\": \"deep\"\n}\n</web_search_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Search the web for current information using Serper API.",
+    "type": "object",
+    "properties": {
+     "query": {
+      "description": "The search query to find relevant web content",
+      "type": "string",
+      "minLength": 1
+     },
+     "depth": {
+      "description": "Search depth - 'standard' for quick results, 'deep' for more comprehensive search. Default is 'standard'.",
+      "default": "standard",
+      "type": "string",
+      "enum": [
+       "standard",
+       "deep"
+      ]
+     }
+    },
+    "required": [
+     "query"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "read_url",
+   "description": "Purpose: Fetch a URL returned by web_search and extract the readable page text so you can answer with source-backed evidence.\n\nUse this after web_search when snippets are not enough. Prefer authoritative, relevant pages from the search results. The tool follows redirects, extracts titles and metadata, strips scripts/styles/navigation boilerplate from HTML, and returns normalized readable text.\n\nDo not use run_terminal_command with curl just to inspect web pages; use read_url instead. If read_url reports unsupported content or extraction failure, then choose a different search result or explain the limitation.\n\nExample:\n<read_url_params_example>\n{\n  \"url\": \"https://react.dev/reference/react/useActionState\",\n  \"max_chars\": 12000\n}\n</read_url_params_example>",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Fetch a URL and extract readable text from the page.",
+    "type": "object",
+    "properties": {
+     "url": {
+      "description": "The full http:// or https:// URL to fetch and extract readable text from.",
+      "type": "string",
+      "format": "uri"
+     },
+     "max_chars": {
+      "description": "Maximum number of extracted text characters to return. Defaults to 20000.",
+      "default": 20000,
+      "type": "integer",
+      "minimum": 1000,
+      "maximum": 50000
+     }
+    },
+    "required": [
+     "url"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "report_project_profile",
+   "description": "Internal tool. Call it only when a message explicitly asks you to report the project profile. Never call it otherwise, and never mention it to the user.",
+   "parameters": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "description": "Report what kind of project this is and what it is built with.",
+    "type": "object",
+    "properties": {
+     "status": {
+      "description": "unchanged: the current profile is correct. updated: send the new profile. not_enough_context: you have not seen enough of the project yet.",
+      "type": "string",
+      "enum": [
+       "unchanged",
+       "updated",
+       "not_enough_context"
+      ]
+     },
+     "app_kinds": {
+      "description": "Required when status is updated.",
+      "type": "array",
+      "items": {
+       "type": "string",
+       "enum": [
+        "Web app",
+        "Mobile app",
+        "Desktop app",
+        "Backend / API",
+        "CLI tool",
+        "Library / package",
+        "Game",
+        "Data / ML",
+        "Other"
+       ]
+      }
+     },
+     "technologies": {
+      "description": "Required when status is updated. The complete list; it replaces the old one.",
+      "type": "array",
+      "items": {
+       "type": "string"
+      }
+     }
+    },
+    "required": [
+     "status"
+    ],
+    "additionalProperties": false
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "suggest_prompts",
+   "description": "Propose follow-up prompts, rendered inline as clickable cards at this exact point. Call this before ending almost every substantive turn — offer two to four follow-ups, including bold ideas that branch beyond the immediate change, not just the obvious next step. Introduce each idea in a new prose paragraph immediately before the call, and start later prose in another paragraph. Usually pass one prompt, calling this tool again for each distinct idea; group only alternatives or closely related options. Merely rendering a prompt does not run it. Do not restate your answer here. Keep each prompt short and goal-oriented — one sentence naming the outcome, not the files, steps, or design decisions — so the agent that receives it is free to choose the approach. It must still stand alone when clicked. Give each a short label.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "prompts": {
+      "type": "array",
+      "items": {
+       "type": "object",
+       "properties": {
+        "prompt": {
+         "type": "string"
+        },
+        "label": {
+         "type": "string"
+        }
+       },
+       "required": [
+        "prompt"
+       ]
+      }
+     }
+    },
+    "required": [
+     "prompts"
+    ]
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "ask_questions",
+   "description": "Ask the user one or more structured questions and wait for their answers. Each question shows its options as clickable choices plus a free-text field, so use it whenever a real decision is the user’s to make — choosing between approaches, clarifying an ambiguous request, confirming something consequential — instead of guessing or asking in prose. Give each question a short header and 2–4 concrete options (label + one-line description), recommended option first with \"(Recommended)\" in its label; never add an \"Other\" option. The turn pauses until the user answers or skips.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "questions": {
+      "minItems": 1,
+      "type": "array",
+      "items": {
+       "type": "object",
+       "properties": {
+        "question": {
+         "type": "string",
+         "minLength": 1
+        },
+        "header": {
+         "type": "string"
+        },
+        "options": {
+         "type": "array",
+         "items": {
+          "type": "object",
+          "properties": {
+           "label": {
+            "type": "string",
+            "minLength": 1
+           },
+           "description": {
+            "type": "string"
+           }
+          },
+          "required": [
+           "label"
+          ]
+         }
+        },
+        "multiSelect": {
+         "type": "boolean"
+        }
+       },
+       "required": [
+        "question"
+       ]
+      }
+     }
+    },
+    "required": [
+     "questions"
+    ]
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "read_thread_context",
+   "description": "Read a bounded, persisted transcript excerpt and workspace/delivery metadata from another thread in this project. The user must explicitly reference the thread in the current prompt with an @ thread mention; pass the full threadId from the prompt's resolved thread references. This never returns provider session state or an in-progress response. Defaults to the latest 20 usable messages (24,000 text characters total; 8,000 per message). This is only a starting excerpt: when earlier context matters, search the ENTIRE saved conversation with query or follow nextBeforeSeq with beforeSeq. For overall background, also inspect the opening exchange using aroundSeq: firstMessageSeq. Use aroundSeq to read a search hit with neighboring messages. Read clipped text with messageSeq and offset (nextOffset continues the message; 0 starts it). Do not conclude that an earlier decision is absent from only the recent page. Tool calls/results, reasoning and attachment contents are omitted.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "threadId": {
+      "type": "string",
+      "minLength": 1
+     },
+     "beforeSeq": {
+      "description": "Read messages older than this exclusive message ID. Use nextBeforeSeq from a previous page; also works with query.",
+      "type": "integer",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991
+     },
+     "query": {
+      "description": "Case-insensitive literal text search (maximum 200 characters) across the entire persisted conversation and attachment names. Results include excerpts around matches.",
+      "type": "string",
+      "minLength": 1
+     },
+     "aroundSeq": {
+      "description": "Read a search hit in context: this message and up to two usable messages on either side. Use alone.",
+      "type": "integer",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991
+     },
+     "messageSeq": {
+      "description": "Read one message by its ID, including text clipped in an earlier excerpt. Use alone or with offset.",
+      "type": "integer",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991
+     },
+     "offset": {
+      "description": "Text offset for messageSeq. Use the returned nextOffset to continue a long message.",
+      "type": "integer",
+      "minimum": 0,
+      "maximum": 9007199254740991
+     }
+    },
+    "required": [
+     "threadId"
+    ]
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "request_elevation",
+   "description": "Request explicit user approval to run one command with operating-system administrator privileges. The app shows the exact command and reason, then invokes the native OS elevation prompt only if approved. Never include sudo/doas/pkexec in the command.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "command": {
+      "type": "string",
+      "minLength": 1
+     },
+     "reason": {
+      "type": "string",
+      "minLength": 1
+     }
+    },
+    "required": [
+     "command",
+     "reason"
+    ]
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "register_preview",
+   "description": "Show content in this thread's Preview tab. Choose exactly one mode: (1) pass `url` and `pid` for a running dev server, after it answers HTTP; or (2) pass `htmlPath` for a complete local .html/.htm file inside this thread's workspace, which the app serves safely without a separate process. Dev-server URLs must be loopback addresses. Set `replace: true` only when intentionally replacing the thread's current live preview; this stops its registered server when applicable. Otherwise a live-preview conflict is rejected. Registering the live preview again re-shows it.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "url": {
+      "type": "string"
+     },
+     "pid": {
+      "type": "integer",
+      "minimum": -9007199254740991,
+      "maximum": 9007199254740991
+     },
+     "htmlPath": {
+      "type": "string"
+     },
+     "replace": {
+      "type": "boolean"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_open",
+   "description": "Open a Chromium browser tab in this task, showing the same page to the user. Public HTTP(S) URLs and localhost are supported. No dev-server process is required. Returns tab id; pass it to subsequent tools. Reuse navigates the agent’s current tab or the supplied tabId instead of creating another.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "url": {
+      "type": "string"
+     },
+     "profileId": {
+      "type": "string"
+     },
+     "incognito": {
+      "type": "boolean"
+     },
+     "reuse": {
+      "type": "boolean"
+     },
+     "tabId": {
+      "type": "string"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_status",
+   "description": "List this task’s browser tabs and current page state.",
+   "parameters": {
+    "type": "object",
+    "properties": {}
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_close",
+   "description": "Close one browser tab without stopping its dev server.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_press",
+   "description": "Press a real browser key, e.g. Enter, Tab, Escape, ArrowDown, Control+a or Meta+a.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "key": {
+      "type": "string",
+      "minLength": 1
+     }
+    },
+    "required": [
+     "key"
+    ]
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_scroll",
+   "description": "Scroll the browser with real wheel input; x/y are pixel deltas.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "x": {
+      "type": "number"
+     },
+     "y": {
+      "type": "number"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_wait",
+   "description": "Wait until all supplied conditions match the page: CSS selector, visible text, URL substring. Bounded and interrupted when the human takes control.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "selector": {
+      "type": "string"
+     },
+     "text": {
+      "type": "string"
+     },
+     "urlIncludes": {
+      "type": "string"
+     },
+     "timeoutMs": {
+      "type": "integer",
+      "minimum": 100,
+      "maximum": 60000
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_resize",
+   "description": "Set the browser viewport in CSS pixels. Set fill:true to fill the panel instead.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "width": {
+      "type": "integer",
+      "minimum": 240,
+      "maximum": 3840
+     },
+     "height": {
+      "type": "integer",
+      "minimum": 240,
+      "maximum": 2160
+     },
+     "fill": {
+      "type": "boolean"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_set_color_scheme",
+   "description": "Emulate the page’s light/dark appearance.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "colorScheme": {
+      "type": "string",
+      "enum": [
+       "system",
+       "light",
+       "dark"
+      ]
+     }
+    },
+    "required": [
+     "colorScheme"
+    ]
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_recording_start",
+   "description": "Record this browser tab as a local WebM video (up to five minutes).",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_recording_stop",
+   "description": "Stop recording and return the local video artifact path.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_snapshot",
+   "description": "Read this thread's running preview page as a text accessibility tree. Each interactive node carries a `uid=` handle that preview_click / preview_type accept. Uids expire whenever the page changes (navigation, re-render, or a newer snapshot) — take a fresh snapshot before acting if in doubt. Open a browser with preview_open or register_preview. Omit tabId for the active tab in the desktop app.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_screenshot",
+   "description": "Capture a PNG screenshot of this thread's running preview page. Use it to SEE what the user sees — layout, styling, rendering glitches that no DOM reading reveals. Captures the viewport; fullPage tries for the whole scrollable page but often degrades to the viewport (it needs the page to hold still), so scroll with preview_evaluate to survey a long page.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "fullPage": {
+      "type": "boolean"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_click",
+   "description": "Click an element in the running preview page, addressed by a `uid` from the latest preview_snapshot, or a Playwright locator (e.g. role=button[name=\"Save\"]). Provide exactly one. Scrolls the element into view first. A stale-uid error means the page changed — re-snapshot and retry with a fresh uid. If the click navigates, this waits for the new page to load and answers `navigated: true` with its url; the DOM is then current, but rendering can lag it briefly, so trust preview_snapshot over an immediate screenshot.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "uid": {
+      "type": "string"
+     },
+     "locator": {
+      "type": "string"
+     },
+     "dblClick": {
+      "type": "boolean"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_type",
+   "description": "Type text into a browser element using uid from preview_snapshot OR a Playwright locator. Focuses the element, clears its current value by default (clear:false to append), inserts the text through real input events, and optionally presses Enter to submit.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "uid": {
+      "type": "string"
+     },
+     "locator": {
+      "type": "string"
+     },
+     "text": {
+      "type": "string"
+     },
+     "clear": {
+      "type": "boolean"
+     },
+     "pressEnter": {
+      "type": "boolean"
+     }
+    },
+    "required": [
+     "text"
+    ]
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_navigate",
+   "description": "Navigate a browser tab: `to` is an HTTP(S) URL, or one of \"reload\", \"back\", \"forward\". Waits briefly for the page to load. All previous snapshot uids become stale after navigating.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "to": {
+      "type": "string",
+      "minLength": 1
+     }
+    },
+    "required": [
+     "to"
+    ]
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_evaluate",
+   "description": "Evaluate a JavaScript expression in the running preview page and return its JSON-serialized result (promises are awaited). Use it to probe state the snapshot cannot show — computed styles, app store contents, function results. Prefer read-only expressions; use preview_click/preview_type for user-like interaction.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "expression": {
+      "type": "string",
+      "minLength": 1
+     }
+    },
+    "required": [
+     "expression"
+    ]
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "preview_logs",
+   "description": "Read the running preview page's console messages and network requests captured since the preview attached (or since the last clear). Check this after interactions to catch errors, failed requests, and warnings the page produced.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "tabId": {
+      "type": "string"
+     },
+     "kind": {
+      "type": "string",
+      "enum": [
+       "console",
+       "network",
+       "all"
+      ]
+     },
+     "limit": {
+      "type": "integer",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991
+     },
+     "clear": {
+      "type": "boolean"
+     }
+    }
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "browser_check",
+   "description": "Unavailable in this build — use your normal tools (or ask the user to look at the Preview tab) instead.",
+   "parameters": {
+    "type": "object",
+    "properties": {}
+   }
+  }
+ },
+ {
+  "type": "function",
+  "function": {
+   "name": "write_doc",
+   "description": "Unavailable in this build — write markdown files with your normal file tools instead.",
+   "parameters": {
+    "type": "object",
+    "properties": {
+     "name": {
+      "type": "string"
+     },
+     "content": {
+      "type": "string"
+     },
+     "mode": {
+      "type": "string",
+      "enum": [
+       "append",
+       "replace"
+      ]
+     }
+    },
+    "required": [
+     "name",
+     "content"
+    ]
+   }
+  }
+ }
+]