Feature request: Multi-repo workspace support

Feature Request

Problem

When working on projects that span multiple repositories, there's no way to open a single Claude Code session that has context across all of them. Currently the workarounds are running separate terminal sessions or using git worktrees, but neither provides a unified experience.

Tools like Cursor offer a workspace feature that allows working across multiple repos simultaneously with shared context.

Proposed Solution

A workspace mode where Claude Code can be aware of and operate across multiple repositories in a single session. For example:

claude --workspace /path/to/repo-a /path/to/repo-b

This would allow:

• Searching and reading code across all repos in the workspace
• Making coordinated changes across repos (e.g., updating an API in one repo and the client in another)
• Understanding cross-repo dependencies and relationships

Current Workarounds

• Running multiple Claude Code sessions in separate terminals (no shared context)
• Git worktrees (isolated branches, same repo only)
• Agent teams (experimental, high token usage, not designed for multi-repo)

Use Case

Microservice architectures, monorepo-adjacent setups, and library + consumer repo combinations where changes often need to be coordinated across repositories.