fix(ask): Properly handle regex filters that include parenthesis by msukkari · Pull Request #786 · sourcebot-dev/sourcebot

msukkari · 2026-01-23T01:32:44Z

Weird edge case where if a regex filter like filename/reponame contained a parenthesis the parser would fail. This is because the query language forbids parenthesis in the value since they're used to match against the ParenExpr symbol.

The ideal case is that the agent would be smart enough to wrap the regexp in quotes, which would solve this problem. I've added instructions in the tool call to tell it to do this, but it rarely does. As a result, I've added basic logic to process the regexp before adding it in the query string to wrap it in quotes if a parenthesis is included.

Fixes#771

Summary by CodeRabbit

Bug Fixes
- Properly handle regex filters that include parentheses.
New Features
- Added file path filtering capability to code search functionality.
Documentation
- Updated guidance on using file filters with parentheses in regex expressions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-23T01:33:08Z

Walkthrough

PR addresses issue #771 by implementing proper handling of regex filters containing parentheses. Introduces new preprocessRegexp utility function that wraps values with parentheses in quotes, adds filterByFile parameter to the search_code tool, and applies consistent preprocessing across MCP and web client implementations to prevent query parsing failures.

Changes

Cohort / File(s)	Summary
Regex preprocessing utility `packages/shared/src/query.ts`	New exported function `preprocessRegexp(value: string)` that detects parentheses in unquoted values and wraps them in double quotes to safely handle special characters in regex patterns.
Shared package exports `packages/shared/src/index.client.ts`, `packages/shared/src/index.server.ts`	Added re-exports of `preprocessRegexp` from `./query.js` to make the utility available across package boundaries.
MCP search_code tool enhancement `packages/mcp/src/index.ts`	Extended `search_code` tool with new `filterByFile` parameter (array of strings). Imported `preprocessRegexp` and implemented filtering logic to transform file paths with preprocessing before appending to query as `( file:… )` clauses. Updated descriptions to document new functionality.
Web client tool documentation & preprocessing `packages/web/src/features/chat/tools.ts`, `packages/web/src/features/chat/utils.ts`	Updated tool descriptions to document parenthesis handling requirements. Added preprocessing step in `buildSearchQuery` to transform file and repo filter regexes using `preprocessRegexp` before query composition.
Changelog `CHANGELOG.md`	Added entry under Unreleased/Fixed: "Properly handle regex filters that include parenthesis." Appended reference tag to existing hotkey mapping item.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

feat(ask_sb): Improved search tool ; tools for listing / searching repos ; removed search scope constraint #400: Introduces the foundational regex handling enhancement (preprocessRegexp) that this PR extends with MCP tool integration and file filtering support.
chore(api): Changed the search api to return raw source (instead of base64 encoding) #356: Also modifies the search_code tool in packages/mcp/src/index.ts, though for different functionality (snippet source handling).

Suggested reviewers

brendan-kellam

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding proper handling of regex filters containing parentheses, which directly addresses the fix for issue `#771`.
Linked Issues check	✅ Passed	The PR implements the required fix for issue `#771` by adding preprocessRegexp logic to wrap regex filter values containing parentheses in quotes, preventing parser failures.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing regex filter handling with parentheses. No out-of-scope modifications detected; changes focus on the preprocessRegexp function, its exports, and its integration into search query building.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

packages/web/src/features/chat/tools.ts (1)

142-173: Fix minor typos in the tool description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.`)+ .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.`)

packages/mcp/src/index.ts (1)

24-49: Fix minor typos in schema/description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.")+ .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.")

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 12: Update the changelog entry text to use the plural form "parentheses"
instead of "parenthesis" for clarity; locate the line containing "Properly
handle regex filters that include parenthesis.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to
"Properly handle regex filters that include parentheses.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

coderabbitai · 2026-01-23T01:38:31Z

 ### Fixed
- Properly map all hotkeys in UI based on the platform [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly map all hotkeys in UI based on the platform. [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)


⚠️ Potential issue | 🟡 Minor
Use “parentheses” (plural) for clarity.
Minor wording nit in the changelog entry.
✏️ Suggested tweak
-- Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)+- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
📝 Committable suggestion
‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)
- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
🤖 Prompt for AI Agents
In `@CHANGELOG.md` at line 12, Update the changelog entry text to use the plural form "parentheses" instead of "parenthesis" for clarity; locate the line containing "Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to "Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

brendan-kellam · 2026-01-23T02:34:53Z

 // Entry point for the MCP server
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { preprocessRegexp } from '@sourcebot/shared';


nit: mcp cannot take a dependency on @sourcebot/shared since we do not publish it to npm

brendan-kellam · 2026-01-23T02:41:27Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

msukkari · 2026-01-23T05:06:16Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

Closing in favor of #788

msukkari · 2026-01-23T01:32:44Z

Weird edge case where if a regex filter like filename/reponame contained a parenthesis the parser would fail. This is because the query language forbids parenthesis in the value since they're used to match against the ParenExpr symbol.

The ideal case is that the agent would be smart enough to wrap the regexp in quotes, which would solve this problem. I've added instructions in the tool call to tell it to do this, but it rarely does. As a result, I've added basic logic to process the regexp before adding it in the query string to wrap it in quotes if a parenthesis is included.

Fixes#771

Summary by CodeRabbit

Bug Fixes
- Properly handle regex filters that include parentheses.
New Features
- Added file path filtering capability to code search functionality.
Documentation
- Updated guidance on using file filters with parentheses in regex expressions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-23T01:33:08Z

