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 |

La issue riguarda il flusso /chat e i worktree locali per più repository. Riproduci un’attività usando repository GitHub e Azure DevOps, includendo configurazioni con più repository e monorepo, quindi verifica come i repository vengono collocati e individuati nella directory dei worktree. Il lavoro è completato quando gli utenti possono disabilitare i worktree o ottenere cartelle di worktree specifiche per repository, in modo che la ricerca veda tutti i repository, con il comportamento dei branch definito.

Scritto dal modello di indicizzazione a partire dal testo della issue.