Shared Drives For Agents: Everything Available Runs On Your Identity

Summary

A survey of ways to give two agent sessions a shared file area — and three findings that matter more than the option list. Every available option runs on your identity, so a rogue session reaches everything every other session can reach and nothing can be attributed to an agent; the only real granularity is segregation (a dedicated drive per agent), not scoping; and nothing surveyed supports per-agent public and private keys. Three requirement rows come back empty across the entire market, which is the finding rather than an omission — and the first concrete, evidenced instance of the site's thesis.

Key concepts

• Granularity by segregation — when possession of access is binary, granularity comes from the shape of what you store
• Everything acts as you — connector authorisation is per identity; every session is indistinguishable from you
• Attribution from content, not platform — own paths and signed writes — a design decision, not a feature to wait for
• Curation destroys provenance — memory platforms resolve conflicting facts on write, which erases who said what, when

Key ideas

• The ecosystem's dominant advice is the opposite of the question: isolate parallel sessions, don't share.
• The scope paradox: the safe scope can't read your existing files; the useful scope reads everything and can't be narrowed.
• No option offers micropayments or per-call billing, so per-agent economics are not currently purchasable.
• The empty rows are standing refutation targets — anybody who fills one improves the research.

On this site

Presented as a research page at ../research/shared-drives.html; its findings propagate through the thesis, Hope, method and options pages.

Infographic

Read the document