Walkthrough

PR addresses issue #771 by implementing proper handling of regex filters containing parentheses. Introduces new preprocessRegexp utility function that wraps values with parentheses in quotes, adds filterByFile parameter to the search_code tool, and applies consistent preprocessing across MCP and web client implementations to prevent query parsing failures.

Changes

Cohort / File(s)	Summary
Regex preprocessing utility `packages/shared/src/query.ts`	New exported function `preprocessRegexp(value: string)` that detects parentheses in unquoted values and wraps them in double quotes to safely handle special characters in regex patterns.
Shared package exports `packages/shared/src/index.client.ts`, `packages/shared/src/index.server.ts`	Added re-exports of `preprocessRegexp` from `./query.js` to make the utility available across package boundaries.
MCP search_code tool enhancement `packages/mcp/src/index.ts`	Extended `search_code` tool with new `filterByFile` parameter (array of strings). Imported `preprocessRegexp` and implemented filtering logic to transform file paths with preprocessing before appending to query as `( file:… )` clauses. Updated descriptions to document new functionality.
Web client tool documentation & preprocessing `packages/web/src/features/chat/tools.ts`, `packages/web/src/features/chat/utils.ts`	Updated tool descriptions to document parenthesis handling requirements. Added preprocessing step in `buildSearchQuery` to transform file and repo filter regexes using `preprocessRegexp` before query composition.
Changelog `CHANGELOG.md`	Added entry under Unreleased/Fixed: "Properly handle regex filters that include parenthesis." Appended reference tag to existing hotkey mapping item.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

feat(ask_sb): Improved search tool ; tools for listing / searching repos ; removed search scope constraint #400: Introduces the foundational regex handling enhancement (preprocessRegexp) that this PR extends with MCP tool integration and file filtering support.
chore(api): Changed the search api to return raw source (instead of base64 encoding) #356: Also modifies the search_code tool in packages/mcp/src/index.ts, though for different functionality (snippet source handling).

Suggested reviewers

brendan-kellam

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding proper handling of regex filters containing parentheses, which directly addresses the fix for issue `#771`.
Linked Issues check	✅ Passed	The PR implements the required fix for issue `#771` by adding preprocessRegexp logic to wrap regex filter values containing parentheses in quotes, preventing parser failures.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing regex filter handling with parentheses. No out-of-scope modifications detected; changes focus on the preprocessRegexp function, its exports, and its integration into search query building.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

packages/web/src/features/chat/tools.ts (1)

142-173: Fix minor typos in the tool description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.`)+ .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.`)

packages/mcp/src/index.ts (1)

24-49: Fix minor typos in schema/description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.")+ .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.")

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 12: Update the changelog entry text to use the plural form "parentheses"
instead of "parenthesis" for clarity; locate the line containing "Properly
handle regex filters that include parenthesis.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to
"Properly handle regex filters that include parentheses.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

coderabbitai · 2026-01-23T01:38:31Z

 ### Fixed
- Properly map all hotkeys in UI based on the platform [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly map all hotkeys in UI based on the platform. [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)


⚠️ Potential issue | 🟡 Minor
Use “parentheses” (plural) for clarity.
Minor wording nit in the changelog entry.
✏️ Suggested tweak
-- Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)+- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
📝 Committable suggestion
‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)
- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
🤖 Prompt for AI Agents
In `@CHANGELOG.md` at line 12, Update the changelog entry text to use the plural form "parentheses" instead of "parenthesis" for clarity; locate the line containing "Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to "Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

brendan-kellam · 2026-01-23T02:34:53Z

 // Entry point for the MCP server
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { preprocessRegexp } from '@sourcebot/shared';


nit: mcp cannot take a dependency on @sourcebot/shared since we do not publish it to npm

brendan-kellam · 2026-01-23T02:41:27Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

msukkari · 2026-01-23T05:06:16Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

Closing in favor of #788

msukkari · 2026-01-23T01:32:44Z

Weird edge case where if a regex filter like filename/reponame contained a parenthesis the parser would fail. This is because the query language forbids parenthesis in the value since they're used to match against the ParenExpr symbol.

The ideal case is that the agent would be smart enough to wrap the regexp in quotes, which would solve this problem. I've added instructions in the tool call to tell it to do this, but it rarely does. As a result, I've added basic logic to process the regexp before adding it in the query string to wrap it in quotes if a parenthesis is included.

Fixes#771

Summary by CodeRabbit

Bug Fixes
- Properly handle regex filters that include parentheses.
New Features
- Added file path filtering capability to code search functionality.
Documentation
- Updated guidance on using file filters with parentheses in regex expressions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-23T01:33:08Z

Walkthrough

PR addresses issue #771 by implementing proper handling of regex filters containing parentheses. Introduces new preprocessRegexp utility function that wraps values with parentheses in quotes, adds filterByFile parameter to the search_code tool, and applies consistent preprocessing across MCP and web client implementations to prevent query parsing failures.

Changes

