Relay makes cross-device task handoffs with context possible

Use the handoff note to explain the next step

Every Bundle in Relay requires a handoff note. It gives the receiver a clear starting point. For example, an Agent on the workstation could deliver these files:

evaluation/
├── report.csv
├── failures.jsonl
└── HANDOFF.md

An example note for these files:

The evaluation is complete; failure samples are in failures.jsonl. Read HANDOFF.md first, then analyze the failures and prepare a report. This handoff is for analysis only; there is no need to rerun the evaluation.

Before using the files, the receiver can identify their purpose, find the detailed instructions, and understand the scope of the next step.

Keep the note short. For a complex task, put the details in a document delivered with the files.

Keep detailed context in a handoff document

A useful handoff document helps the receiver understand the current state and find what they need to continue. The HANDOFF.md in this example could contain:

# Evaluation handoff

## Goal
Analyze failures in this evaluation and propose improvements.

## Current progress
The evaluation is complete and the results are exported.
Failure samples have not been analyzed individually.
Proposed improvements have not been verified.

## Files
- report.csv: summary metrics.
- failures.jsonl: failure samples for further analysis.

## Next steps
1. Read the failure samples and group them by cause.
2. Select representative examples for each group.
3. Write a report that separates confirmed findings from hypotheses.

## Scope
Analyze the existing results only.
Do not rerun the evaluation or change the model or evaluation settings.

## Completion criteria
Produce a report with failure categories, representative examples,
and questions that still need verification.

For multi-step work, we recommend including HANDOFF.md with the files and naming it in the note. Reuse an existing task brief or experiment log when it already provides the context. The filename is a convention; a simple task may need only a note.

For code tasks, record the code revision, how to run it, and checks already performed. For research or data tasks, include sources, processing steps and unresolved questions. Focus on what the receiver needs to continue.

Start the receive workflow by reading in full

Written context needs to become part of the receiver’s workflow.

The Relay Skill makes reading the full handoff note a required receive step. After selecting a Bundle from the inbox or a listing, the Agent must read its complete note. If it has only a Bundle ID, a table preview or an incomplete note, it queries the Bundle details to fill the gap.

After downloading, if the note names a handoff document, the Skill requires the Agent to read that document in full before continuing within the user’s authorized task.

To keep the note locally, check relay bundle pull --help for --save-note. A supporting CLI can run relay bundle pull <bundle-id> --output ./incoming --save-note to save the full note as RELAY_NOTE.md. This is separate from the sender’s HANDOFF.md. The flag is optional and never overwrites files; older CLIs can retain the note read from inbox or show.

In the evaluation example, the receiver first reads the handoff, confirms that evaluation is complete, and then starts analyzing the failure samples. The recorded progress and scope guide the next actions.

Let each device work on its own schedule

The sender must stay connected until upload and publication succeed. The receiver can come online later, open the same workspace with the required access, and collect the Bundle.

This fits work done in stages: a workstation produces results and a laptop reviews them; one device collects research and another continues writing; one Agent delivers an output and another uses the handoff to take the next step.

Relay transfers files and written context. The receiver uses them to understand progress and prepare the code, tools or environment needed to continue. A useful handoff depends on an accurate account of completed work, unresolved questions and next steps.

When you finish a work session, leave the output and a clear account of what comes next. The next device has a starting point when it comes online.