Beam

Mirrors a workspace's files onto your main checkout, so a dev server already running there, with live reload, shows the workspace's changes without you switching branches. It requires Paseo 0.9.2 or newer, and the workspace and main checkout must belong to the same git repository.

While a beam is active, the main checkout is rewritten to match the workspace after each change, including uncommitted and untracked files. Untracked files ignored by Git, such as a typical .env or node_modules, are not copied; tracked files are mirrored even if they match an ignore rule. Only one beam can be active at a time. Edits you make directly in the main checkout while beaming are overwritten on the next sync and discarded when you beam out, which restores the checkout from a snapshot taken at the start. Unloading the plugin or stopping Paseo stops the syncing but does not restore the checkout or restart its watcher automatically; beam out and back in to resume mirroring.

You can start a beam from the Beam button in the workspace header, or an agent can beam its own workspace in and out. New Claude and OpenCode agents get beam_status, beam_in and beam_out tools; Claude receives preapproval for these tools, so agents can rewrite the main checkout without another approval prompt. Other agents, including Codex, run the same tools as a shell command. An agent that asks for a beam held by another workspace can wait up to 300 seconds for it. A beam is held by a workspace, not an agent, and is released when that workspace is archived or its directory is deleted.

The plugin runs git on the daemon host and keeps its snapshot state in your home directory and the main checkout's .git directory. Agent calls use a generated local proxy and an owner-only Unix socket in the plugin data folder. Tool replies expose workspace names, paths and status to the calling agent and its configured provider; the plugin does not upload the mirrored working tree to an independent service.