Cohort / File(s)	Summary
Regex preprocessing utility `packages/shared/src/query.ts`	New exported function `preprocessRegexp(value: string)` that detects parentheses in unquoted values and wraps them in double quotes to safely handle special characters in regex patterns.
Shared package exports `packages/shared/src/index.client.ts`, `packages/shared/src/index.server.ts`	Added re-exports of `preprocessRegexp` from `./query.js` to make the utility available across package boundaries.
MCP search_code tool enhancement `packages/mcp/src/index.ts`	Extended `search_code` tool with new `filterByFile` parameter (array of strings). Imported `preprocessRegexp` and implemented filtering logic to transform file paths with preprocessing before appending to query as `( file:… )` clauses. Updated descriptions to document new functionality.
Web client tool documentation & preprocessing `packages/web/src/features/chat/tools.ts`, `packages/web/src/features/chat/utils.ts`	Updated tool descriptions to document parenthesis handling requirements. Added preprocessing step in `buildSearchQuery` to transform file and repo filter regexes using `preprocessRegexp` before query composition.
Changelog `CHANGELOG.md`	Added entry under Unreleased/Fixed: "Properly handle regex filters that include parenthesis." Appended reference tag to existing hotkey mapping item.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

feat(ask_sb): Improved search tool ; tools for listing / searching repos ; removed search scope constraint #400: Introduces the foundational regex handling enhancement (preprocessRegexp) that this PR extends with MCP tool integration and file filtering support.
chore(api): Changed the search api to return raw source (instead of base64 encoding) #356: Also modifies the search_code tool in packages/mcp/src/index.ts, though for different functionality (snippet source handling).

Suggested reviewers

brendan-kellam

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding proper handling of regex filters containing parentheses, which directly addresses the fix for issue `#771`.
Linked Issues check	✅ Passed	The PR implements the required fix for issue `#771` by adding preprocessRegexp logic to wrap regex filter values containing parentheses in quotes, preventing parser failures.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing regex filter handling with parentheses. No out-of-scope modifications detected; changes focus on the preprocessRegexp function, its exports, and its integration into search query building.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

packages/web/src/features/chat/tools.ts (1)

142-173: Fix minor typos in the tool description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.`)+ .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.`)

packages/mcp/src/index.ts (1)

24-49: Fix minor typos in schema/description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.")+ .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.")

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 12: Update the changelog entry text to use the plural form "parentheses"
instead of "parenthesis" for clarity; locate the line containing "Properly
handle regex filters that include parenthesis.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to
"Properly handle regex filters that include parentheses.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

coderabbitai · 2026-01-23T01:38:31Z

 ### Fixed
- Properly map all hotkeys in UI based on the platform [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly map all hotkeys in UI based on the platform. [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)


⚠️ Potential issue | 🟡 Minor
Use “parentheses” (plural) for clarity.
Minor wording nit in the changelog entry.
✏️ Suggested tweak
-- Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)+- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
📝 Committable suggestion
‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)
- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
🤖 Prompt for AI Agents
In `@CHANGELOG.md` at line 12, Update the changelog entry text to use the plural form "parentheses" instead of "parenthesis" for clarity; locate the line containing "Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to "Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

brendan-kellam · 2026-01-23T02:34:53Z

 // Entry point for the MCP server
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { preprocessRegexp } from '@sourcebot/shared';


nit: mcp cannot take a dependency on @sourcebot/shared since we do not publish it to npm

brendan-kellam · 2026-01-23T02:41:27Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

msukkari · 2026-01-23T05:06:16Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

Closing in favor of #788

msukkari · 2026-01-23T01:32:44Z

Weird edge case where if a regex filter like filename/reponame contained a parenthesis the parser would fail. This is because the query language forbids parenthesis in the value since they're used to match against the ParenExpr symbol.

The ideal case is that the agent would be smart enough to wrap the regexp in quotes, which would solve this problem. I've added instructions in the tool call to tell it to do this, but it rarely does. As a result, I've added basic logic to process the regexp before adding it in the query string to wrap it in quotes if a parenthesis is included.

Fixes#771

Summary by CodeRabbit

Bug Fixes
- Properly handle regex filters that include parentheses.
New Features
- Added file path filtering capability to code search functionality.
Documentation
- Updated guidance on using file filters with parentheses in regex expressions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-23T01:33:08Z

Walkthrough

PR addresses issue #771 by implementing proper handling of regex filters containing parentheses. Introduces new preprocessRegexp utility function that wraps values with parentheses in quotes, adds filterByFile parameter to the search_code tool, and applies consistent preprocessing across MCP and web client implementations to prevent query parsing failures.

Changes

Cohort / File(s)	Summary
Regex preprocessing utility `packages/shared/src/query.ts`	New exported function `preprocessRegexp(value: string)` that detects parentheses in unquoted values and wraps them in double quotes to safely handle special characters in regex patterns.
Shared package exports `packages/shared/src/index.client.ts`, `packages/shared/src/index.server.ts`	Added re-exports of `preprocessRegexp` from `./query.js` to make the utility available across package boundaries.
MCP search_code tool enhancement `packages/mcp/src/index.ts`	Extended `search_code` tool with new `filterByFile` parameter (array of strings). Imported `preprocessRegexp` and implemented filtering logic to transform file paths with preprocessing before appending to query as `( file:… )` clauses. Updated descriptions to document new functionality.
Web client tool documentation & preprocessing `packages/web/src/features/chat/tools.ts`, `packages/web/src/features/chat/utils.ts`	Updated tool descriptions to document parenthesis handling requirements. Added preprocessing step in `buildSearchQuery` to transform file and repo filter regexes using `preprocessRegexp` before query composition.
Changelog `CHANGELOG.md`	Added entry under Unreleased/Fixed: "Properly handle regex filters that include parenthesis." Appended reference tag to existing hotkey mapping item.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

