search_code
Locate text or code patterns within files using regex and file filters. Supports context lines, custom timeouts, and searches only in allowed directories. Use absolute paths for reliable results.
Instructions
Search for text/code patterns within file contents using ripgrep.
Use this instead of 'execute_command' with grep/find for searching code content.
Fast and powerful search similar to VS Code search functionality.
Supports regular expressions, file pattern filtering, and context lines.
Has a default timeout of 30 seconds which can be customized.
Only searches within allowed directories.
IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths.
This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| contextLines | No | ||
| filePattern | No | ||
| ignoreCase | No | ||
| includeHidden | No | ||
| maxResults | No | ||
| path | Yes | ||
| pattern | Yes | ||
| timeoutMs | No |
Input Schema (JSON Schema)
{
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false,
"properties": {
"contextLines": {
"type": "number"
},
"filePattern": {
"type": "string"
},
"ignoreCase": {
"type": "boolean"
},
"includeHidden": {
"type": "boolean"
},
"maxResults": {
"type": "number"
},
"path": {
"type": "string"
},
"pattern": {
"type": "string"
},
"timeoutMs": {
"type": "number"
}
},
"required": [
"path",
"pattern"
],
"type": "object"
}