What your team sees

View as Markdown

What a teammate can read of your sessions and what never leaves your account, so you can decide which folders to share. It holds from Yield 0.3.4; yield status shows the version on each computer.

In short: a folder you have not shared is yours alone. A shared folder’s sessions show the team who, what and which files. What you and the agent said reaches a teammate in two ways, both through a secret filter: the session’s last turns when you hand it to them, and, from Yield 0.3.9, one turn’s prompt and final reply when they ask yield why about a file that turn wrote.

  YOUR COMPUTER
  +---------------------------------------------------+
  |  Claude Code or Codex, in a shared folder          |
  |  the capture service reads each line as written    |
  +----------+----------------+-----------------+------+
             |                |                 |
     every line, as written   |  after each     |  only on a handoff:
             |                |  turn           |  the last 3 turns,
             v                v                 v  through the filter
  YOUR PERSONAL ACCOUNT   THE ORGANIZATION          THE TAKER
  +------------------+   +--------------------+   +-------------------+
  | the transcript,  |   | who, title, state, |   | the excerpt, read |
  | not redacted;    |   | files written;     |   | only by you and   |
  | only you read it |   | the folder's files |   | whoever takes it  |
  +------------------+   | as snapshots;      |   +-------------------+
                         | from 0.3.9, each   |
                         | turn's prompt and  |
                         | final reply, after |
                         | the secret filter, |
                         | for a member's why |
                         +--------------------+
                          every member reads it

A folder you have not shared

Every session is captured into your personal account. A session in a folder you have not connected to an organization, and every session you started in a folder before you connected it, is never visible to a teammate, not even its title. A handoff of it can go only to you.

A shared folder: metadata only

After yield connect --account <organization> and your yes on that computer, each session you start in the folder is the team’s. Every member of the organization can read:

• who started it, and its Project;
• its title, made from the folder and the files it touched, never from what you typed;
• its state (running, waiting, idle or ended) and since when;
• the files each turn wrote, as paths relative to the folder;
• the folder’s files after each turn, as snapshots in the team Project’s repository.

A teammate’s yield ps, yield context and yield files never show your prompts, the agent’s replies, tool calls or their output. Before Yield 0.3.9 neither does yield why; from 0.3.9 it shows one turn’s prompt and final reply (below). The organization’s records of the session also name the agent, the git branch, the working directory within the folder and a random handle for your computer, never its name, its id or any path outside the folder.

A handoff carries your last turns

A shared session’s transcript stays in your personal account. When you hand it to a teammate, your computer attaches an excerpt for the taker: the last 3 turns, each message cut at 4,000 characters, at most the newest 65,536 characters in all, after the secret filter. Tonbo returns it only to you and to whoever takes the handoff, and checks that they are still a member on every read.

A teammate’s yield why on a file

From Yield 0.3.9, when a turn of a shared session writes files, your computer stores one excerpt of it with the organization: the turn’s prompt and the agent’s final reply, after the secret filter, each cut at 6,000 characters at most, with the paths the turn wrote. A teammate’s yield why <path> --account <organization> returns, for each of your turns that wrote that file, its excerpt, marked as a teammate’s.

Tonbo returns one turn’s excerpt at a time and only for a path that turn wrote, checks on every read that you and the reader are both still members, and has no way to list them. Turns captured by 0.3.8 or earlier have no excerpt, and one that fails to send is not sent again. Beyond the two excerpts, your transcript, tool calls and their output included, reaches a teammate only through a handoff of the session itself.

The secret filter

It runs on your computer over a team handoff’s excerpt and, from 0.3.9, each team turn’s yield why excerpt before they leave, and replaces each match with [redacted:<rule>]. Its rules, in order:

It matches patterns, so a secret in a shape it does not know passes through. Treat both excerpts as text your teammates will read.

Your own sessions are not redacted

Your personal account holds every captured line as the agent wrote it, secrets included, and a handoff to yourself carries it unfiltered. Only you read it. To keep something out, yield pause before it or yield exclude the folder (Personal loop); what was captured stays, since the Alpha has no command to delete a session.

Folders shared before 0.3.4

Yield 0.3.3 and earlier sent a shared session’s lines, through the same secret filter, to the organization. Those lines stay where they were sent, and through yield only their author reads them; from 0.3.4 a session’s next lines go to your personal account. Upgrade every computer that captures a shared folder by running the installer again.

What Tonbo measures

During the Alpha, yield records a few content-free measures on your personal account, such as how long a taken handoff waits for its first turn and which yield continue candidate you picked: numbers, flags and fixed words, never a task, prompt, path or reason. TONBO_YIELD_METRICS=off turns them off.