feat(ask_sb): Improved search tool ; tools for listing / searching repos ; removed search scope constraint #400: Introduces the foundational regex handling enhancement (preprocessRegexp) that this PR extends with MCP tool integration and file filtering support.
chore(api): Changed the search api to return raw source (instead of base64 encoding) #356: Also modifies the search_code tool in packages/mcp/src/index.ts, though for different functionality (snippet source handling).

Suggested reviewers

brendan-kellam

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding proper handling of regex filters containing parentheses, which directly addresses the fix for issue `#771`.
Linked Issues check	✅ Passed	The PR implements the required fix for issue `#771` by adding preprocessRegexp logic to wrap regex filter values containing parentheses in quotes, preventing parser failures.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing regex filter handling with parentheses. No out-of-scope modifications detected; changes focus on the preprocessRegexp function, its exports, and its integration into search query building.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

packages/web/src/features/chat/tools.ts (1)

142-173: Fix minor typos in the tool description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.`)+ .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.`)

packages/mcp/src/index.ts (1)

24-49: Fix minor typos in schema/description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.")+ .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.")

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 12: Update the changelog entry text to use the plural form "parentheses"
instead of "parenthesis" for clarity; locate the line containing "Properly
handle regex filters that include parenthesis.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to
"Properly handle regex filters that include parentheses.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

coderabbitai · 2026-01-23T01:38:31Z

 ### Fixed
- Properly map all hotkeys in UI based on the platform [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly map all hotkeys in UI based on the platform. [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)


⚠️ Potential issue | 🟡 Minor
Use “parentheses” (plural) for clarity.
Minor wording nit in the changelog entry.
✏️ Suggested tweak
-- Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)+- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
📝 Committable suggestion
‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)
- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
🤖 Prompt for AI Agents
In `@CHANGELOG.md` at line 12, Update the changelog entry text to use the plural form "parentheses" instead of "parenthesis" for clarity; locate the line containing "Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to "Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

brendan-kellam · 2026-01-23T02:34:53Z

 // Entry point for the MCP server
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { preprocessRegexp } from '@sourcebot/shared';


nit: mcp cannot take a dependency on @sourcebot/shared since we do not publish it to npm

brendan-kellam · 2026-01-23T02:41:27Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

msukkari · 2026-01-23T05:06:16Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

Closing in favor of #788

msukkari · 2026-01-23T01:32:44Z

Weird edge case where if a regex filter like filename/reponame contained a parenthesis the parser would fail. This is because the query language forbids parenthesis in the value since they're used to match against the ParenExpr symbol.

The ideal case is that the agent would be smart enough to wrap the regexp in quotes, which would solve this problem. I've added instructions in the tool call to tell it to do this, but it rarely does. As a result, I've added basic logic to process the regexp before adding it in the query string to wrap it in quotes if a parenthesis is included.

Fixes#771

Summary by CodeRabbit

Bug Fixes
- Properly handle regex filters that include parentheses.
New Features
- Added file path filtering capability to code search functionality.
Documentation
- Updated guidance on using file filters with parentheses in regex expressions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-23T01:33:08Z

Walkthrough

PR addresses issue #771 by implementing proper handling of regex filters containing parentheses. Introduces new preprocessRegexp utility function that wraps values with parentheses in quotes, adds filterByFile parameter to the search_code tool, and applies consistent preprocessing across MCP and web client implementations to prevent query parsing failures.

Changes

Cohort / File(s)	Summary
Regex preprocessing utility `packages/shared/src/query.ts`	New exported function `preprocessRegexp(value: string)` that detects parentheses in unquoted values and wraps them in double quotes to safely handle special characters in regex patterns.
Shared package exports `packages/shared/src/index.client.ts`, `packages/shared/src/index.server.ts`	Added re-exports of `preprocessRegexp` from `./query.js` to make the utility available across package boundaries.
MCP search_code tool enhancement `packages/mcp/src/index.ts`	Extended `search_code` tool with new `filterByFile` parameter (array of strings). Imported `preprocessRegexp` and implemented filtering logic to transform file paths with preprocessing before appending to query as `( file:… )` clauses. Updated descriptions to document new functionality.
Web client tool documentation & preprocessing `packages/web/src/features/chat/tools.ts`, `packages/web/src/features/chat/utils.ts`	Updated tool descriptions to document parenthesis handling requirements. Added preprocessing step in `buildSearchQuery` to transform file and repo filter regexes using `preprocessRegexp` before query composition.
Changelog `CHANGELOG.md`	Added entry under Unreleased/Fixed: "Properly handle regex filters that include parenthesis." Appended reference tag to existing hotkey mapping item.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

feat(ask_sb): Improved search tool ; tools for listing / searching repos ; removed search scope constraint #400: Introduces the foundational regex handling enhancement (preprocessRegexp) that this PR extends with MCP tool integration and file filtering support.
chore(api): Changed the search api to return raw source (instead of base64 encoding) #356: Also modifies the search_code tool in packages/mcp/src/index.ts, though for different functionality (snippet source handling).

Suggested reviewers

brendan-kellam

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding proper handling of regex filters containing parentheses, which directly addresses the fix for issue `#771`.
Linked Issues check	✅ Passed	The PR implements the required fix for issue `#771` by adding preprocessRegexp logic to wrap regex filter values containing parentheses in quotes, preventing parser failures.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing regex filter handling with parentheses. No out-of-scope modifications detected; changes focus on the preprocessRegexp function, its exports, and its integration into search query building.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

