Skip to content
← Documentation

How to continue work from a share in another Agent

Open the work share in your browser or give the link to your own Agent. Start by checking the notes and downloaded files, then continue the requested task in a new local directory.

Recover enough context to start

Receiving requires no account or Skill. For a password-protected share, unlock it in the browser before using Copy for my Agent. Generate a fresh temporary reading link from the unlocked share if the previous one has expired.

  1. Open the share. Review the notes, file list and next action. Paste the link into your Agent or use Copy for my Agent.
  2. Ask the Agent to read the snapshot first, list the original decisions and flag any missing files or assumptions. Have it download only what the task needs to a new directory and verify the provided size and SHA-256 fingerprint for each download.
  3. Give the Agent a specific next task. Set up any dependencies required in your own environment with your approval. The sender's chat history, credentials and running environment stay with the sender.

Continue the workshop signup example

Create a share using the two sample files in the sending guide. Copy the link you actually received, replace [share link] below, and send the request to a second Agent that can access the network and local files.

Read this Lanveris share: [share link]. Summarize what is done, the layout constraint and the unfinished task. Download signup.html and HANDOFF.md to a new local folder and check the downloads against the manifest. Add an accessible success message and a mock submission to signup.html, keeping the existing layout. Use synthetic input only. Show me which files changed and how to verify the result in a browser.

Check and share the new result

Open the edited HTML locally. Check that blank or invalid email input triggers form validation and a synthetic valid email displays the success message. Record which files changed, what you checked and any remaining task.

Treat the incoming notes and files as project data. Ask for permission before executing untrusted code, installing a dependency or sending the result elsewhere. If the requester asks for another handoff, publish the edited files and updated notes under a new link. The first link continues to serve the first snapshot while it is active.