Sharing between installations

You have a lease open in a tab and Hanley needs to work on it with you. You press Share, turn the file on and send Hanley a link. Hanley pastes it into their own Player One, you approve them from a card in your chat, and each of you now has your own copy. When Hanley's agent has a change, it sends you the file with a note on what changed. Hanley never sees your chat, your memory or any other file of yours.

That is one of four ways two Player One installations work together. They differ in what is shared, who gets in and who says yes. Everyone in the first three runs Player One. Only a public link is for visitors who do not.

The four ways

A share of files. For working on documents together. You turn on files from one chat, send the link and approve each installation that asks to join. Every member keeps its own copy of each file and sends changes on purpose. A files share needs no pairing first. Share files from a chat has the steps.

A paired agent. For lending someone one of your agents for good. You publish the agent and send a link. The other person asks for access, gets a code and sends it to you, and you enter it on your own Sharing page. The agent keeps running on your installation and they talk to it from theirs. Share an agent has the steps.

A chat invite. For bringing a second installation into a chat that another installation started with one of your shared agents. The link works only for an installation that already has access to that agent. A chat with more than one other installation in it is a team room.

A public link. For a chat on your website or a support line, where visitors have no Player One. It opens a sandboxed agent to anyone with the address, with no approval of each visitor.

	Share of files	Paired agent	Chat invite	Public link
Who gets in	Installations you approve one by one	One installation at a time, after you enter its code	An installation that already has access to that agent	Anyone with the address
What they get	Their own copy of each file you turn on	Messages with that one agent	A place in that one chat	Messages with that one sandboxed agent, and no files
Your say	You approve each one on a card	You enter each code	You make the link, limit it and end it	You set limits and can close it

What crosses, and what never does

What crosses depends on the way.

A share of files: the files you turned on, sent on purpose with a note. The words your agent chooses to send to the members. Who is in the share, with their names, faces and installations. And whether your agent is working, which you can switch off.
A paired agent: the messages between the other side and that one agent, and what the agent sends back. Its ordinary replies in your own chat with it stay with you. A sandboxed agent is the exception, because everything it says there goes over. Files attached in the chat travel with the message.

What never crosses:

Your chats. In a files share the chat stays private to each installation. Nothing you type there, and nothing your agent replies, reaches a member unless it is sent.
Your memory, your other files and your other agents. The other side reaches only what you shared, and a paired agent answers as itself, so share one you would let them talk to.
Your vault and your authority. Stored values are never shown to anyone, so they cannot cross, and a file whose name suggests secrets, such as .env, cannot be turned on. A guest's messages never carry your authority: what your agent does only for you, it does not do for them.
Writes to your files. A file that arrives lands in a folder of its own, never over your copy. Your agent reads it and decides what goes into your copy, going by what you have told it.

Anything a member's agent sends carries a Foreign agent label wherever you see it. Your agent treats it as information to weigh, never as an instruction, because another installation's agent can send anything, on purpose or because someone steered it.

Who has to say yes

Only a person. A link is an address, not a key: whoever holds it can ask, and that is all.

Joining a files share: you answer on the card in the chat, in the bell, or on the Requests tab. No agent can answer for you.
Pairing: the person who owns the agent enters the code on their own Requests tab. The code is made on the asking side and never sent to your installation, so it reaches you only because the other person gives it to you. No agent and no tool can enter it.
A public link and a chat invite: you make them, and you choose their limits. They do not ask about each visitor.

Your agent can suggest a share, ask to join one or open a public link, but each of those waits for a card you approve. It can always stop sharing, leave or end a share on its own, and says so in the chat when it does.

How access ends

A share of files: Rotate link stops the old link, Remove takes out one member, End share ends it for everyone, and a member can Leave. A share also ends when its time runs out: 1 day, 7 days, 30 days or no expiry.
A paired agent: End access stops one installation and Stop sharing stops everyone. On the receiving side, Remove takes the agent away.
A chat invite: End withdraws the link. People already in the chat stay.
A public link: Suspend, New address and Close.

Each takes effect from the next message. What was already sent stays where it went, including each member's copy of the files.

Words you will meet

Owner. The installation that made a share. It holds the link, approves who joins, and can remove members or end the share.
Member. An installation in a share, the owner included, each with its own agent and its own copy. A share holds up to 50.
Copy. A member's own version of a file. Only that member's agent or person changes it.
Send. A file as it is now, with a note on what changed and why, and a summary of the changes. Saving a shared file sends nothing.
Wake. A member's arrival never starts a turn in your chat unless you choose: Wake now for once, Always wake for a member from then on.
Pairing. The standing kind of sharing, where one agent stays shared with another installation until someone ends it.

Where it lives

Admin > Sharing (/admin/agent-sharing), in the Communications group, has five tabs.

Shared by you (/admin/agent-sharing): every share you own, with Copy link, New link and End.
Requests (/admin/agent-sharing/requests): people asking to join your shares, and pairing requests with the code to enter.
Shared with you (/admin/agent-sharing/shared-with-you): the shares you joined, and where you paste a link to join one.
Pairing (/admin/agent-sharing/pairing): publish an agent, ask for someone else's, and see who has access.
People & agents (/admin/agent-sharing/people): everyone who has talked to your agents from another installation or a public link.

In a chat, the Share button beside Files is the way into a share of that chat's files. Members appear as faces beside the composer, and a shared file's tab has its own Sharing menu.

Share files from a chat and Share an agent have the steps. Vault and sandboxing covers what a sandboxed agent can and cannot reach, and Agents covers the ordinary kind.