packages/web/src/features/chat/tools.ts (1)

142-173: Fix minor typos in the tool description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.`)+ .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.`)

packages/mcp/src/index.ts (1)

24-49: Fix minor typos in schema/description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.")+ .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.")

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 12: Update the changelog entry text to use the plural form "parentheses"
instead of "parenthesis" for clarity; locate the line containing "Properly
handle regex filters that include parenthesis.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to
"Properly handle regex filters that include parentheses.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

coderabbitai · 2026-01-23T01:38:31Z

 ### Fixed
- Properly map all hotkeys in UI based on the platform [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly map all hotkeys in UI based on the platform. [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)


⚠️ Potential issue | 🟡 Minor
Use “parentheses” (plural) for clarity.
Minor wording nit in the changelog entry.
✏️ Suggested tweak
-- Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)+- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
📝 Committable suggestion
‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)
- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
🤖 Prompt for AI Agents
In `@CHANGELOG.md` at line 12, Update the changelog entry text to use the plural form "parentheses" instead of "parenthesis" for clarity; locate the line containing "Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to "Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

brendan-kellam · 2026-01-23T02:34:53Z

 // Entry point for the MCP server
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { preprocessRegexp } from '@sourcebot/shared';


nit: mcp cannot take a dependency on @sourcebot/shared since we do not publish it to npm

brendan-kellam · 2026-01-23T02:41:27Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

msukkari · 2026-01-23T05:06:16Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

Closing in favor of #788

msukkari · 2026-01-23T01:32:44Z

Weird edge case where if a regex filter like filename/reponame contained a parenthesis the parser would fail. This is because the query language forbids parenthesis in the value since they're used to match against the ParenExpr symbol.

The ideal case is that the agent would be smart enough to wrap the regexp in quotes, which would solve this problem. I've added instructions in the tool call to tell it to do this, but it rarely does. As a result, I've added basic logic to process the regexp before adding it in the query string to wrap it in quotes if a parenthesis is included.

Fixes#771

Summary by CodeRabbit

Bug Fixes
- Properly handle regex filters that include parentheses.
New Features
- Added file path filtering capability to code search functionality.
Documentation
- Updated guidance on using file filters with parentheses in regex expressions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-23T01:33:08Z

Walkthrough

PR addresses issue #771 by implementing proper handling of regex filters containing parentheses. Introduces new preprocessRegexp utility function that wraps values with parentheses in quotes, adds filterByFile parameter to the search_code tool, and applies consistent preprocessing across MCP and web client implementations to prevent query parsing failures.

Changes

Cohort / File(s)	Summary
Regex preprocessing utility `packages/shared/src/query.ts`	New exported function `preprocessRegexp(value: string)` that detects parentheses in unquoted values and wraps them in double quotes to safely handle special characters in regex patterns.
Shared package exports `packages/shared/src/index.client.ts`, `packages/shared/src/index.server.ts`	Added re-exports of `preprocessRegexp` from `./query.js` to make the utility available across package boundaries.
MCP search_code tool enhancement `packages/mcp/src/index.ts`	Extended `search_code` tool with new `filterByFile` parameter (array of strings). Imported `preprocessRegexp` and implemented filtering logic to transform file paths with preprocessing before appending to query as `( file:… )` clauses. Updated descriptions to document new functionality.
Web client tool documentation & preprocessing `packages/web/src/features/chat/tools.ts`, `packages/web/src/features/chat/utils.ts`	Updated tool descriptions to document parenthesis handling requirements. Added preprocessing step in `buildSearchQuery` to transform file and repo filter regexes using `preprocessRegexp` before query composition.
Changelog `CHANGELOG.md`	Added entry under Unreleased/Fixed: "Properly handle regex filters that include parenthesis." Appended reference tag to existing hotkey mapping item.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

feat(ask_sb): Improved search tool ; tools for listing / searching repos ; removed search scope constraint #400: Introduces the foundational regex handling enhancement (preprocessRegexp) that this PR extends with MCP tool integration and file filtering support.
chore(api): Changed the search api to return raw source (instead of base64 encoding) #356: Also modifies the search_code tool in packages/mcp/src/index.ts, though for different functionality (snippet source handling).

Suggested reviewers

brendan-kellam

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding proper handling of regex filters containing parentheses, which directly addresses the fix for issue `#771`.
Linked Issues check	✅ Passed	The PR implements the required fix for issue `#771` by adding preprocessRegexp logic to wrap regex filter values containing parentheses in quotes, preventing parser failures.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing regex filter handling with parentheses. No out-of-scope modifications detected; changes focus on the preprocessRegexp function, its exports, and its integration into search query building.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

packages/web/src/features/chat/tools.ts (1)

142-173: Fix minor typos in the tool description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.`)+ .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.`)

packages/mcp/src/index.ts (1)

24-49: Fix minor typos in schema/description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.")+ .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.")

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 12: Update the changelog entry text to use the plural form "parentheses"
instead of "parenthesis" for clarity; locate the line containing "Properly
handle regex filters that include parenthesis.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to
"Properly handle regex filters that include parentheses.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

coderabbitai · 2026-01-23T01:38:31Z

 ### Fixed
