Shared handoffs and Missions

Install optional services separately

Helios can display tandem Missions, shared scratchpad entries, other-machine session history and optional routing information. These services are separate from the app and are not required for an ordinary provider chat.

Configure only the integrations you use. The repository’s environment reference describes the relevant variables. A configuration value alone does not establish that its service is reachable or authenticated.

Read shared context

The Shared workspace pane connects to a configured scratchpad service. If the service is absent, it can report that it cannot reach the scratchpad. Your provider conversations can still work.

Read an entry’s scope and age before using it. Shared notes are context, and can become outdated as project files change.

Write a session handoff

The supported Hand Off Session flow writes a reviewable summary to the configured scratchpad. Its form includes:

• Key: the entry identifier.
• Expires after: the retention choice.
• Contact: the target agent/provider.
• Include transcript tail: whether to include a bounded text-only excerpt.
• Summary: what another session needs to continue.

Review the contents before choosing Write to Scratchpad. That action sends the selected session information to the configured service. Pooled or unverified sessions are not eligible for the supported handoff path.

A useful handoff names the objective, current result, changed files, checks run and next unblocked step. Avoid credentials and unrelated conversation content.

Inspect tandem Missions

Missions reads the external tandem engine’s mission state. It can show phases, slices, usage, activity and artifacts. Without tandem or mission data, the pane is empty.

A gated phase can offer Approve & continue. Approval records the decision; it does not itself run the next phase. The external tandem mission still needs to be run through its normal workflow.

Session pools and routing

Other-machine history requires a configured session-pool root and Show other machines’ sessions in Behavior. Pooled sessions are read-only; this is not remote computer control.

The optional router depends on a separately installed broker. If unavailable, ordinary supported provider sessions remain the way to start work. Tool inventories show reported configuration, not an assurance that every server is healthy.