Device collaboration
Paired EvoX devices can exchange experience within their permissions and, in supporting versions, accept delegated tasks. This is managed separately from local parallel work in a conversation.
Decide whether you want to share a method or have another device perform work. Experience exchange need not expose an entire project, and task delegation is not remote desktop control.
Pair and connect
Find devices in the swarm connection area, complete pairing on both sides, and assign a recognizable local name. Then inspect the connection state:
| State | Meaning |
|---|---|
| Discovered | A candidate was found, but is not necessarily trusted |
| Paired | A trust relationship exists; the device may be offline |
| Connected | The current connection works; individual permissions still apply |
Start with a small task using public material to verify delegation and result delivery before expanding scope.
Read the panel
Overview shows connections and activity, tasks and results track work, and permissions control collaboration. Device names, tasks, and states below are fictional. Changing tabs does not connect devices or change real settings.
Example devices
Local conversation work and cross-device delegation are different records. Finishing conversation work need not create corresponding entries here.
Authorize experience and tasks separately
| Permission | Purpose | When to enable |
|---|---|---|
| Share experience | Share supported experience assets | Other nodes should be able to reuse validated methods |
| Accept contributions | Receive gene and capsule candidates | You want to evaluate outside experience |
| Dispatch tasks | Request work from another device | You have a complete task and shareable inputs |
| Accept node tasks | Let other nodes request local work | You are willing to provide local resources and permitted tools |
These permissions are independent. Pairing does not enable all of them, and accepting experience does not imply accepting task execution. Some options remain experimental; organization-locked settings cannot be changed personally.
Check the source, applicability, and validation of received experience. Receiving is not adopting. See Genes and Capsules.
Prepare a self-contained task
The receiving device does not automatically see your files, workspace, or complete conversation. Include necessary material and specify input, output, and limits.
Attach sanitized public product text to a request such as:
Identify contradictions using only the product description below. For each finding, quote the relevant passages, explain the conflict, and list missing information. Do not access my local project, edit files, or invent unsupported features.
“Check the document from earlier” is insufficient. Before delegating work that depends on private local files, decide whether the material should be shared and whether the recipient can actually access it.
Choose how to delegate
Where available, choose Delegate to another device… from the composer's + menu. For a specific paired device, verify its name, online state, and dispatch permission before submitting.
Choosing Let swarm arrange it places work in the corresponding queue. It does not select a particular remote device or guarantee remote execution. Successful enqueueing is not evidence that another device has started.
A delegated task uses the recipient's own tool permissions and may wait until that device is idle. The sender cannot expand the recipient's permissions by dispatching work.
Follow the result
| Stage | Interpretation |
|---|---|
| Delivered, awaiting acceptance | Sent, but possibly still queued |
| Accepted | Follow execution records and await output |
| Completed | Check whether the returned work meets the request |
| Failed or rejected | Read the reason and address permissions, connection, or scope before retrying |
Results from a specific device return to the associated conversation. Work assigned to swarm can be inspected in its queue. If a receipt is missing, check the original task before dispatching duplicates.
The main AI still needs to integrate returned findings. A remote “review complete” does not mean local files were changed or that the suggestions meet your acceptance criteria.