- Properly map all hotkeys in UI based on the platform [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly map all hotkeys in UI based on the platform. [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)


⚠️ Potential issue | 🟡 Minor
Use “parentheses” (plural) for clarity.
Minor wording nit in the changelog entry.
✏️ Suggested tweak
-- Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)+- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
📝 Committable suggestion
‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)
- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
🤖 Prompt for AI Agents
In `@CHANGELOG.md` at line 12, Update the changelog entry text to use the plural form "parentheses" instead of "parenthesis" for clarity; locate the line containing "Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to "Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

brendan-kellam · 2026-01-23T02:34:53Z

 // Entry point for the MCP server
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { preprocessRegexp } from '@sourcebot/shared';


nit: mcp cannot take a dependency on @sourcebot/shared since we do not publish it to npm

brendan-kellam · 2026-01-23T02:41:27Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

msukkari · 2026-01-23T05:06:16Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

Closing in favor of #788

msukkari · 2026-01-23T01:32:44Z

Weird edge case where if a regex filter like filename/reponame contained a parenthesis the parser would fail. This is because the query language forbids parenthesis in the value since they're used to match against the ParenExpr symbol.

The ideal case is that the agent would be smart enough to wrap the regexp in quotes, which would solve this problem. I've added instructions in the tool call to tell it to do this, but it rarely does. As a result, I've added basic logic to process the regexp before adding it in the query string to wrap it in quotes if a parenthesis is included.

Fixes#771

Summary by CodeRabbit

Bug Fixes
- Properly handle regex filters that include parentheses.
New Features
- Added file path filtering capability to code search functionality.
Documentation
- Updated guidance on using file filters with parentheses in regex expressions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-23T01:33:08Z

Walkthrough

PR addresses issue #771 by implementing proper handling of regex filters containing parentheses. Introduces new preprocessRegexp utility function that wraps values with parentheses in quotes, adds filterByFile parameter to the search_code tool, and applies consistent preprocessing across MCP and web client implementations to prevent query parsing failures.

Changes

Cohort / File(s)	Summary
Regex preprocessing utility `packages/shared/src/query.ts`	New exported function `preprocessRegexp(value: string)` that detects parentheses in unquoted values and wraps them in double quotes to safely handle special characters in regex patterns.
Shared package exports `packages/shared/src/index.client.ts`, `packages/shared/src/index.server.ts`	Added re-exports of `preprocessRegexp` from `./query.js` to make the utility available across package boundaries.
MCP search_code tool enhancement `packages/mcp/src/index.ts`	Extended `search_code` tool with new `filterByFile` parameter (array of strings). Imported `preprocessRegexp` and implemented filtering logic to transform file paths with preprocessing before appending to query as `( file:… )` clauses. Updated descriptions to document new functionality.
Web client tool documentation & preprocessing `packages/web/src/features/chat/tools.ts`, `packages/web/src/features/chat/utils.ts`	Updated tool descriptions to document parenthesis handling requirements. Added preprocessing step in `buildSearchQuery` to transform file and repo filter regexes using `preprocessRegexp` before query composition.
Changelog `CHANGELOG.md`	Added entry under Unreleased/Fixed: "Properly handle regex filters that include parenthesis." Appended reference tag to existing hotkey mapping item.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

feat(ask_sb): Improved search tool ; tools for listing / searching repos ; removed search scope constraint #400: Introduces the foundational regex handling enhancement (preprocessRegexp) that this PR extends with MCP tool integration and file filtering support.
chore(api): Changed the search api to return raw source (instead of base64 encoding) #356: Also modifies the search_code tool in packages/mcp/src/index.ts, though for different functionality (snippet source handling).

Suggested reviewers

brendan-kellam

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding proper handling of regex filters containing parentheses, which directly addresses the fix for issue `#771`.
Linked Issues check	✅ Passed	The PR implements the required fix for issue `#771` by adding preprocessRegexp logic to wrap regex filter values containing parentheses in quotes, preventing parser failures.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing regex filter handling with parentheses. No out-of-scope modifications detected; changes focus on the preprocessRegexp function, its exports, and its integration into search query building.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

packages/web/src/features/chat/tools.ts (1)

142-173: Fix minor typos in the tool description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.`)+ .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.`)

packages/mcp/src/index.ts (1)

24-49: Fix minor typos in schema/description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.")+ .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.")

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 12: Update the changelog entry text to use the plural form "parentheses"
instead of "parenthesis" for clarity; locate the line containing "Properly
handle regex filters that include parenthesis.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to
"Properly handle regex filters that include parentheses.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

coderabbitai · 2026-01-23T01:38:31Z

 ### Fixed
- Properly map all hotkeys in UI based on the platform [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly map all hotkeys in UI based on the platform. [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)


⚠️ Potential issue | 🟡 Minor
Use “parentheses” (plural) for clarity.
Minor wording nit in the changelog entry.
✏️ Suggested tweak
-- Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)+- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
📝 Committable suggestion
‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)
- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
🤖 Prompt for AI Agents
In `@CHANGELOG.md` at line 12, Update the changelog entry text to use the plural form "parentheses" instead of "parenthesis" for clarity; locate the line containing "Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to "Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

brendan-kellam · 2026-01-23T02:34:53Z

 // Entry point for the MCP server
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { preprocessRegexp } from '@sourcebot/shared';


nit: mcp cannot take a dependency on @sourcebot/shared since we do not publish it to npm

brendan-kellam · 2026-01-23T02:41:27Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

msukkari · 2026-01-23T05:06:16Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

Closing in favor of #788

