Skip to content
Install

Share a machine

Sharing lets other people in your organization work on a machine with you, or look at what an agent did without access to the machine. Share a machine in one of two ways:

  • Invite someone to the machine as a guest or a read-only guest. They open the workspace and work alongside you.
  • Create a read-only link to one session or to every session. The person sees the transcript and the diff, and has no other access to the machine.
RoleLabel in the workspaceWho
HostHostThe person who created the machine. Superadmins have the same access.
GuestGuestSomeone the host invited with Collaborate access.
Read-only guestRead onlySomeone the host invited with Watch access.
Organization adminNoneAn admin of the machine’s organization who was not invited.

An organization admin who is also invited has the invited role, and can also start, stop, and delete the machine.

ActionHostGuestRead-only guestOrganization admin
See the machine in lists: name, status, runner, ownerYesYesYesYes
See sessions, transcripts, comments, diffs, files, and who is hereYesYesYesNo
Watch other people’s terminals and script outputYesYesYesNo
Open previewsYesYesYesNo
Prompt the agent and send reviewsYesYesNoNo
Comment with /chatYesYesNoNo
Edit, create, rename, and delete filesYesYesNoNo
Open their own terminalsYesYesNoNo
Start and stop run scriptsYesYesNoNo
Create, archive, and delete sessions and their branchesYesYesNoNo
CommitYesYesNoNo
Push, pull, open pull requests, and merge, with their own GitHub accountYesYesNoNo
Start the machineYesYesNoYes
Stop or delete the machine, and retry failed changesYesNoNoYes
Connect over SSH and open editor linksYesNoNoNo
Invite people, change roles, and remove peopleYesNoNoNo
Change machine settings and clone repositoriesYesNoNoNo
Attach projects and deploy preview environmentsYesNoNoNo
Create and revoke read-only links, and fork the machineYesNoNoNo

The server enforces these rules on each request, each terminal, and each live message. The server drops a read-only guest’s edits to a shared file.

Anyone can leave a machine they were invited to.

You must be the host. You can invite people in the machine’s organization only, and a machine can be shared with up to 50 people.

  1. In the workspace title bar, select Share.
  2. Select Invite people.
  3. Enter a name or an email address, and select the person. You can add several people.
  4. Select Next.
  5. Select Collaborate or Watch.
  6. Select Invite.

The first time the person opens the machine, a notice states whose machine it is. They select Continue to proceed.

To change a role or remove someone, select Share, then open the menu next to their name. A role change or removal takes effect immediately. Their open workspace disconnects, and their terminals and previews stop within seconds.

Copy link for guests in the session menu copies a link to the session. The link works only for people who are on the machine.

  • The agent is the host’s. A guest’s prompts run on the host’s Claude subscription, inside the host’s machine. A guest can ask the agent to do anything the agent can do.
  • The files are the host’s. A guest with a terminal can read anything on the machine. This includes agent tokens, attached project env files, and the GitHub credential the agent uses.
  • Terminals can be watched. The host and guests can watch each other’s terminals.
  • The agent’s Orchard access is the host’s. The agent holds an Orchard MCP token for the host, limited to the machine’s organization. A guest can read this token and act as the host in that organization until the token changes.
  • A guest’s GitHub token is used on the host’s machine. A push from the workspace receives the token for that one command. In a guest’s own terminal, the token stays in the shell’s environment while the terminal is open. The host, other guests, and the agent can read it there.
  • Organization admins cannot read a machine’s contents. An organization admin can see that the machine exists, and can start, stop, or delete it. An organization admin cannot see its sessions, transcripts, files, diffs, terminals, previews, or members without an invitation. Superadmins have host access.

When you remove a guest or make them read-only, Orchard does the following:

  1. It ends their terminals.
  2. It revokes the agent’s Orchard token and issues a new one. The agent’s Orchard tools pick up the new token when the machine next starts.
  3. It changes the agent server password and the SSH bridge token. The agent server restarts, which stops any agent run in progress.

Removal does not undo anything the guest already changed or copied. If you no longer trust someone who had access, delete the machine and create a new one.

Git operations through Greenhouse use the identity of the person who runs them.

  • Commits from the Changes tab use your name and your GitHub noreply address, or your Orchard name and email if you have not linked GitHub.
  • Pushes, pulls, pull requests, and merges use your own GitHub token. Greenhouse passes it to that one command through an inline credential helper, and does not store it on the machine.
  • Your terminals have your git identity and a credential helper for your GitHub token, so git commit and git push in them are yours.
  • The agent runs as the host. Its commits and pushes are the host’s, with a Co-authored-by trailer for each person who prompted it in that turn.

Each prompt shows who sent it, including prompts from the CLI, MCP, Slack, and issues.

FeatureBehavior
PresenceAvatars in the title bar show who is on the machine. Session rows, tabs, and the file tree show where each person is.
FollowSelect someone’s avatar to follow their session, tab, and file. Select it again to stop.
TypingWhile someone writes a prompt, you see their draft above the composer. Drafts are not stored.
Comments/chat <message> posts to the people in the session and does not prompt the agent. Comments stay with the session.
Co-editingTwo people with the same file open edit it together. The agent’s edits on disk merge in.
NotificationsWhen the agent finishes a turn, the host and everyone who prompted the session in the last six hours get a notification, unless they are viewing the machine.

A read-only link shows the latest messages of a session’s agent chat, its changed files, and its diff. It does not give access to files, terminals, previews, or machine controls.

You must be the host. The person who opens the link must be signed in to Orchard and be a member of the machine’s organization. Organization guests cannot open it.

  1. In the workspace title bar, select Share.
  2. Select Read-only link.
  3. If you have a session open, select This session or Every session.
  4. Under Expires after, select 1 day, 7 days, or 30 days.
  5. Select Create link.

To revoke a link, select the X next to it in the same sheet.

Orchard stores only a hash of the link’s token. The CLI prints the token once.

The link has the form https://<your orchard>/share/sandbox#<token>. The token follows the #, so browsers do not send it to the server in the request URL.

A machine can have up to 50 active links. A revoked link stops working on the next request. Deleting the machine stops all of its links. The audit log records the use of each link.