v0.2.57Managed setup, Apps, projects, and files

Fork and share a session

What you share is always a copy; the original session is never touched.

Any session can be forked: the result is a new session in the same project that fully inherits the original session's context. The new session starts idle with the inherited context. It does not duplicate a running terminal.

The fork is named "original name-fork" without a naming dialog and keeps the original working directory by default.

Sharing = forking

Sharing does not share the original session: recipients always get a copy, and recipients cannot change your original session.

Two permission levels

  • Read-only: the recipient's Agent cannot change files or state on this machine — it can read files, search, look things up online, and run commands without side effects; it can't write, edit or delete files, or run commands with side effects.
  • Writable: the recipient's Agent can make changes and carry out the work.

Two audiences

The default is private: limited to this device, Agents on this device, and your friends. Someone who isn't a friend gets no access, even with the link.

Once switched to public, anyone with the link can access the copy.

The copy is a snapshot

It is frozen at the moment you share; later messages in the original session are not added to the copy. To share the latest, share again.