[FEATURE] Let Claude instances share knowledge by link and communication instead of copying context

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

When I run an agent team, knowledge only moves between teammates by
copying it. A teammate that spent 60k tokens understanding the auth
module can either send a summary paragraph over SendMessage — lossy, and
the recipient can't ask follow-ups against the source — or write
everything to a file that other teammates read in full. There's no way to
pull just the part you need.

Two costs follow from that. If four teammates need the same spec, the
team tokenizes it four times. And a teammate's understanding dies with it:
once it goes idle, is shut down, or gets compacted, the only way to
recover what it learned is to have kept it alive and spend a turn asking.

In practice this means I babysit the handoffs. I re-explain to teammate B
what teammate A already figured out, and I keep agents alive purely
because they're holding context I might need. The larger the team, the
more of my attention goes to moving information around rather than to
the work.

Proposed Solution

A teammate that knows something publishes a link — context://researcher/auth-module
— and that's all anyone has to pass around.

When I give another teammate that link, or it receives one, it works out
what it needs and asks the other instance in the background. Several
rounds of questions if necessary. I don't see the exchange, I just get an
agent that now knows what it needed to know, without me re-explaining it
or the other agent dumping its whole context.

The link should be persistent — still usable later in the session, or in
a resumed one, not just while both agents happen to be running.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_