msukkari · 2026-01-23T01:32:44Z

Weird edge case where if a regex filter like filename/reponame contained a parenthesis the parser would fail. This is because the query language forbids parenthesis in the value since they're used to match against the ParenExpr symbol.

The ideal case is that the agent would be smart enough to wrap the regexp in quotes, which would solve this problem. I've added instructions in the tool call to tell it to do this, but it rarely does. As a result, I've added basic logic to process the regexp before adding it in the query string to wrap it in quotes if a parenthesis is included.

Fixes#771

Summary by CodeRabbit

Bug Fixes
- Properly handle regex filters that include parentheses.
New Features
- Added file path filtering capability to code search functionality.
Documentation
- Updated guidance on using file filters with parentheses in regex expressions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-23T01:33:08Z

Walkthrough

PR addresses issue #771 by implementing proper handling of regex filters containing parentheses. Introduces new preprocessRegexp utility function that wraps values with parentheses in quotes, adds filterByFile parameter to the search_code tool, and applies consistent preprocessing across MCP and web client implementations to prevent query parsing failures.

Changes

Cohort / File(s)	Summary
Regex preprocessing utility `packages/shared/src/query.ts`	New exported function `preprocessRegexp(value: string)` that detects parentheses in unquoted values and wraps them in double quotes to safely handle special characters in regex patterns.
Shared package exports `packages/shared/src/index.client.ts`, `packages/shared/src/index.server.ts`	Added re-exports of `preprocessRegexp` from `./query.js` to make the utility available across package boundaries.
MCP search_code tool enhancement `packages/mcp/src/index.ts`	Extended `search_code` tool with new `filterByFile` parameter (array of strings). Imported `preprocessRegexp` and implemented filtering logic to transform file paths with preprocessing before appending to query as `( file:… )` clauses. Updated descriptions to document new functionality.
Web client tool documentation & preprocessing `packages/web/src/features/chat/tools.ts`, `packages/web/src/features/chat/utils.ts`	Updated tool descriptions to document parenthesis handling requirements. Added preprocessing step in `buildSearchQuery` to transform file and repo filter regexes using `preprocessRegexp` before query composition.
Changelog `CHANGELOG.md`	Added entry under Unreleased/Fixed: "Properly handle regex filters that include parenthesis." Appended reference tag to existing hotkey mapping item.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

feat(ask_sb): Improved search tool ; tools for listing / searching repos ; removed search scope constraint #400: Introduces the foundational regex handling enhancement (preprocessRegexp) that this PR extends with MCP tool integration and file filtering support.
chore(api): Changed the search api to return raw source (instead of base64 encoding) #356: Also modifies the search_code tool in packages/mcp/src/index.ts, though for different functionality (snippet source handling).

Suggested reviewers

brendan-kellam

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding proper handling of regex filters containing parentheses, which directly addresses the fix for issue `#771`.
Linked Issues check	✅ Passed	The PR implements the required fix for issue `#771` by adding preprocessRegexp logic to wrap regex filter values containing parentheses in quotes, preventing parser failures.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing regex filter handling with parentheses. No out-of-scope modifications detected; changes focus on the preprocessRegexp function, its exports, and its integration into search query building.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

packages/web/src/features/chat/tools.ts (1)

142-173: Fix minor typos in the tool description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.`)+ .describe(`Filter results from filepaths that match the regex. When this option is not specified, all files are searched. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.`)

packages/mcp/src/index.ts (1)

24-49: Fix minor typos in schema/description text.

“expresion” → “expression”, “paranthesis” → “parenthesis”.

✏️ Proposed fix

- .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expresion includes a paranthesis **YOU MUST** wrap this value in quotes when passing it in.")+ .describe("Scope the search to results inside filepaths that match the provided regex expression. By default all files are searched, so **only use this filter if you need to filter on specific files**. **YOU MUST** ensure that this is a valid regex expression and any special characters are properly escaped. If the regex expression includes a parenthesis **YOU MUST** wrap this value in quotes when passing it in.")

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 12: Update the changelog entry text to use the plural form "parentheses"
instead of "parenthesis" for clarity; locate the line containing "Properly
handle regex filters that include parenthesis.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to
"Properly handle regex filters that include parentheses.
[`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

coderabbitai · 2026-01-23T01:38:31Z

 ### Fixed
- Properly map all hotkeys in UI based on the platform [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly map all hotkeys in UI based on the platform. [#784](https://github.com/sourcebot-dev/sourcebot/pull/784)
+- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)


⚠️ Potential issue | 🟡 Minor
Use “parentheses” (plural) for clarity.
Minor wording nit in the changelog entry.
✏️ Suggested tweak
-- Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)+- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
📝 Committable suggestion
‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)
- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)
🤖 Prompt for AI Agents
In `@CHANGELOG.md` at line 12, Update the changelog entry text to use the plural form "parentheses" instead of "parenthesis" for clarity; locate the line containing "Properly handle regex filters that include parenthesis. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)" and change it to "Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)".

brendan-kellam · 2026-01-23T02:34:53Z

 // Entry point for the MCP server
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { preprocessRegexp } from '@sourcebot/shared';


nit: mcp cannot take a dependency on @sourcebot/shared since we do not publish it to npm

brendan-kellam · 2026-01-23T02:41:27Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

msukkari · 2026-01-23T05:06:16Z

I wonder if we could improve our parsing to not throw a exception in the case of a unmatched paren?

