Improve Multi-Repository Support Without Worktree Dependency

**Mood:** 😊
**Category:** Requests and ideas

It would be useful to provide an option to disable worktree usage when working with local folders. My setup contains a mix of GitHub and Azure DevOps repositories, including both multi-repository and monorepo scenarios.
One possible approach would be to prompt the user to create a branch with the same name across all selected repositories instead of automatically relying on worktrees.
Additionally, when worktrees are used, the agent currently does not create a dedicated folder for each repository under the worktree directory. As a result, repository discovery and search do not work reliably because not all repositories are present in the worktree location. I often need to explicitly tell the agent where to look for specific repositories.
Previously, I manually cloned all repositories required for a task into a single directory, and the search functionality worked much better without any additional guidance. It would be great if the worktree experience could achieve the same level of repository visibility and searchability.

---
| Field | Value |
| --- | --- |
| App version | 1.0.16 |
| Theme | GitHub |
| Path | /chat |

该 issue 涉及 /chat 流程和本地多仓库 worktree。使用 GitHub 和 Azure DevOps 仓库复现一个任务，包括多仓库和 monorepo 设置，然后检查仓库如何放置在 worktree 目录中以及如何被发现。完成的标准是用户可以禁用 worktree，或获得特定于仓库的 worktree 文件夹，使搜索能够看到所有仓库，并定义 branch 的行为。

由索引模型根据 Issue 内容生成。