Inviting a teammate to a local session
Invite a second browser profile, review a guest’s suggestion, and change or remove their access.
Use a local multiplayer session to let someone suggest a change and decide together whether to send it to your agent. Participant invitations currently open on the host machine. For a walkthrough, use one browser profile for the host and a second profile for the guest. A link opened on a teammate’s laptop points to that laptop’s own loopback address.
For developer access from your own phone, use phone pairing. It connects the phone to your project’s threads and Imprint with host access.
Invite a guest
Open the participant-enabled dev app as the host. In the expanded toolbar, hover over or focus your own colored bubble to open the details card. Click Invite to copy a single-use link. Open it in the guest profile within five minutes. If it expires, copy a fresh one.
In the guest profile, enter a display name and press Enter or click the send arrow to join the session. The guest now has a bubble in the host’s toolbar.
A guest who opens the regular local app URL can also choose Ask for access. The host can open the pending request in the toolbar and choose Invite or Decline request.
Review a suggestion
New human guests start with Suggest access. In the guest profile, choose Chat, annotate an element, and send the change. In the host profile, open the guest’s suggestion, read the request, and choose Approve and send to pass it to the coding agent. The approval covers the submitted request. Later edits to a draft need a new submission. The agent works against the current checkout.
Change or remove access
Open the guest’s bubble in the host toolbar. Switch Suggest to Edit to let that guest send work to the agent directly. Switch back to Suggest to require host review for future submissions. The coding agent’s own permission prompts still apply.
To end access, use the remove control in the guest’s card. The guest must be admitted again to rejoin.
Enable participant sessions in a dev app
If the toolbar has no peer bubble, check both the client and the dev server. On the client, enable multiplayer on PopmeltProvider, or pass multiplayer: true to mountPopmelt. The dev server also needs an explicit participant integration:
- Start the project bridge with
startPopmelt({ projectRoot, devOrigin: origin, restartMode: 'embedded', participantSessions: {} }). Use the dev app’s loopback origin consistently. - Pass the returned bridge to
createParticipantDevBootstrap({ projectRoot, origin, bridge }). Both helpers come from@popmelt.com/core/server. Expose the result ofawait bootstrap.read()aswindow.__POPMELT_PARTICIPANTS__before the toolbar mounts. - Route
/__popmelt/hosttobootstrap.hostEntryin the dev server. In the host profile, open the private URL written to.popmelt/participant-host-link.json. Use the toolbar’s Invite action for guests. Keep the host link on the host machine.
Didn't find the answer? Have an idea?
Ask a question