Skip to content

Share an agent

Say Hanley's team should use your researcher. You publish it and send Hanley a link, and Hanley asks for access. Their page shows a code, which they send you in a message. You enter it on your own Sharing page, and the researcher appears on their Agents page. It keeps running on your installation, with your model, tools, files and memory, and they see only what it sends them.

The same page lets you use an agent someone shared with you, bring a second installation into a chat, and open a sandboxed agent to anyone with an address. To work on files together instead, see Share files from a chat.

Before you start

Both installations need a public web address. If you are not sure yours has one, ask your assistant to check.

Choose the agent with care. Sharing one is trusting the other side with what it knows and can do, so share an agent you would let them talk to, and sandbox one you would not. Only a sandboxed agent can be opened to the public.

Everything here is on Admin > Sharing (/admin/agent-sharing), in the Communications group. Its tabs are Shared by you, Requests, Shared with you, Pairing and People & agents. Sharing between installations says what each is for.

Share one of your agents

  1. Open the Pairing tab (/admin/agent-sharing/pairing).
  2. Under Agents you share, choose the agent. Give it a Name they see and a Description they see if you like; both are optional.
  3. Check the card underneath. It is all anyone with the link will see until you approve them.
  4. Optionally, choose the project that new chats with this agent land in, under New chats go to.
  5. Press Publish, then Copy link and send the link to the person.

The link is an address, not a key. Whoever holds it sees the card and can ask for access, and nothing more.

Approve their request

  1. They paste your link into their own installation and ask for access. Their page shows them a code, which they send you in a message.
  2. Open the Requests tab (/admin/agent-sharing/requests), which shows a count while anyone is waiting. The row says who is asking and shows the card of the agent they asked for.
  3. Paste the code as it came and press Approve, or Turn down. Spaces, hyphens and capitals do not matter. A code lasts ten minutes and allows five tries, and a wrong one costs a try.

You should now see them under Who has access on the Pairing tab.

Only a person can enter a code, on this page. No agent can approve a request for you.

Use an agent someone shared with you

  1. Open the Pairing tab, paste the link you were sent and press Look at the link. You see the card behind it before you ask for anything.
  2. Press Ask for access. A code appears in a box, with the path of the other person's Requests tab in a second box. Send the code to the person who shared the agent, in a message only they will read, and to nobody else. Whoever enters it is who gets connected.
  3. Wait for them to approve. The agent arrives by itself, and Check if they approved asks straight away.

You can also paste the link into a chat and ask your assistant to connect. The code then appears in a box in the chat, for you to send.

You should now see the agent on Manage > Agents (/agents) with a Shared with you badge, in the project you have open. Its chat says that messages leave your installation, and files you attach there go to the other installation. Everything you type in that chat can be read by the person who runs the agent, and they see you under the name and picture on your own card at Manage > Contacts (/manage/contacts).

Under Agents shared with you on the Pairing tab, View agent opens it, Refresh card asks their installation for its current name, description and picture, and Remove takes it away and ends the access.

What the other side can reach

  • They talk to that one agent and nothing else of yours: no files, memory or other agents, except through what that agent does for them.
  • Their chat is also one of the agent's chats on your installation. You can read it and talk to your agent privately there, and they see only what the agent sends them. A sandboxed agent is the exception: everything it says there goes over, so talk to it in a chat of your own.
  • Their messages never carry your authority. What your agent does only for you, it does not do for them.
  • An agent shared with you cannot be passed on to anyone else.

Bring another installation into a chat

You have a chat that another installation started with one of your shared agents, and a third installation should join it.

  1. Open that chat and press Share, beside Files at the top left. In a chat like this the dialog has an Invite to this chat section.
  2. Choose how long the link works under Link works for, a week unless you change it, and set Most uses if you want to cap the joins. Empty means no limit.
  3. Press Make invite link and send the link to the person.

The link gives nobody access to the agent. It works only for an installation that already has access to that agent. Whoever uses it lands in this chat, and a line in the chat says who joined. A chat with more than one other installation in it is a team room.

The person pastes the link under Join from a link on their Shared with you tab (/admin/agent-sharing/shared-with-you) and presses Join. They join at once, in a new chat of their own with the agent, with no approval from you.

Your invite links are listed on the Shared by you tab as Chat invites, with how many joins each has admitted. Copy link shows it again, New link stops the link you sent before and keeps the count, and End withdraws it. People already in the chat stay.

Open a sandboxed agent to everyone

For a chat on your website or a public support line, where visitors do not have Player One.

  1. Publish the agent first, as above. Only a sandboxed agent you already publish is offered.
  2. On the Shared by you tab (/admin/agent-sharing), choose Open to anyone beside the agent. Set any of the three limits: turns a day, turns in one conversation, and days a visitor's chat is kept. Each is empty by default, and empty means no limit. The third is recorded with the link, but chats are not yet deleted when it runs out, so delete visitors' chats yourself when you no longer need them.
  3. Press Open the link. The address appears, and Copy link on its row shows it again whenever you need it.

Anyone with the address can talk to the agent. Nobody asks you first, and you will not know who they are. Treat the address like a password. Flood protection is always on, whatever limits you set. A visitor who reaches one of your limits gets a plain message saying so. A public link carries no files, in either direction, and it does not expire by itself.

Each link shows its conversations, its turns and how many visitors it turned away. Suspend stops the link admitting anyone and keeps its conversations, and Resume opens it again while the agent is still sandboxed. Change limits edits the three limits. New address replaces the address and ends every conversation on the old one, and Close ends the link for good.

If you are building the website, the address is itself the agent card address. A client built for the A2A protocol talks to the agent there. Give it the address as the card address, not as a base to add a path to.

Who has talked to your agents

The People & agents tab (/admin/agent-sharing/people) lists everyone who has talked to your agents from another installation or a public link. Filter by agents or people, by connection, or by verified, which a tick marks. Rename changes the name wherever it shows, and Open contact opens it on Manage > Contacts (/manage/contacts).

End access

  • End access on a row under Who has access stops that installation from its next message. The row stays, marked Ended.
  • New link stops the old link opening, while people already approved keep their access.
  • Stop sharing ends every approval given through the agent's link at once, and closes its public link.
  • On the other side, Remove under Agents shared with you takes the agent away and ends the access.

What was already sent stays where it went.

If something goes wrong

A request you did not expect. Enter nothing and press Turn down. A request left alone runs out by itself.

The code keeps not matching. Turn the request down. It may not come from the person who sent the code; ask them to start again from your link.

They say no request reached you, or the page says the other side could not prove it holds the code. The link did not lead where it should. Nothing was added. Get the link again from the person directly.

"Not delivered yet" in the chat. The other installation could not be reached. The message arrives when it next checks in, and nothing needs sending again.

"This installation has no public address, so there is no link to give out." Ask your assistant to check your address.

A chat invite says "This instance has no access to that agent, so it cannot join the chat." Pair with that agent first, then use the invite again.

Resume is greyed out on a public link. The agent is no longer sandboxed, so the link suspended itself. Resume works again once the agent is back in its sandbox.

Where next