← 插件

Collab 协作

通过端到端加密的浏览器链接与任何人实时共享 Agent:对方可以旁观,经你允许还可以发送提示词。

$ paseo plugin add bendavid/collab
报告问题
bendavid编排9次安装bc58ca1bdde6源代码
Collab 协作 截图 1Collab 协作 截图 2Collab 协作 截图 3Collab 协作 截图 4

该插件的概览尚未翻译为你的语言,因此以英文显示。

Share one agent with someone through a browser link. A Collab pill on each agent's composer creates a one-off public link. The guest opens it in any browser, with no Paseo app or account. They watch the conversation live and, if you allow it, send prompts to the agent.

The guest page is a static site on GitHub Pages, and the conversation travels through the Paseo relay, the same service the Paseo app uses for remote access. The conversation is end-to-end encrypted between your daemon and the guest's browser: the key and an access secret travel in the link's #fragment, which browsers never send to any server, so the relay forwards only ciphertext and the page's host never sees the conversation.

Setup

The plugin needs Paseo 0.15.2 or later on the host, and npm on the daemon's command path, which Paseo uses to install the plugin's locked dependencies. It has no settings and needs no accounts. It works on any operating system Paseo runs on. Guests need only a current browser. A self-hosted relay or guest page can replace the defaults; the README explains how.

What guests see and can do

Guests get the whole conversation from its start, then live updates, in a chat view: prompts, replies with formatted Markdown and highlighted code, reasoning, task lists, and a card per tool call. They also see when the agent is waiting for you to approve a tool call, but not what it asked for.

Tool cards carry everything the timeline records: commands and their output, file contents the agent reads, diffs of the changes it makes, search matches, fetched web pages, and the inputs and outputs of MCP and other tools. Nothing is filtered or redacted, including secret files such as .env and any credentials that appear in output, so share a link only with people who may see all of it. Paths inside the agent's directory are shown relative to it, and your home directory as ~. A field longer than 1 MiB is cut to fit the relay's message size; command output keeps its end.

  • With Let guests send prompts on, guests can prompt the agent. A prompt can make the agent run commands on your machine, so only enable it for people you trust that far.
  • When guests join, they are asked for a name, prefilled with "Guest 1", "Guest 2", and so on. Names are unique on a link (a repeated name gets a number), "Host" and "You" are reserved, and a guest who reconnects in the same browser tab keeps their name. Names are chosen by the guests themselves, so they identify, not authenticate.
  • Guest prompts reach the agent labelled with the guest's name, with a note that the guest is not the session's owner. Your own prompts are not labelled. Guests see who sent each prompt. In Paseo, a guest prompt appears with its label text, because the app does not recognize the label.
  • A guest prompt sent while the agent is working joins the running turn instead of interrupting it. Providers that cannot do this (Claude, Codex, OpenCode, OMP, and Pi can) restart the turn with the prompt instead.
  • The prompt switch is fixed for the life of a link. Stop the link and create a new one to change it.
  • Everyone on the link sees who is connected. In Paseo, the Collab pill turns into a green badge while a link is live and shows how many guests are connected (for example "Collab · 2"); its popover lists them by name.
  • Up to 8 guests can join one link at a time.

Where data goes

  • To guests: everything described above, encrypted end to end. The relay, relay.paseo.sh by default, forwards it without being able to read it.
  • To the agent's provider: a guest's prompt becomes a prompt to the agent, so it reaches the agent's model provider exactly as your own prompts do.
  • Kept by the plugin: links live only in the daemon's memory, so restarting the daemon or the plugin ends them. The plugin stores nothing on disk.
  • Kept by the guest's browser: the name a guest chooses, in that tab's session storage, so a reload keeps it.
  • Connections made: your daemon connects to the relay while a link is live. A guest's browser loads the page from bendavid.github.io and connects to the relay. The plugin sends no analytics and downloads nothing while running.

Limits

  • Anyone holding the full link can join until you stop it. Stopping the link, the plugin, or the daemon disconnects every guest. After 20 failed join attempts the link stops itself.
  • GitHub Pages serves the page's code, built by the repository's public workflow from the commit shown in the page's header. GitHub cannot read the conversation without changing that code, but a compromised or compelled host could.
  • The relay sees connection metadata: when guests connect, their IP addresses, and traffic volume.
  • Guests can join wherever both GitHub Pages and the Paseo relay are reachable.