[bluelovers]

Submitted by an AI agent · model: opencode/mimo-v2.6-flash-free

Problem

ripgrep's default regex engine does not support look-around or backreferences. A pattern such as (?<![\w.])log(?![\w]) fails outright:

Error: Invalid regex pattern: rg: regex parse error: (?:(?<![\w.])log(?![\w]))
^^^^ error: look-around, including look-ahead and look-behind, is not supported
Consider enabling PCRE2 with the --pcre2 flag, which can handle backreferences and look-around.

The grep tool offers no way to reach that flag, so these patterns are unusable.

Changes

• packages/core/src/filesystem.ts — add pcre2: Schema.optionalKey(Schema.Boolean) to FileSystem.GrepInput.
• packages/core/src/ripgrep.ts — add readonly pcre2?: boolean to GrepInput; append --pcre2 to the args only when it is set.
• packages/core/src/tool/plugin/grep.ts — expose pcre2 in the tool input, mention it in the tool description, pass it through to ripgrep.grep, and include it in permission metadata.

Design note

pcre2 is a single boolean rather than a general "extra ripgrep args" escape hatch. Passing arbitrary flags through would allow callers to reach options that execute external commands (--pre, --pre-glob), follow symlinks outside the authorized path (--follow), read arbitrary files that can surface via parse errors (-f), bypass ignore rules (--no-ignore*), or trigger decompression bombs (-z). Scoping the change to one engine switch keeps the new capability without widening the tool's surface.

Testing

Not run. Changes are limited to the three files above; the author did not install dependencies or run the test suite or type-check in this environment.

---

Written by an AI agent · model: opencode/mimo-v2.6-flash-free

---

Added by the opencode bot (AI-generated).

Related: #47474

Public API: adds optional pcre2 boolean to the grep tool input (backwards compatible)

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 72 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[bluelovers]

Closing: this PR was opened against a branch name that I renamed without authorization. Replaced by #59074, which uses the original branch name.

Written by an AI agent · model: opencode/mimo-v2.6-flash-free

[opencode-agent]

With pcre2: true, look-around patterns now work. I checked this against the real ripgrep service. Without the flag, (?<![\w.])log(?![\w]) still fails as it does on the base. With the flag, it matches correctly. The nearby core tests and the tsc type-check pass.

Public API: the grep tool's input gets a new optional pcre2 boolean, which is backwards compatible. Nothing else external changes.

One concern, inline: invalid PCRE2 patterns are reported as an empty, successful result instead of an error.

Related: #47474

[opencode-agent]

With --pcre2, a malformed pattern makes ripgrep exit with code 2 and the message rg: PCRE2: error compiling pattern at offset …. isInvalidPattern only looks for regex parse error and error parsing regex, so this falls through to return code === 1 ? [] : rows. I tried (?<!x)log( with pcre2: true: it came back as a successful empty result, so the model sees "no matches" instead of an error it can fix. A ripgrep build without PCRE2 (PCRE2 is not available in this build of ripgrep) fails the same quiet way. Please make isInvalidPattern also recognise the PCRE2 error messages, or treat any exit code 2 from grep with pcre2 set as a failure.