Closing in favor of #788

properly quote regexp filters in tool calls if it includes a parenthesis
226fa9c

msukkari requested a review from brendan-kellam January 23, 2026 01:32

This comment has been minimized.
Sign in to view

changelog
48b738f

coderabbitaiBot reviewed Jan 23, 2026
View reviewed changes

brendan-kellam reviewed Jan 23, 2026
View reviewed changes

msukkari closed this Jan 23, 2026

properly quote regexp filters in tool calls if it includes a parenthesis
226fa9c

msukkari requested a review from brendan-kellam January 23, 2026 01:32

This comment has been minimized.
Sign in to view

changelog
48b738f

coderabbitaiBot reviewed Jan 23, 2026
View reviewed changes

brendan-kellam reviewed Jan 23, 2026
View reviewed changes

msukkari closed this Jan 23, 2026

properly quote regexp filters in tool calls if it includes a parenthesis
226fa9c

msukkari requested a review from brendan-kellam January 23, 2026 01:32

This comment has been minimized.
Sign in to view

changelog
48b738f

coderabbitaiBot reviewed Jan 23, 2026
View reviewed changes

brendan-kellam reviewed Jan 23, 2026
View reviewed changes

msukkari closed this Jan 23, 2026

properly quote regexp filters in tool calls if it includes a parenthesis
226fa9c

msukkari requested a review from brendan-kellam January 23, 2026 01:32

This comment has been minimized.
Sign in to view

changelog
48b738f

coderabbitaiBot reviewed Jan 23, 2026
View reviewed changes

brendan-kellam reviewed Jan 23, 2026
View reviewed changes

msukkari closed this Jan 23, 2026

properly quote regexp filters in tool calls if it includes a parenthesis
226fa9c

msukkari requested a review from brendan-kellam January 23, 2026 01:32

This comment has been minimized.
Sign in to view

changelog
48b738f

coderabbitaiBot reviewed Jan 23, 2026
View reviewed changes

brendan-kellam reviewed Jan 23, 2026
View reviewed changes

msukkari closed this Jan 23, 2026

properly quote regexp filters in tool calls if it includes a parenthesis
226fa9c

msukkari requested a review from brendan-kellam January 23, 2026 01:32

This comment has been minimized.
Sign in to view

changelog
48b738f

coderabbitaiBot reviewed Jan 23, 2026
View reviewed changes

brendan-kellam reviewed Jan 23, 2026
View reviewed changes

msukkari closed this Jan 23, 2026

properly quote regexp filters in tool calls if it includes a parenthesis
226fa9c

msukkari requested a review from brendan-kellam January 23, 2026 01:32

This comment has been minimized.
Sign in to view

changelog
48b738f

coderabbitaiBot reviewed Jan 23, 2026
View reviewed changes

brendan-kellam reviewed Jan 23, 2026
View reviewed changes

msukkari closed this Jan 23, 2026

properly quote regexp filters in tool calls if it includes a parenthesis
226fa9c

msukkari requested a review from brendan-kellam January 23, 2026 01:32

This comment has been minimized.
Sign in to view

changelog
48b738f

coderabbitaiBot reviewed Jan 23, 2026
View reviewed changes

brendan-kellam reviewed Jan 23, 2026
View reviewed changes

msukkari closed this Jan 23, 2026

	- Properly handle regex filters that include parenthesis. [#786](https://github.com/sourcebot-dev/sourcebot/pull/786)
	- Properly handle regex filters that include parentheses. [`#786`](https://github.com/sourcebot-dev/sourcebot/pull/786)

Uh oh!

Conversation

msukkari commented Jan 23, 2026• edited by coderabbitai BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

This comment has been minimized.

coderabbitaiBot commented Jan 23, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested reviewers

Uh oh!

coderabbitaiBot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitaiBotJan 23, 2026

Choose a reason for hiding this comment

Uh oh!

brendan-kellamJan 23, 2026

Choose a reason for hiding this comment

Uh oh!

brendan-kellam commented Jan 23, 2026

Uh oh!

msukkari commented Jan 23, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

msukkari commented Jan 23, 2026• edited by coderabbitai BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

This comment has been minimized.

coderabbitaiBot commented Jan 23, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested reviewers

Uh oh!

coderabbitaiBot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitaiBotJan 23, 2026

Choose a reason for hiding this comment

Uh oh!

brendan-kellamJan 23, 2026

Choose a reason for hiding this comment

Uh oh!

brendan-kellam commented Jan 23, 2026

Uh oh!

msukkari commented Jan 23, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

msukkari commented Jan 23, 2026• edited by coderabbitai BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

msukkari commented Jan 23, 2026•
edited by coderabbitai Bot
Loading

coderabbitaiBot commented Jan 23, 2026•
edited
Loading

msukkari commented Jan 23, 2026•
edited
Loading

msukkari commented Jan 23, 2026•
edited by coderabbitai Bot
Loading

coderabbitaiBot commented Jan 23, 2026•
edited
Loading

msukkari commented Jan 23, 2026•
edited
Loading

msukkari commented Jan 23, 2026•
edited by coderabbitai Bot
Loading

coderabbitaiBot commented Jan 23, 2026•
edited
Loading

msukkari commented Jan 23, 2026•
edited
Loading

msukkari commented Jan 23, 2026•
edited by coderabbitai Bot
Loading

coderabbitaiBot commented Jan 23, 2026•
edited
Loading