[FEATURE] Multi-repository communication and persistent cross-session memory

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Currently, Claude Code operates within the scope of a single repository and local session. It cannot communicate with agents or processes running in other repositories, nor can it share context across different terminal sessions seamlessly. This limits its usefulness for microservice architectures, monorepos divided into separate working trees, or complex workflows that span multiple dependent projects.

Proposed Solution

Cross-Repo Context: Allow Claude Code to open, read, or pass messages to another repository's agent if specified by the user (e.g., a command like /connect-repo ../other-service).

Persistent Sessions: Introduce a mechanism where Claude can save, reference, or resume context from a previous session or a parallel running session in another terminal window.

Inter-Agent Communication: Enable a "mesh" or broker system where an instance of Claude working on a frontend repo can programmatically query or send a webhook/message to an instance of Claude working on a backend repo.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

I am debugging an API contract change. I want Claude Code in my frontend repo to ask the Claude Code instance running in my backend repo what the exact expected JSON schema is, and then automatically update the TypeScript types in the frontend.

Additional Context

This features reduces admin overhead when working on multiple projects that are related.