Letting your team see what your agent writes

You set an agent on something the team is waiting for: the research for Monday, a release checklist, the notes from a customer call. The team sees it when you copy it out, into a document or a chat, and the copy is behind from the moment the agent writes its next line.

Yes, if the agent writes into one branch of your outline: open that branch’s menu, choose Share…, and send your colleague a view or edit link or an email invite. Once the branch is in their Pando, they see the agent’s bullets arrive while Pando is open on their screen, and its chip pulses in their top bar as it writes.

Set it up

Connect the agent as a connector, or with the key of an agent you create under Agents and API keys. A key from Make a key writes as you, and your colleague then sees your chip, not the agent’s. On Claude Team and Enterprise plans an Owner adds the custom connector first. Your colleague connects nothing: a link opens in a browser.

Sharing the branch

• Tell the agent which branch to write in. A share covers one bullet and everything under it and, in the Share sheet’s own words, "nothing beside it".
• Open that bullet’s menu and choose Share…. Only a bullet you may edit can be shared: in your own outline the menu shows Share… on every bullet, and on a branch you were lent to view the link or invite is refused.
• Make a view link or an edit link. Anyone holding it opens the branch without an account, and Show in my Pando lets them sign in and keep it in an outline of their own.
• Or, under “Or invite somebody by email”, type their address and choose Invite them to view or Invite them to edit. Pando does not send the mail; it gives you a link to pass on. The invite becomes their permission the next time they sign in with that address, so a colleague who is already signed in signs out and in again. An unused invite expires after 30 days and stays listed, so you can invite them again.

What your colleague sees

Once they have kept the branch or taken the invite:

• The branch in their sidebar under Shared with me, with your name and a pencil or an eye for edit or read-only. Opened by its link or its own address, the branch also carries a band that reads "You may edit" or "Read-only", then "shared with you by" and your name; opened from the sidebar inside their own outline, it carries none.
• New bullets as they land. Every accepted write rings your account, from the app, the API or an agent over MCP, and their open Pando fetches the branch at once. A tab in the background catches up after it comes back to the front, at the next write in your outline or within about a minute.
• Your agent’s chip in their top bar: its initial in a dashed ring, pulsing for four seconds after each write. A tap says "An agent on this outline", then its name and "is writing… It is an agent key, writing over MCP." A connector carries its client’s name, such as Claude.

Who wrote it: only while it is happening

The chip is all the attribution a screen shows. Pando records who made each change, but nothing on a bullet names its writer, so four seconds after the last write a line your agent wrote and a line you typed look the same. The Changes view shows what changed and when, not who, and only in the reader’s own outline, not in a branch lent to them.

If the team needs to know which lines are the agent’s, give it a branch of its own and share that one to view. A connector approved to read and write starts able to write anywhere in your outline, so hold it to that branch: open the branch, open Agents and API keys in Settings, tap the agent’s row under Your agents, and press Let it reach only “…”, the bullet you are in. It then reaches that branch and nothing else.

Names reach further than the words

Your account rings on every write anywhere in your outline. So a colleague holding one branch sees your agent’s chip pulse when it writes somewhere else, sees yours while you have your outline open, and sees anybody else you lent a branch to while that person has it open. With “Notify me when others write” on, those writes also reach them as a notification with the writer’s name while their Pando tab is out of sight. The changes themselves are cut, one at a time, to the bullets they may view.

What they can do with it

• With view, read it. There is no button to ask for more, so they ask you.
• With edit, add, change, move and delete anything inside the branch, and make links and invites of their own for it, which show in your Share sheet marked "made by" and their name.
• No lock holds them: a lock against agents only is not felt by a person, and a person with edit may take a lock off. If the branch must not change, share it to view.

To take it back, open the same sheet: under “Who else can see it” each person has a Remove row, and their open Pando drops the branch with a note that you took it back. Revoking a link does not end a branch somebody kept through it; the sheet says so and points at Remove. A connector that still reaches your whole outline is listed there too, and Remove on it takes the whole outline from it, not only this branch. To keep it to this branch instead, press Let it reach only “…”, the bullet you are in, on its row under Your agents in Agents and API keys.

Your agent’s reach

Sharing is about people. A connector you approve starts with your whole outline whether you share anything or not, and a link or an invite does not change what it reaches. To give it one branch and nothing else, use Let it reach only “…”, the bullet you are in, on its row under Your agents in Agents and API keys. Cursor calls a project’s .cursor/mcp.json "shared with your team", but the entry from the setup above carries only the address: each colleague who signs in approves the connector in Pando for their own outline, not yours.

When this is the wrong tool

• You need to see afterwards which lines the agent wrote. Pando names the writer while it writes, and no screen names it afterwards.
• The team should hear the moment the agent finishes, wherever they are. A notification to a closed app goes only to the owner of the outline, so a colleague with Pando closed sees the work when they next open it.
• Your colleagues want their own Claude or ChatGPT to read the work. Their connectors reach their own outline, and in Pando a grant reaches down a branch, not across into another account, so a branch you lent them is out of reach.
• Everyone’s agents should work in one space as equals. Here one person’s outline lends branches to the others, and a colleague’s tab follows at most five lent branches live.

What it costs

Nothing. Sharing is in the free plan with every other feature: 1,000 bullets and no payment card. What anyone writes in the branch you shared, your colleague or your agent, counts toward your account, not theirs.

Deeper

• Seeing what your agent wrote, while it writes it
• Keeping an agent out of the rest of your notes

Connect an agent, about two minutes · The twelve tools · Which note apps an agent can reach · Who runs this